Lines Matching refs:device
94 * bridges, everything else is consider a PCI leaf device.
116 event fault.io.pciex.device-interr@PCIEXFN, FITrate=PCIEX_DEV_FIT;
118 event fault.io.pciex.device-interr-deg@PCIEXFN, FITrate=PCIEX_DEV_FIT, retire=0;
121 event fault.io.pciex.device-interr-unaf@PCIEXFN, FITrate=PCIEX_DEV_FIT,
124 engine serd.io.device.nonfatal@PCIEXFN, N=CORRLINK_COUNT, T=CORRLINK_TIME;
125 event fault.io.pciex.device-interr-corr@PCIEXFN, FITrate=PCIEX_DEV_FIT,
126 engine=serd.io.device.nonfatal@PCIEXFN;
127 engine serd.io.device.nonfatal@PCIEXFN/PCIEXFN,
129 event fault.io.pciex.device-interr-corr@PCIEXFN/PCIEXFN, FITrate=PCIEX_DEV_FIT,
130 engine=serd.io.device.nonfatal@PCIEXFN/PCIEXFN;
131 engine serd.io.device.nonfatal@pciexrc/PCIEXFN,
133 event fault.io.pciex.device-interr-corr@pciexrc/PCIEXFN, FITrate=PCIEX_DEV_FIT,
134 engine=serd.io.device.nonfatal@pciexrc/PCIEXFN;
136 event fault.io.pciex.device-interr@pciexrc, FITrate=PCIEX_RC_FIT;
138 event fault.io.pciex.device-interr-deg@pciexrc, FITrate=PCIEX_RC_FIT, retire=0;
141 event fault.io.pciex.device-interr-unaf@pciexrc, FITrate=PCIEX_RC_FIT,
144 engine serd.io.device.nonfatal@pciexrc, N=CORRLINK_COUNT, T=CORRLINK_TIME;
145 event fault.io.pciex.device-interr-corr@pciexrc, FITrate=PCIEX_RC_FIT,
146 engine=serd.io.device.nonfatal@pciexrc;
148 event fault.io.pciex.device-invreq@PCIEXFN, FITrate=PCIEX_DEV_INV_FIT;
150 event fault.io.pciex.device-invreq@pciexrc, FITrate=PCIEX_RC_FIT;
152 event fault.io.pciex.device-noresp@PCIEXFN, FITrate=PCIEX_DEV_NR_FIT;
154 event fault.io.pciex.device-noresp@pciexrc, FITrate=PCIEX_RC_NR_FIT;
175 event ereport.io.device.inval_state@PCIEXFN{within(5s)};
176 event ereport.io.device.no_response@PCIEXFN{within(5s)};
177 event ereport.io.device.stall@PCIEXFN{within(5s)};
178 event ereport.io.device.badint_limit@PCIEXFN{within(5s)};
179 event ereport.io.device.intern_corr@PCIEXFN{within(5s)};
180 event ereport.io.device.intern_uncorr@PCIEXFN{within(5s)};
194 event error.io.device.nf-device@PCIEXFN;
195 event error.io.device.deg-device@PCIEXFN;
196 event error.io.device.f-device@PCIEXFN;
198 prop error.io.device.f-device@PCIEXFN (1)->
199 ereport.io.device.inval_state@PCIEXFN,
200 ereport.io.device.no_response@PCIEXFN,
201 ereport.io.device.stall@PCIEXFN,
202 ereport.io.device.badint_limit@PCIEXFN,
203 ereport.io.device.intern_corr@PCIEXFN,
204 ereport.io.device.intern_uncorr@PCIEXFN;
206 prop error.io.device.f-device@PCIEXFN (0)->
209 prop error.io.device.deg-device@PCIEXFN (1)->
210 ereport.io.device.inval_state@PCIEXFN,
211 ereport.io.device.no_response@PCIEXFN,
212 ereport.io.device.stall@PCIEXFN,
213 ereport.io.device.badint_limit@PCIEXFN,
214 ereport.io.device.intern_corr@PCIEXFN,
215 ereport.io.device.intern_uncorr@PCIEXFN;
217 prop error.io.device.deg-device@PCIEXFN (1)->
220 prop error.io.device.nf-device@PCIEXFN (1)->
221 ereport.io.device.inval_state@PCIEXFN,
222 ereport.io.device.no_response@PCIEXFN,
223 ereport.io.device.stall@PCIEXFN,
224 ereport.io.device.badint_limit@PCIEXFN,
225 ereport.io.device.intern_corr@PCIEXFN,
226 ereport.io.device.intern_uncorr@PCIEXFN;
228 prop error.io.device.nf-device@PCIEXFN (1)->
269 * - nr-d: the device not to respond to a valid upstream request
270 * - ca-d: the device to completer abort a valid upstream request
300 prop fault.io.pciex.device-noresp@pciexrc (1)->
303 prop fault.io.pciex.device-invreq@pciexrc (1)->
306 prop fault.io.pciex.device-interr-corr@pciexrc {
312 prop fault.io.pciex.device-interr-corr@pciexrc {
318 prop fault.io.pciex.device-interr-corr@pciexrc {
324 prop fault.io.pciex.device-interr-corr@pciexrc {
330 prop fault.io.pciex.device-interr-corr@pciexrc {
336 prop fault.io.pciex.device-interr-unaf@pciexrc (1)->
339 prop fault.io.pciex.device-interr-deg@pciexrc (1)->
342 prop fault.io.pciex.device-interr@pciexrc (1)->
350 * A faulty PCI Express leaf device or upstream switch port may cause:
352 * - flt-nr-u: the device not to respond to a valid downstream request
353 * - flt-ca-u: the device to completer abort a valid downstream request
361 * - device: internal error reported by leaf device
384 event ereport.io.device.fw_corrupt@PCIEXFN{within(5s)};
385 event ereport.io.device.fw_mismatch@PCIEXFN{within(5s)};
387 prop fault.io.pciex.device-noresp@PCIEXFN { IS_LF(PCIEXFN) } (1)->
390 prop fault.io.pciex.device-noresp@PCIEXFN { IS_SU(PCIEXFN) } (1)->
393 prop fault.io.pciex.device-invreq@PCIEXFN { IS_LF(PCIEXFN) } (1)->
396 prop fault.io.pciex.device-interr-corr@pciexrc/PCIEXFN {
402 prop fault.io.pciex.device-interr-corr@pciexrc/PCIEXFN {
408 prop fault.io.pciex.device-interr-corr@pciexrc/PCIEXFN {
414 prop fault.io.pciex.device-interr-corr@pciexrc/PCIEXFN {
420 prop fault.io.pciex.device-interr-corr@pciexrc/PCIEXFN {
426 prop fault.io.pciex.device-interr-corr@PCIEXFN/PCIEXFN {
433 prop fault.io.pciex.device-interr-corr@PCIEXFN/PCIEXFN {
440 prop fault.io.pciex.device-interr-corr@PCIEXFN/PCIEXFN {
447 prop fault.io.pciex.device-interr-corr@PCIEXFN/PCIEXFN {
454 prop fault.io.pciex.device-interr-corr@PCIEXFN/PCIEXFN {
461 prop fault.io.pciex.device-interr-unaf@PCIEXFN { IS_SU(PCIEXFN) } (1)->
464 prop fault.io.pciex.device-interr-corr@PCIEXFN { IS_LF(PCIEXFN) } (0)->
465 error.io.device.nf-device@PCIEXFN;
467 prop fault.io.pciex.device-interr-unaf@PCIEXFN { IS_LF(PCIEXFN) } (1)->
470 prop fault.io.pciex.device-interr-deg@PCIEXFN { IS_SU(PCIEXFN) } (1)->
473 prop fault.io.pciex.device-interr@PCIEXFN { IS_SU(PCIEXFN) } (1)->
478 prop fault.io.pciex.device-interr-deg@PCIEXFN { IS_LF(PCIEXFN) } (1)->
480 error.io.device.deg-device@PCIEXFN;
482 prop fault.io.pciex.device-interr@PCIEXFN { IS_LF(PCIEXFN) } (1)->
484 error.io.device.f-device@PCIEXFN,
490 ereport.io.device.fw_corrupt@PCIEXFN;
497 ereport.io.device.fw_mismatch@PCIEXFN;
507 * - nr-d: the device not to respond to an upstream request
508 * - ca-d: the device to completer abort an upstream request
524 prop fault.io.pciex.device-noresp@PCIEXFN { IS_SD(PCIEXFN) } (1)->
527 prop fault.io.pciex.device-interr-corr@PCIEXFN { IS_SD(PCIEXFN) &&
533 prop fault.io.pciex.device-interr-corr@PCIEXFN { IS_SD(PCIEXFN) &&
539 prop fault.io.pciex.device-interr-corr@PCIEXFN { IS_SD(PCIEXFN) &&
545 prop fault.io.pciex.device-interr-corr@PCIEXFN { IS_SD(PCIEXFN) &&
551 prop fault.io.pciex.device-interr-corr@PCIEXFN { IS_SD(PCIEXFN) &&
557 prop fault.io.pciex.device-interr-unaf@PCIEXFN { IS_SD(PCIEXFN) } (1)->
560 prop fault.io.pciex.device-interr-deg@PCIEXFN { IS_SD(PCIEXFN) } (1)->
563 prop fault.io.pciex.device-interr@PCIEXFN { IS_SD(PCIEXFN) } (1)->
572 * - flt-nr-u: a device to not respond because the link is down
573 * - nr-d: a device to not respond because the link is down
657 * - flt-nr-u: the device not to respond to a valid downstream request
658 * - flt-ca-u: the device to completer abort a valid downstream request
669 * - nr-pw-d: the device not to respond to a valid upstream request
670 * - nr-drw-d: the device not to respond to a valid upstream request
672 * - ta-pw-d: the device responds with a ta to a valid upstream
674 * - ta-drw-d: the device responds with a ta to a valid upstream
694 prop fault.io.pciex.device-noresp@PCIEXFN { IS_BG(PCIEXFN) } (1)->
700 prop fault.io.pciex.device-interr-unaf@PCIEXFN { IS_BG(PCIEXFN) } (1)->
704 prop fault.io.pciex.device-interr-deg@PCIEXFN { IS_BG(PCIEXFN) } (1)->
708 prop fault.io.pciex.device-interr@PCIEXFN { IS_BG(PCIEXFN) } (1)->
720 prop fault.io.pciex.device-interr-unaf@PCIEXFN { IS_BG(PCIEXFN) } (0)->
723 prop fault.io.pciex.device-interr@PCIEXFN { IS_BG(PCIEXFN) } (0)->
903 * Use these for errors reported by root-complex on behalf of another device.
977 * - poisreq-d cascades down to the leaf device/bridge and any switch ports
982 * be seen at the leaf (which may be a pci device beyond the bridge).
1042 * - poiscomp-d cascades down to the leaf device/bridge and any switch ports on
1046 * the root complex identifying the leaf device, we won't actually be informed
1093 * - ecrcreq-d cascades down to the leaf device/bridge and any switches on
1097 * identifying the leaf device, we won't actually be informed that the error
1103 * driver wasn't hardened we may be able to identify the leaf device (and
1106 * reported from the root complex identifying the leaf device. The combination
1138 * - ecrccomp-d cascades down to the leaf device/bridge and any switches on
1142 * complex identifying the leaf device, we won't actually be informed that
1175 * - source-poisreq-u refers to at least one leaf or bridge device
1257 * - source-poiscomp-u refers to at least one leaf or bridge device
1328 * - source-ecrcreq-u cascades down to at least one leaf device (pciex or pci),
1339 * cto) at the root complex. Recognizing which leaf device may be implicated
1372 * - source-ecrccomp-u cascades down to at least one leaf device (pciex or pci),
1384 * root complex. Recognizing which leaf device may be implicated can be done
1417 * is always at the root complex. For a hardened leaf device driver, we will
1421 * identifying the leaf device, we won't actually be informed that the error
1452 * We have to use target-ma to informs us which device failed to respond.
1475 * device, we won't actually be informed that the error was a mtlp.
1516 * error, or of the leaf device sending an invalid request (the latter is
1559 * This could be the fault of the leaf device/bridge/upstream switch port
1570 * will identify the device from the ca ereport.
1573 * can still identify the leaf device from the source-id payload of the nonfatal
1652 * complex identifying the leaf device). The reporter then sends the appropriate
1921 * we will respond with a target abort (which the child device will treat
1924 * just drop the request (which the child device sees as a split
1954 * Similarly a child device may have responded with a master abort or
2038 * physical address associated with a fault allows the target device to be