Searched refs:hostbridge (Results 1 – 10 of 10) sorted by relevance
61 ereport.io.pciex.rc.epkt@hostbridge { MATCHES_DESC(b, o, p, c, d) }75 event ereport.io.pciex.rc.epkt@hostbridge {within(5s)};78 event error.io.pciex.rc.stall@hostbridge;79 event error.io.pciex.rc.poiscomp@hostbridge;80 event error.io.pciex.nr-d@hostbridge/pciexrc/PCIEXFN;81 event error.io.pciex.badreq-u@hostbridge/pciexrc/PCIEXFN;82 event error.io.pciex.poiscomp-d@hostbridge/pciexrc/PCIEXFN;83 event error.io.pciex.noimpact-d@hostbridge/pciexrc/PCIEXFN;84 event error.io.pciex.lost-d@hostbridge/pciexrc/PCIEXFN;85 event error.io.pciex.degraded-d@hostbridge/pciexrc/PCIEXFN;[all …]
105 * A faulty hostbridge may cause:211 * ereport generation rules for hostbridge630 * A hostbridge driver may generate "target-" ereports when knowledge of the
267 * A faulty PCI Express hostbridge (root complex) may cause:
26 MODULE = hostbridge31 HBDIR = ../../common/hostbridge32 HBSRCS = hostbridge.c hb_$(ARCH).c
27 SUBDIRS = chip chipset hostbridge pcibus x86pi zen
31 HBDIR = ../../common/hostbridge
36 BRDIR = ../../common/hostbridge
414 event ereport.cpu.intel.nb.pex@hostbridge{within(12s)};415 event upset.cpu.intel.nb.pex@hostbridge;417 prop upset.cpu.intel.nb.pex@hostbridge (1)->419 ereport.cpu.intel.nb.pex@hostbridge;421 prop upset.cpu.intel.nb.pex@hostbridge (0)-> EREPORT_BUS_ERROR;
1921 int hostbridge; in nb_pex_report() local1927 hostbridge = nb_regs->nb.pex_regs.pex - 1; in nb_pex_report()1930 "hostbridge", hostbridge); in nb_pex_report()
629 $(i386_ONLY)file path=usr/platform/i86pc/lib/fm/topo/plugins/hostbridge.so \