Lines Matching refs:device
53 engine serd.io.device.nonfatal@PCIFN,
81 * @PCIFN is the sending device while for downstream
82 * propagations it is the receiving device.
85 event fault.io.pci.device-interr-corr@PCIFN,
86 engine=serd.io.device.nonfatal@PCIFN, FITrate=PCI_DEV_FIT;
88 event fault.io.pci.device-interr-unaf@PCIFN,
91 event fault.io.pci.device-interr-deg@PCIFN, FITrate=PCI_DEV_FIT, retire=0;
93 event fault.io.pci.device-interr@PCIFN, FITrate=PCI_DEV_FIT;
95 event fault.io.pci.device-invreq@PCIFN, FITrate=PCI_DEV_FIT;
97 event fault.io.pci.device-noresp@PCIFN, FITrate=PCI_DEV_FIT;
107 * - nr-pw-d: the device not to respond to an upstream request
108 * - nr-drw-d: the device not to respond to an upstream request
109 * - ta-pw-d: the device to send a target abort to an upstream request
110 * - ta-drw-d: the device to send a target abort to an upstream request
111 * - serr-u: the device to report itself in error
118 * - dpe-d: the device to transfer bad data and/or bad parity downstream
119 * - retry-to-d: the device to exceed the set timeout for a delayed
150 event error.io.pci.device-serr@PCIFN;
151 event error.io.pci.device-ta@PCIFN;
152 event error.io.pci.device-par@PCIFN;
172 prop fault.io.pci.device-noresp@pcibus/pcidev[fromdev]/pcifn (0)->
177 prop fault.io.pci.device-invreq@pcibus/pcidev[fromdev]/pcifn (0)->
181 prop fault.io.pci.device-interr-unaf@pcibus/pcidev[fromdev]/pcifn (0)->
184 prop fault.io.pci.device-interr-deg@pcibus/pcidev[fromdev]/pcifn (0)->
187 prop fault.io.pci.device-interr@PCIFN (0)->
188 error.io.pci.device-par@PCIFN,
189 error.io.pci.device-ta@PCIFN,
190 error.io.pci.device-serr@PCIFN;
192 prop error.io.pci.device-par@pcibus/pcidev[fromdev]/pcifn (1)->
197 prop error.io.pci.device-ta@pcibus/pcidev[fromdev]/pcifn (1)->
201 prop error.io.pci.device-ta@pcibus/pcidev[fromdev]/pcifn (1)->
205 prop error.io.pci.device-serr@PCIFN (2)->
272 * A faulty PCI leaf device or pci-pci bridge may cause:
274 * - nr-pw-u: the device not to respond to a valid downstream request
275 * - nr-drw-u: the device not to respond to a valid downstream request
276 * - ta-pw-u: the device responds with a ta to a valid downstream
278 * - ta-drw-u: the device responds with a ta to a valid downstream
280 * - serr-u: the device to report itself in error
287 * - dpe-u: the device to deliver bad data/parity upstream.
288 * - retry-to-u: the device to exceed the set timeout for a delayed
291 * A faulty PCI-X leaf device or bridge may also cause:
293 * - tx-oor: the device sends a byte count larger than the completers
295 * - rx-unex-sc: the device recieved a split completion with a tag
326 event error.io.device.nf-device@PCIFN;
327 event error.io.device.f-device@PCIFN;
328 event error.io.device.deg-device@PCIFN;
333 event ereport.io.device.fw_corrupt@PCIFN{within(5s)};
334 event ereport.io.device.fw_mismatch@PCIFN{within(5s)};
340 prop fault.io.pci.device-noresp@pcibus/pcidev[fromdev]/pcifn (0)->
345 prop fault.io.pci.device-interr-corr@pcibus/pcidev[fromdev]/pcifn (0)->
346 error.io.device.nf-device@PCI_NOT_HB;
348 prop fault.io.pci.device-interr-unaf@pcibus/pcidev[fromdev]/pcifn (0)->
351 prop fault.io.pci.device-interr-deg@pcibus/pcidev[fromdev]/pcifn (0)->
352 error.io.device.deg-device@PCI_NOT_HB,
355 prop fault.io.pci.device-interr@pcibus/pcidev[fromdev]/pcifn (0)->
361 error.io.device.f-device@PCI_NOT_HB,
367 ereport.io.device.fw_corrupt@PCIFN;
374 ereport.io.device.fw_mismatch@PCIFN;
380 prop fault.io.pci.device-invreq@pcibus/pcidev[fromdev]/pcifn {FD_IS_LEAF} (0)->
460 * - nr-pw-d: the device not to respond to a valid upstream request
461 * - nr-drw-d: the device not to respond to a valid upstream request
462 * - ta-pw-d: the device responds with a ta to a valid upstream
464 * - ta-drw-d: the device responds with a ta to a valid upstream
469 * - retry-to-d: the device to exceed the set timeout for a delayed
484 prop fault.io.pci.device-noresp@PCIFN (0)->
489 prop fault.io.pci.device-interr-unaf@PCIFN (0)->
492 prop fault.io.pci.device-interr-deg@PCIFN (0)->
495 prop fault.io.pci.device-interr@PCIFN (0)->
628 * downstream target ereports are for any descendant device
631 * physical address associated with a fault allows the target device to be
800 * Request with address parity error must be detected by parent device
829 * we will respond with a target abort (which the child device will treat
832 * just drop the request (which the child device sees as a split
871 * request with address parity error must be detected by child device
894 * If the device sees a downstream split completion error (pci-x only) it could
1094 event ereport.io.device.inval_state@PCIFN{within(5s)};
1095 event ereport.io.device.no_response@PCIFN{within(5s)};
1096 event ereport.io.device.stall@PCIFN{within(5s)};
1097 event ereport.io.device.badint_limit@PCIFN{within(5s)};
1098 event ereport.io.device.intern_corr@PCIFN{within(5s)};
1099 event ereport.io.device.intern_uncorr@PCIFN{within(5s)};
1108 prop error.io.device.f-device@PCIFN { IS_LEAF } (1)->
1109 ereport.io.device.inval_state@PCIFN,
1110 ereport.io.device.no_response@PCIFN,
1111 ereport.io.device.stall@PCIFN,
1112 ereport.io.device.badint_limit@PCIFN,
1113 ereport.io.device.intern_corr@PCIFN,
1114 ereport.io.device.intern_uncorr@PCIFN;
1116 prop error.io.device.f-device@PCIFN { IS_LEAF } (1)->
1119 prop error.io.device.deg-device@PCIFN { IS_LEAF } (1)->
1120 ereport.io.device.inval_state@PCIFN,
1121 ereport.io.device.no_response@PCIFN,
1122 ereport.io.device.stall@PCIFN,
1123 ereport.io.device.badint_limit@PCIFN,
1124 ereport.io.device.intern_corr@PCIFN,
1125 ereport.io.device.intern_uncorr@PCIFN;
1127 prop error.io.device.deg-device@PCIFN { IS_LEAF } (1)->
1130 prop error.io.device.nf-device@PCIFN { IS_LEAF } (1)->
1131 ereport.io.device.inval_state@PCIFN,
1132 ereport.io.device.no_response@PCIFN,
1133 ereport.io.device.stall@PCIFN,
1134 ereport.io.device.badint_limit@PCIFN,
1135 ereport.io.device.intern_corr@PCIFN,
1136 ereport.io.device.intern_uncorr@PCIFN;
1138 prop error.io.device.nf-device@PCIFN { IS_LEAF } (1)->