| /titanic_50/usr/src/cmd/fm/dicts/ |
| H A D | GMCA.po | 41 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
51 msgstr "A level 0 cache on this cpu is faulty. Refer to %s for more information."
57 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
67 msgstr "A level 1 cache on this cpu is faulty. Refer to %s for more information."
73 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
83 msgstr "A level 2 cache on this cpu is faulty. Refer to %s for more information."
89 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
99 msgstr "A cache on this cpu is faulty. Refer to %s for more information."
105 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
115 msgstr "A level 0 Data TLB on this cpu is faulty. Refer to %s for more information."
[all …]
|
| H A D | INTEL.po | 41 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
51 msgstr "A level 0 cache on this cpu is faulty. Refer to %s for more information."
57 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
67 msgstr "A level 1 cache on this cpu is faulty. Refer to %s for more information."
73 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
83 msgstr "A level 2 cache on this cpu is faulty. Refer to %s for more information."
89 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
99 msgstr "A cache on this cpu is faulty. Refer to %s for more information."
105 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
115 msgstr "A level 0 Data TLB on this cpu is faulty. Refer to %s for more information."
[all …]
|
| H A D | AMD.po | 57 msgstr "Schedule a repair procedure to replace the affected memory module. Use 'fmadm faulty' to id…
73 msgstr "Schedule a repair procedure to replace the affected memory module. Use 'fmadm faulty' to id…
89 msgstr "Schedule a repair procedure to replace the affected memory module. Use 'fmadm faulty' to i…
105 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
121 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
137 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
153 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
169 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
185 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
201 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th…
[all …]
|
| H A D | PCIEX.po | 41 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t…
57 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
73 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
89 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
105 …e schedule a repair procedure to replace the affected device. Use fmadm faulty to identify the de…
121 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
137 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
153 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
169 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
185 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
[all …]
|
| H A D | PCI.po | 153 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t…
169 …e schedule a repair procedure to replace the affected device. Use fmadm faulty to identify the de…
185 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
201 …chedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the de…
217 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t…
233 …e schedule a repair procedure to replace the affected device. Use fmadm faulty to identify the de…
249 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t…
265 …e schedule a repair procedure to replace the affected device. Use fmadm faulty to identify the de…
281 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t…
297 msgstr "Use fmadm faulty to identify the device and then update the firmware to the latest version …
[all …]
|
| H A D | SUN4V.po | 217 msgstr "Schedule a repair procedure to replace the affected memory module. Use 'fmadm faulty' to id…
1097 msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to …
1113 msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to r…
1129 msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to r…
1145 … to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n"
1161 … to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n"
1177 … to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n"
1193 … to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n"
1209 … to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n"
1225 … to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n"
[all …]
|
| H A D | DISK.po | 90 … Schedule a repair procedure to replace the affected\ndevice. Use 'fmadm faulty' to find the affec…
106 msgstr "Schedule a repair procedure to replace the affected device. Use 'fmadm faulty' to find the …
|
| H A D | FMD.po | 130 msgstr "Use fmadm faulty to identify the repaired components, and any suspects that still need to b…
|
| H A D | SCF.po | 39 msgstr "An attempt will be made to deconfigure the faulty components after one or more domains are …
89 …orm has redundant clock capability, the platform will be \nreset and the faulty Clock Unit will be…
1175 msgstr "Resources associated with the faulty FRU will be deconfigured. Please consult the \ndetail …
1191 msgstr "Resources associated with the faulty FRU will be deconfigured. Please consult the \ndetail …
1207 …taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconf…
1223 …taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconf…
1239 …taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconf…
1257 … no longer be able \nto contact the chips and devices that are connected to the faulty MBC chip.\n"
2311 msgstr "Depending upon which part of the XB chip is faulty, either a crossbar way is deconfigured,\…
2313 msgstr "Depending upon which part of the XB chip is faulty, either the entire platform is\nreset, o…
[all …]
|
| H A D | ZFS.po | 170 …e errors persist over a period of time, ZFS may determine the\ndevice is faulty and mark it as suc…
|
| /titanic_50/usr/src/lib/fm/libfmd_snmp/mibs/ |
| H A D | SUN-FM-MIB.mib | 98 faulty(2),
106 -- The problem table is analogous to the output of fmadm faulty organized
107 -- by the UUID of the case in which the faulty diagnosis was made. The
327 See fmadm(1M) faulty."
418 the fault manager to be faulty."
428 information provided by the fmadm(1M) faulty command."
437 believes to be faulty."
462 which the fault manager believes to be faulty."
470 "The current status of the resource. See fmadm(1M) faulty."
|
| /titanic_50/usr/src/cmd/fm/fmadm/ |
| H A D | Makefile.com | 31 faulty.c \
|
| /titanic_50/usr/src/cmd/fm/eversholt/files/sparc/sun4u/ |
| H A D | schizo.esc | 70 * A faulty Schizo hostbridge may cause:
150 * A faulty xcal CPU[0] may cause:
160 * A faulty xcal CPU[1] may cause:
170 * A faulty CPU may cause:
205 * A faulty host bus may cause:
261 * A faulty PCI bus may cause:
314 * A faulty PCI device may cause:
|
| H A D | psycho.esc | 53 * A faulty Psycho hostbridge may cause:
90 * A faulty host bus may cause:
109 * A faulty CPU may cause:
164 * A faulty PCI device may cause:
|
| H A D | oberon.esc | 86 * A faulty Oberon may cause;
107 * A faulty PX nexus driver can cause
|
| H A D | xmits.esc | 80 * A faulty Xmits hostbridge may cause:
170 * A faulty CPU may cause:
205 * A faulty host bus may cause:
267 * A faulty PCI bus may cause:
322 * A faulty PCI device may cause:
|
| H A D | tomatillo.esc | 69 * A faulty Tomatillo hostbridge may cause:
160 * A faulty CPU may cause:
200 * A faulty host bus may cause:
264 * A faulty PCI device may cause:
|
| /titanic_50/usr/src/cmd/fm/fmd/common/ |
| H A D | fmd_asru.c | 441 boolean_t faulty = FMD_B_FALSE, unusable = FMD_B_FALSE; in fmd_asru_hash_recreate() local
463 &faulty) != 0) { in fmd_asru_hash_recreate()
496 cp = fmd_case_recreate(fmd.d_rmod, NULL, faulty ? FMD_CASE_CLOSED : in fmd_asru_hash_recreate()
579 if (faulty) { in fmd_asru_hash_recreate()
1507 boolean_t faulty = (alp->al_flags & FMD_ASRU_FAULTY) != 0; in fmd_asru_logevent() local
1536 nvl = fmd_protocol_rsrc_asru(_fmd_asru_events[faulty | (unusable << 1)], in fmd_asru_logevent()
1537 alp->al_asru_fmri, cip->ci_uuid, cip->ci_code, faulty, unusable, in fmd_asru_logevent()
|
| H A D | fmd_protocol.c | 211 boolean_t faulty, boolean_t unusable, boolean_t message, nvlist_t *event, in fmd_protocol_rsrc_asru() argument
237 err |= nvlist_add_boolean_value(nvl, FM_RSRC_ASRU_FAULTY, faulty); in fmd_protocol_rsrc_asru()
|
| H A D | fmd_case.c | 2150 int faulty = 0; in fmd_case_update() local
2166 fmd_asru_hash_apply_by_case(fmd.d_asrus, cp, fmd_case_faulty, &faulty); in fmd_case_update()
2169 if (faulty) { in fmd_case_update()
2451 int faulty = 0; in fmd_case_repair_replay_case() local
2466 fmd_asru_hash_apply_by_case(fmd.d_asrus, cp, fmd_case_faulty, &faulty); in fmd_case_repair_replay_case()
2470 if (cip->ci_state >= FMD_CASE_REPAIRED && !faulty) { in fmd_case_repair_replay_case()
2504 } else if (faulty && not_faulty) { in fmd_case_repair_replay_case()
|
| /titanic_50/usr/src/cmd/fm/eversholt/files/i386/i86pc/ |
| H A D | gcpu_amd.esc | 56 * faulty.
61 * The maximum number of pages we will diagnose as faulty on any one
|
| H A D | amd64.esc | 137 * whether to declare a dimm faulty after repeated page faults.
167 * The fraction of pages on a single rank that must be diagnosed as faulty
173 * failure) without getting carried away and allowing a single faulty rank to
187 * with any diagnosis threshold (i.e., the number of faulty pages we are
|
| /titanic_50/usr/src/cmd/fm/eversholt/files/common/ |
| H A D | pci.esc | 105 * A faulty hostbridge may cause:
272 * A faulty PCI leaf device or pci-pci bridge may cause:
291 * A faulty PCI-X leaf device or bridge may also cause:
458 * A faulty pci-pci bridge may also cause
504 * A faulty PCI bus may cause:
|
| H A D | pciex.esc | 267 * A faulty PCI Express hostbridge (root complex) may cause:
350 * A faulty PCI Express leaf device or upstream switch port may cause:
505 * A faulty PCI Express downstream switch port may cause
570 * A faulty PCIEX bus may cause:
654 * A faulty pciex-pci bridge may cause
|
| /titanic_50/usr/src/cmd/fm/eversholt/files/sparc/sun4/ |
| H A D | fire.esc | 285 * A faulty ebus can cause ebus timeout ebus_to
|