Cross Reference: /illumos-gate/usr/src/cmd/fm/eversholt/files/common/pciex.esc

Lines Matching refs:nr
269  * - nr-d:		the device not to respond to a valid upstream request
281 event error.io.pciex.nr-d@pciexrc/PCIEXFN;
301     error.io.pciex.nr-d@pciexrc/PCIEXFNHZ;
352  * - flt-nr-u:		the device not to respond to a valid downstream request
366 event error.io.pciex.flt-nr-u@PCIEXFN;
388     error.io.pciex.flt-nr-u@PCIEXFN;
391     error.io.pciex.flt-nr-u@PCIEXFN;
507  * - nr-d:		the device not to respond to an upstream request
517 event error.io.pciex.nr-d@PCIEXFN/PCIEXFN;
525     error.io.pciex.nr-d@PCIEXFN/PCIEXFNHZ;
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
578 event error.io.pciex.nr-d@PCIEXFN;
581     error.io.pciex.flt-nr-u@PCIEXFN,
582     error.io.pciex.nr-d@PCIEXFN;
657  * - flt-nr-u:		the device not to respond to 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
686 event error.io.pci.nr-pw-d@PCIEXFN/PCIFN;
687 event error.io.pci.nr-drw-d@PCIEXFN/PCIFN;
695     error.io.pciex.flt-nr-u@PCIEXFN,
697     error.io.pci.nr-pw-d@PCIEXFN/PCIFNHZ,
698     error.io.pci.nr-drw-d@PCIEXFN/PCIFNHZ;
803 event error.io.pciex.nr-fwd-d@PCIEXFN;
834 event error.io.pciex.nr-u@PCIEXFN;
835 event error.io.pciex.nr-u@PCIEXFN/PCIEXFN;
836 event error.io.pciex.nr-u@pciexrc/PCIEXFN;
1101  * eventually get a cto at the root complex - so use an nr-u at the pciex
1116     error.io.pciex.flt-nr-u@PCIEXFN;
1126     error.io.pciex.flt-nr-u@PCIEXFN;
1130     error.io.pciex.flt-nr-u@PCIEXFN;
1148  * cto only which would be an nr-d.
1162     error.io.pciex.nr-d@PCIEXFN;
1169     error.io.pciex.nr-d@PCIEXFN;
1335  * eventually get a cto - so use an nr-d at the pciex leaf or bridge to get
1348     error.io.pciex.nr-d@PCIEXFN;
1380  * eventually get a cto - so use an flt-nr-u at the pciex leaf or bridge to get
1393     error.io.pciex.flt-nr-u@PCIEXFN;
1416  * - nr-d will effectively cascade downstream to the requester. The fault here
1424 prop error.io.pciex.nr-d@PCIEXFN (1)->
1425     error.io.pciex.nr-fwd-d@PCIEXFN { IS_BG(PCIEXFN) || IS_LF(PCIEXFN) },
1426     error.io.pciex.nr-fwd-d@PCIEXFNHZ { (IS_BG(PCIEXFNHZ) ||
1429 prop error.io.pciex.nr-fwd-d@PCIEXFN { IS_BG(PCIEXFN) } (2)->
1433 prop error.io.pciex.nr-fwd-d@PCIEXFN { IS_BG(PCIEXFN) } (0)->
1436     error.io.pci.nr-drw-d@PCIEXFN/PCIFN,
1439 prop error.io.pciex.nr-fwd-d@PCIEXFN { IS_LF(PCIEXFN) } (1)->
1442 prop error.io.pciex.nr-fwd-d@PCIEXFN { IS_LF(PCIEXFN) } (0)->
1449  * - flt-nr-u will effectively cascade upstream to the root complex which will
1454 prop error.io.pciex.flt-nr-u@PCIEXFN (1)->
1457 prop error.io.pciex.flt-nr-u@PCIEXFN (1)->
1458     error.io.pciex.nr-u@PCIEXFN;
1460 prop error.io.pciex.nr-u@PCIEXFN/PCIEXFN (1)->
1461     error.io.pciex.nr-u@PCIEXFN;
1463 prop error.io.pciex.nr-u@pciexrc/PCIEXFN (1)->
1466 prop error.io.pciex.nr-u@pciexrc/PCIEXFN (0)->
1691  * Stub mce/mue/ce/nr/noadverr.
1702 event ereport.io.pci.nr@PCIEXFN{within(5s)};
1703 event ereport.io.pci.nr@pciexrc{within(5s)};
1727     ereport.io.pci.nr@PCIEXFN,
1741     ereport.io.pci.nr@pciexrc,