From 5c0b3261bd16d5eb356ffc864b6eab76c2e760e5 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Tue, 19 Jul 2022 16:49:53 -0400 Subject: 14828 remove SPARC FMA support Reviewed by: Peter Tribble Reviewed by: Toomas Soome Approved by: Dan McDonald --- usr/src/cmd/fm/dicts/Makefile | 19 +- usr/src/cmd/fm/dicts/SCF.dict | 198 - usr/src/cmd/fm/dicts/SCF.po | 2713 ------------ usr/src/cmd/fm/dicts/SUN4.dict | 50 - usr/src/cmd/fm/dicts/SUN4.po | 345 -- usr/src/cmd/fm/dicts/SUN4U.dict | 273 -- usr/src/cmd/fm/dicts/SUN4U.po | 3930 ------------------ usr/src/cmd/fm/dicts/SUN4V.dict | 119 - usr/src/cmd/fm/dicts/SUN4V.po | 1481 ------- usr/src/cmd/fm/eversholt/eftinfo/sparc/Makefile | 29 - usr/src/cmd/fm/eversholt/esc/sparc/Makefile | 29 - usr/src/cmd/fm/eversholt/files/Makefile | 1 - usr/src/cmd/fm/eversholt/files/sparc/Makefile | 42 - .../fm/eversholt/files/sparc/sun4/Makefile.sun4 | 36 - usr/src/cmd/fm/eversholt/files/sparc/sun4/fire.esc | 672 --- .../cmd/fm/eversholt/files/sparc/sun4u/Makefile | 33 - .../cmd/fm/eversholt/files/sparc/sun4u/oberon.esc | 160 - .../cmd/fm/eversholt/files/sparc/sun4u/psycho.esc | 252 -- .../cmd/fm/eversholt/files/sparc/sun4u/schizo.esc | 441 -- .../fm/eversholt/files/sparc/sun4u/tomatillo.esc | 430 -- .../cmd/fm/eversholt/files/sparc/sun4u/xmits.esc | 449 -- .../cmd/fm/eversholt/files/sparc/sun4v/Makefile | 34 - .../cmd/fm/eversholt/files/sparc/sun4v/gcpu.esc | 515 --- .../cmd/fm/eversholt/files/sparc/sun4v/gmem.esc | 478 --- .../fm/eversholt/files/sparc/sun4v/n2niu_xaui.esc | 50 - .../fm/eversholt/files/sparc/sun4v/n2niu_xfp.esc | 53 - .../cmd/fm/eversholt/files/sparc/sun4v/n2piu.esc | 288 -- usr/src/cmd/fm/eversholt/files/sparc/sun4v/sp.esc | 37 - .../cmd/fm/eversholt/files/sparc/sun4v/vfncx.esc | 58 - .../cmd/fm/eversholt/files/sparc/sun4v/zambezi.esc | 839 ---- usr/src/cmd/fm/eversholt/native/sparc/Makefile | 28 - usr/src/cmd/fm/fmadm/sparc/Makefile | 29 - usr/src/cmd/fm/fmd/sparc/Makefile | 29 - usr/src/cmd/fm/fmdump/sparc/Makefile | 29 - usr/src/cmd/fm/fminject/sparc/Makefile | 29 - usr/src/cmd/fm/fmstat/sparc/Makefile | 29 - usr/src/cmd/fm/fmtopo/sparc/Makefile | 29 - usr/src/cmd/fm/ipmitopo/sparc/Makefile | 28 - usr/src/cmd/fm/modules/Makefile | 18 +- usr/src/cmd/fm/modules/SUNW,Netra-CP3060/Makefile | 29 - .../cmd/fm/modules/SUNW,Netra-CP3060/etm/Makefile | 29 - .../cmd/fm/modules/SUNW,Netra-CP3060/etm/etm.conf | 55 - usr/src/cmd/fm/modules/SUNW,Netra-CP3260/Makefile | 29 - .../cmd/fm/modules/SUNW,Netra-CP3260/etm/Makefile | 29 - .../cmd/fm/modules/SUNW,Netra-CP3260/etm/etm.conf | 56 - usr/src/cmd/fm/modules/SUNW,Netra-T5220/Makefile | 29 - .../cmd/fm/modules/SUNW,Netra-T5220/etm/Makefile | 29 - .../cmd/fm/modules/SUNW,Netra-T5220/etm/etm.conf | 56 - usr/src/cmd/fm/modules/SUNW,Netra-T5440/Makefile | 29 - .../cmd/fm/modules/SUNW,Netra-T5440/etm/Makefile | 29 - .../cmd/fm/modules/SUNW,Netra-T5440/etm/etm.conf | 58 - .../modules/SUNW,SPARC-Enterprise-T5120/Makefile | 29 - .../SUNW,SPARC-Enterprise-T5120/etm/Makefile | 29 - .../SUNW,SPARC-Enterprise-T5120/etm/etm.conf | 56 - .../cmd/fm/modules/SUNW,SPARC-Enterprise/Makefile | 29 - .../SUNW,SPARC-Enterprise/cpumem-retire/Makefile | 57 - .../cpumem-retire/cpumem-retire.conf | 39 - .../SUNW,SPARC-Enterprise/event-transport/Makefile | 36 - .../event-transport/event-transport.conf | 88 - .../event-transport/ex_dscp.c | 808 ---- .../event-transport/ex_dscp.h | 99 - .../cmd/fm/modules/SUNW,Sun-Blade-T6300/Makefile | 29 - .../fm/modules/SUNW,Sun-Blade-T6300/etm/Makefile | 29 - .../fm/modules/SUNW,Sun-Blade-T6300/etm/etm.conf | 55 - .../cmd/fm/modules/SUNW,Sun-Blade-T6320/Makefile | 29 - .../fm/modules/SUNW,Sun-Blade-T6320/etm/Makefile | 29 - .../fm/modules/SUNW,Sun-Blade-T6320/etm/etm.conf | 56 - usr/src/cmd/fm/modules/SUNW,Sun-Fire-T200/Makefile | 29 - .../cmd/fm/modules/SUNW,Sun-Fire-T200/etm/Makefile | 29 - .../cmd/fm/modules/SUNW,Sun-Fire-T200/etm/etm.conf | 55 - usr/src/cmd/fm/modules/SUNW,T5140/Makefile | 29 - usr/src/cmd/fm/modules/SUNW,T5140/etm/Makefile | 29 - usr/src/cmd/fm/modules/SUNW,T5140/etm/etm.conf | 58 - usr/src/cmd/fm/modules/SUNW,USBRDT-5240/Makefile | 29 - .../cmd/fm/modules/SUNW,USBRDT-5240/etm/Makefile | 29 - .../cmd/fm/modules/SUNW,USBRDT-5240/etm/etm.conf | 57 - .../cmd/fm/modules/common/cpumem-retire/Makefile | 7 +- .../fm/modules/common/cpumem-retire/cma_cache.c | 143 - usr/src/cmd/fm/modules/common/fdd-msg/Makefile | 3 +- .../modules/sun4/cpumem-diagnosis/Makefile.cpumem | 66 - usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd.h | 277 -- .../fm/modules/sun4/cpumem-diagnosis/cmd_Lxcache.h | 206 - .../fm/modules/sun4/cpumem-diagnosis/cmd_bank.c | 383 -- .../fm/modules/sun4/cpumem-diagnosis/cmd_bank.h | 164 - .../cmd/fm/modules/sun4/cpumem-diagnosis/cmd_cpu.c | 2420 ----------- .../cmd/fm/modules/sun4/cpumem-diagnosis/cmd_cpu.h | 794 ---- .../fm/modules/sun4/cpumem-diagnosis/cmd_cpuerr.c | 581 --- .../fm/modules/sun4/cpumem-diagnosis/cmd_dimm.c | 531 --- .../fm/modules/sun4/cpumem-diagnosis/cmd_dimm.h | 209 - .../fm/modules/sun4/cpumem-diagnosis/cmd_fmri.c | 101 - .../fm/modules/sun4/cpumem-diagnosis/cmd_fmri.h | 83 - .../fm/modules/sun4/cpumem-diagnosis/cmd_list.c | 123 - .../fm/modules/sun4/cpumem-diagnosis/cmd_list.h | 54 - .../fm/modules/sun4/cpumem-diagnosis/cmd_main.c | 881 ---- .../cmd/fm/modules/sun4/cpumem-diagnosis/cmd_mem.c | 291 -- .../cmd/fm/modules/sun4/cpumem-diagnosis/cmd_mem.h | 208 - .../fm/modules/sun4/cpumem-diagnosis/cmd_memerr.c | 947 ----- .../fm/modules/sun4/cpumem-diagnosis/cmd_page.c | 311 -- .../fm/modules/sun4/cpumem-diagnosis/cmd_page.h | 111 - .../fm/modules/sun4/cpumem-diagnosis/cmd_pageerr.c | 100 - .../fm/modules/sun4/cpumem-diagnosis/cmd_state.c | 259 -- .../fm/modules/sun4/cpumem-diagnosis/cmd_state.h | 227 -- .../fm/modules/sun4/cpumem-diagnosis/cmd_util.c | 83 - usr/src/cmd/fm/modules/sun4u/Makefile | 28 - .../fm/modules/sun4u/USII-io-diagnosis/Makefile | 47 - .../sun4u/USII-io-diagnosis/USII-io-diagnosis.conf | 29 - .../fm/modules/sun4u/USII-io-diagnosis/iod_main.c | 170 - .../cmd/fm/modules/sun4u/cpumem-diagnosis/Makefile | 48 - .../modules/sun4u/cpumem-diagnosis/cmd_Lxcache.c | 1511 ------- .../sun4u/cpumem-diagnosis/cmd_Lxcacheerr.c | 2048 ---------- .../modules/sun4u/cpumem-diagnosis/cmd_cpu_arch.c | 262 -- .../cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_dp.c | 442 -- .../cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_dp.h | 131 - .../modules/sun4u/cpumem-diagnosis/cmd_dp_page.c | 276 -- .../modules/sun4u/cpumem-diagnosis/cmd_dp_page.h | 57 - .../fm/modules/sun4u/cpumem-diagnosis/cmd_dperr.c | 424 -- .../fm/modules/sun4u/cpumem-diagnosis/cmd_ecache.c | 154 - .../fm/modules/sun4u/cpumem-diagnosis/cmd_ecache.h | 55 - .../fm/modules/sun4u/cpumem-diagnosis/cmd_hc_opl.c | 123 - .../sun4u/cpumem-diagnosis/cmd_memerr_arch.c | 932 ----- .../fm/modules/sun4u/cpumem-diagnosis/cmd_opl.c | 220 - .../fm/modules/sun4u/cpumem-diagnosis/cmd_opl.h | 162 - .../fm/modules/sun4u/cpumem-diagnosis/cmd_oplerr.c | 529 --- .../sun4u/cpumem-diagnosis/cpumem-diagnosis.conf | 67 - .../cmd/fm/modules/sun4u/datapath-retire/Makefile | 40 - usr/src/cmd/fm/modules/sun4u/datapath-retire/cda.h | 66 - .../cmd/fm/modules/sun4u/datapath-retire/cda_cpu.c | 101 - .../fm/modules/sun4u/datapath-retire/cda_main.c | 222 - .../sun4u/datapath-retire/datapath-retire.conf | 26 - usr/src/cmd/fm/modules/sun4v/Makefile | 28 - .../cmd/fm/modules/sun4v/cpumem-diagnosis/Makefile | 40 - .../fm/modules/sun4v/cpumem-diagnosis/cmd_branch.c | 702 ---- .../fm/modules/sun4v/cpumem-diagnosis/cmd_branch.h | 125 - .../modules/sun4v/cpumem-diagnosis/cmd_cpu_arch.c | 469 --- .../modules/sun4v/cpumem-diagnosis/cmd_hc_sun4v.c | 646 --- .../modules/sun4v/cpumem-diagnosis/cmd_hc_sun4v.h | 56 - .../sun4v/cpumem-diagnosis/cmd_memerr_arch.c | 769 ---- .../sun4v/cpumem-diagnosis/cpumem-diagnosis.conf | 32 - .../cmd/fm/modules/sun4v/cpumem-retire/Makefile | 55 - .../fm/modules/sun4v/cpumem-retire/cma_cpu_sun4v.c | 324 -- .../modules/sun4v/cpumem-retire/cma_page_sun4v.c | 72 - .../modules/sun4v/cpumem-retire/cpumem-retire.conf | 42 - usr/src/cmd/fm/modules/sun4v/etm/Makefile | 44 - usr/src/cmd/fm/modules/sun4v/etm/Makefile.etm | 70 - usr/src/cmd/fm/modules/sun4v/etm/etm.c | 4307 -------------------- usr/src/cmd/fm/modules/sun4v/etm/etm.conf | 52 - usr/src/cmd/fm/modules/sun4v/etm/etm_ckpt.c | 681 ---- usr/src/cmd/fm/modules/sun4v/etm/etm_ckpt.h | 108 - usr/src/cmd/fm/modules/sun4v/etm/etm_etm_proto.h | 178 - usr/src/cmd/fm/modules/sun4v/etm/etm_filter.c | 367 -- usr/src/cmd/fm/modules/sun4v/etm/etm_filter.h | 69 - usr/src/cmd/fm/modules/sun4v/etm/etm_impl.h | 106 - usr/src/cmd/fm/modules/sun4v/etm/etm_iosvc.h | 155 - usr/src/cmd/fm/modules/sun4v/etm/etm_xport_api.h | 298 -- .../cmd/fm/modules/sun4v/etm/etm_xport_api_dd.c | 1396 ------- usr/src/cmd/fm/modules/sun4v/generic-mem/Makefile | 63 - .../fm/modules/sun4v/generic-mem/generic-mem.conf | 45 - usr/src/cmd/fm/modules/sun4v/generic-mem/gmem.h | 81 - .../cmd/fm/modules/sun4v/generic-mem/gmem_dimm.c | 555 --- .../cmd/fm/modules/sun4v/generic-mem/gmem_dimm.h | 165 - .../cmd/fm/modules/sun4v/generic-mem/gmem_fmri.c | 99 - .../cmd/fm/modules/sun4v/generic-mem/gmem_fmri.h | 80 - .../cmd/fm/modules/sun4v/generic-mem/gmem_main.c | 214 - .../cmd/fm/modules/sun4v/generic-mem/gmem_mem.c | 168 - .../cmd/fm/modules/sun4v/generic-mem/gmem_mem.h | 103 - .../cmd/fm/modules/sun4v/generic-mem/gmem_memerr.c | 912 ----- .../cmd/fm/modules/sun4v/generic-mem/gmem_page.c | 361 -- .../cmd/fm/modules/sun4v/generic-mem/gmem_page.h | 104 - .../cmd/fm/modules/sun4v/generic-mem/gmem_state.c | 166 - .../cmd/fm/modules/sun4v/generic-mem/gmem_state.h | 149 - .../cmd/fm/modules/sun4v/generic-mem/gmem_util.c | 165 - .../cmd/fm/modules/sun4v/generic-mem/gmem_util.h | 60 - usr/src/cmd/fm/notify/smtp-notify/sparc/Makefile | 27 - usr/src/cmd/fm/notify/snmp-notify/sparc/Makefile | 27 - usr/src/cmd/fm/schemes/cpu/sparc/Makefile | 39 - usr/src/cmd/fm/schemes/cpu/sparcv9/Makefile | 39 - usr/src/cmd/fm/schemes/dev/sparc/Makefile | 36 - usr/src/cmd/fm/schemes/dev/sparcv9/Makefile | 37 - usr/src/cmd/fm/schemes/fmd/sparc/Makefile | 32 - usr/src/cmd/fm/schemes/fmd/sparcv9/Makefile | 33 - usr/src/cmd/fm/schemes/hc/sparc/Makefile | 36 - usr/src/cmd/fm/schemes/hc/sparcv9/Makefile | 37 - usr/src/cmd/fm/schemes/legacy-hc/sparc/Makefile | 32 - usr/src/cmd/fm/schemes/legacy-hc/sparcv9/Makefile | 33 - usr/src/cmd/fm/schemes/mem/sparc/Makefile | 36 - usr/src/cmd/fm/schemes/mem/sparc/mem_disc.c | 586 --- usr/src/cmd/fm/schemes/mem/sparcv9/Makefile | 36 - usr/src/cmd/fm/schemes/mod/sparc/Makefile | 38 - usr/src/cmd/fm/schemes/mod/sparcv9/Makefile | 38 - usr/src/cmd/fm/schemes/pkg/sparc/Makefile | 38 - usr/src/cmd/fm/schemes/pkg/sparcv9/Makefile | 38 - usr/src/cmd/fm/schemes/svc/sparc/Makefile | 34 - usr/src/cmd/fm/schemes/svc/sparcv9/Makefile | 35 - usr/src/cmd/fm/schemes/sw/sparc/Makefile | 33 - usr/src/cmd/fm/schemes/sw/sparcv9/Makefile | 34 - usr/src/cmd/fm/schemes/zfs/sparc/Makefile | 32 - usr/src/cmd/fm/schemes/zfs/sparcv9/Makefile | 33 - usr/src/lib/fm/Makefile | 15 +- usr/src/lib/fm/libdiagcode/sparc/Makefile | 31 - usr/src/lib/fm/libdiagcode/sparcv9/Makefile | 32 - usr/src/lib/fm/libdiskstatus/sparc/Makefile | 28 - usr/src/lib/fm/libdiskstatus/sparcv9/Makefile | 30 - usr/src/lib/fm/libfmd_adm/sparc/Makefile | 28 - usr/src/lib/fm/libfmd_adm/sparcv9/Makefile | 29 - usr/src/lib/fm/libfmd_agent/sparc/Makefile | 27 - .../lib/fm/libfmd_agent/sparc/fmd_agent_sparc.c | 32 - usr/src/lib/fm/libfmd_agent/sparcv9/Makefile | 28 - usr/src/lib/fm/libfmd_log/sparc/Makefile | 28 - usr/src/lib/fm/libfmd_log/sparcv9/Makefile | 29 - usr/src/lib/fm/libfmd_msg/sparc/Makefile | 28 - usr/src/lib/fm/libfmd_msg/sparcv9/Makefile | 29 - usr/src/lib/fm/libfmd_snmp/sparc/Makefile | 32 - usr/src/lib/fm/libfmd_snmp/sparcv9/Makefile | 33 - usr/src/lib/fm/libfmevent/sparc/Makefile | 29 - usr/src/lib/fm/libfmevent/sparcv9/Makefile | 30 - usr/src/lib/fm/libfmnotify/sparc/Makefile | 31 - usr/src/lib/fm/libfmnotify/sparcv9/Makefile | 32 - usr/src/lib/fm/libldom/Makefile | 63 - usr/src/lib/fm/libldom/Makefile.com | 61 - usr/src/lib/fm/libldom/sparc/Makefile | 32 - usr/src/lib/fm/libldom/sparc/ldmsvcs_utils.c | 1747 -------- usr/src/lib/fm/libldom/sparc/ldmsvcs_utils.h | 220 - usr/src/lib/fm/libldom/sparc/ldom.c | 817 ---- usr/src/lib/fm/libldom/sparc/ldom.h | 109 - usr/src/lib/fm/libldom/sparc/ldom_alloc.c | 38 - usr/src/lib/fm/libldom/sparc/ldom_alloc.h | 43 - usr/src/lib/fm/libldom/sparc/ldom_utils.c | 46 - usr/src/lib/fm/libldom/sparc/ldom_utils.h | 43 - usr/src/lib/fm/libldom/sparc/ldom_xmpp_client.c | 828 ---- usr/src/lib/fm/libldom/sparc/ldom_xmpp_client.h | 114 - usr/src/lib/fm/libldom/sparc/mapfile-vers | 58 - usr/src/lib/fm/libldom/sparcv9/Makefile | 33 - usr/src/lib/fm/libmdesc/Makefile | 56 - usr/src/lib/fm/libmdesc/Makefile.com | 67 - usr/src/lib/fm/libmdesc/common/mapfile-vers | 56 - usr/src/lib/fm/libmdesc/sparc/Makefile | 28 - usr/src/lib/fm/libmdesc/sparcv9/Makefile | 29 - usr/src/lib/fm/libseslog/sparc/Makefile | 25 - usr/src/lib/fm/libseslog/sparcv9/Makefile | 27 - usr/src/lib/fm/topo/libtopo/sparc/Makefile | 33 - usr/src/lib/fm/topo/libtopo/sparcv9/Makefile | 34 - usr/src/lib/fm/topo/maps/Makefile | 17 +- .../lib/fm/topo/maps/SUNW,Netra-CP3060/Makefile | 35 - .../SUNW,Netra-CP3060/Netra-CP3060-hc-topology.xml | 45 - .../lib/fm/topo/maps/SUNW,Netra-CP3260/Makefile | 35 - .../SUNW,Netra-CP3260/Netra-CP3260-hc-topology.xml | 58 - usr/src/lib/fm/topo/maps/SUNW,Netra-T5220/Makefile | 33 - .../SUNW,Netra-T5220/Netra-T5220-hc-topology.xml | 56 - usr/src/lib/fm/topo/maps/SUNW,Netra-T5440/Makefile | 33 - .../SUNW,Netra-T5440/Netra-T5440-hc-topology.xml | 50 - .../topo/maps/SUNW,SPARC-Enterprise-T5120/Makefile | 34 - .../SPARC-Enterprise-T5120-hc-topology.xml | 57 - .../SPARC-Enterprise-T5220-hc-topology.xml | 57 - .../fm/topo/maps/SUNW,SPARC-Enterprise/Makefile | 34 - .../SPARC-Enterprise-hc-topology.xml | 47 - .../lib/fm/topo/maps/SUNW,Sun-Blade-T6300/Makefile | 33 - .../Sun-Blade-T6300-hc-topology.xml | 43 - .../lib/fm/topo/maps/SUNW,Sun-Blade-T6320/Makefile | 34 - .../Sun-Blade-T6320-hc-topology.xml | 57 - .../lib/fm/topo/maps/SUNW,Sun-Fire-T200/Makefile | 38 - .../SUNW,Sun-Fire-T200/Netra-T2000-hc-topology.xml | 58 - .../SPARC-Enterprise-T1000-hc-topology.xml | 44 - .../SPARC-Enterprise-T2000-hc-topology.xml | 55 - .../Sun-Fire-T1000-hc-topology.xml | 44 - .../Sun-Fire-T200-hc-topology.xml | 57 - usr/src/lib/fm/topo/maps/SUNW,Sun-Fire/Makefile | 34 - .../maps/SUNW,Sun-Fire/Sun-Fire-hc-topology.xml | 52 - usr/src/lib/fm/topo/maps/SUNW,T5140/Makefile | 36 - .../SUNW,T5140/Sun-Blade-T6340-hc-topology.xml | 49 - .../fm/topo/maps/SUNW,T5140/T5140-hc-topology.xml | 49 - .../fm/topo/maps/SUNW,T5140/T5240-hc-topology.xml | 49 - .../fm/topo/maps/SUNW,T5140/T5440-hc-topology.xml | 53 - usr/src/lib/fm/topo/maps/SUNW,USBRDT-5240/Makefile | 33 - .../SUNW,USBRDT-5240/USBRDT-5240-hc-topology.xml | 49 - usr/src/lib/fm/topo/maps/sparc/Makefile | 36 - usr/src/lib/fm/topo/maps/sun4u/Makefile | 34 - .../lib/fm/topo/maps/sun4u/sun4u-hc-topology.xml | 50 - usr/src/lib/fm/topo/maps/sun4v/Makefile | 34 - .../lib/fm/topo/maps/sun4v/sun4v-hc-topology.xml | 36 - usr/src/lib/fm/topo/modules/Makefile | 6 +- .../fm/topo/modules/SUNW,SPARC-Enterprise/Makefile | 32 - .../modules/SUNW,SPARC-Enterprise/ioboard/Makefile | 36 - .../SUNW,SPARC-Enterprise/ioboard/opl_hostbridge.c | 332 -- .../SUNW,SPARC-Enterprise/ioboard/opl_ioboard.c | 351 -- .../SUNW,SPARC-Enterprise/ioboard/opl_topo.h | 92 - usr/src/lib/fm/topo/modules/SUNW,Sun-Fire/Makefile | 32 - .../fm/topo/modules/SUNW,Sun-Fire/ioboard/Makefile | 31 - .../modules/SUNW,Sun-Fire/ioboard/iob_platform.c | 145 - .../lib/fm/topo/modules/sun4/chip/Makefile.chip | 38 - .../fm/topo/modules/sun4/hostbridge/Makefile.hb | 46 - .../lib/fm/topo/modules/sun4/hostbridge/hb_sun4.c | 349 -- .../lib/fm/topo/modules/sun4/hostbridge/hb_sun4.h | 63 - .../lib/fm/topo/modules/sun4/ioboard/Makefile.iob | 46 - usr/src/lib/fm/topo/modules/sun4/ioboard/ioboard.c | 270 -- usr/src/lib/fm/topo/modules/sun4/ioboard/ioboard.h | 66 - .../lib/fm/topo/modules/sun4/pcibus/Makefile.pci | 57 - usr/src/lib/fm/topo/modules/sun4/pcibus/pci_sun4.c | 41 - usr/src/lib/fm/topo/modules/sun4/pcibus/pci_sun4.h | 46 - usr/src/lib/fm/topo/modules/sun4u/Makefile | 32 - usr/src/lib/fm/topo/modules/sun4u/chip/Makefile | 33 - .../lib/fm/topo/modules/sun4u/chip/chip_sun4u.c | 277 -- .../lib/fm/topo/modules/sun4u/hostbridge/Makefile | 32 - .../fm/topo/modules/sun4u/hostbridge/hb_sun4u.c | 183 - usr/src/lib/fm/topo/modules/sun4u/pcibus/Makefile | 30 - .../lib/fm/topo/modules/sun4u/pcibus/pci_sun4u.c | 120 - .../lib/fm/topo/modules/sun4u/pcibus/pci_sun4u.h | 87 - usr/src/lib/fm/topo/modules/sun4v/Makefile | 41 - usr/src/lib/fm/topo/modules/sun4v/chip/Makefile | 45 - .../lib/fm/topo/modules/sun4v/chip/chip_sun4v.c | 428 -- .../lib/fm/topo/modules/sun4v/cpuboard/Makefile | 41 - .../lib/fm/topo/modules/sun4v/cpuboard/cpuboard.c | 554 --- .../modules/sun4v/cpuboard/cpuboard_hostbridge.c | 300 -- .../fm/topo/modules/sun4v/cpuboard/cpuboard_topo.h | 69 - usr/src/lib/fm/topo/modules/sun4v/dimm/Makefile | 61 - .../lib/fm/topo/modules/sun4v/dimm/dimm_sun4v.c | 421 -- .../lib/fm/topo/modules/sun4v/hostbridge/Makefile | 35 - .../fm/topo/modules/sun4v/hostbridge/hb_mdesc.c | 226 - .../fm/topo/modules/sun4v/hostbridge/hb_mdesc.h | 77 - .../lib/fm/topo/modules/sun4v/hostbridge/hb_rcid.c | 123 - .../lib/fm/topo/modules/sun4v/hostbridge/hb_rcid.h | 67 - .../fm/topo/modules/sun4v/hostbridge/hb_sun4v.c | 420 -- .../lib/fm/topo/modules/sun4v/motherboard/Makefile | 39 - .../topo/modules/sun4v/motherboard/motherboard.c | 413 -- usr/src/lib/fm/topo/modules/sun4v/niu/Makefile | 39 - usr/src/lib/fm/topo/modules/sun4v/niu/niu.c | 402 -- usr/src/lib/fm/topo/modules/sun4v/pcibus/Makefile | 32 - .../lib/fm/topo/modules/sun4v/pcibus/pci_sun4v.c | 263 -- .../lib/fm/topo/modules/sun4v/pcibus/pci_sun4v.h | 202 - .../fm/topo/modules/sun4v/platform-cpu/Makefile | 36 - .../lib/fm/topo/modules/sun4v/platform-cpu/cpu.c | 523 --- .../fm/topo/modules/sun4v/platform-cpu/cpu_mdesc.c | 423 -- .../fm/topo/modules/sun4v/platform-cpu/cpu_mdesc.h | 98 - .../fm/topo/modules/sun4v/platform-mem/Makefile | 36 - .../lib/fm/topo/modules/sun4v/platform-mem/mem.c | 697 ---- .../fm/topo/modules/sun4v/platform-mem/mem_mdesc.c | 511 --- .../fm/topo/modules/sun4v/platform-mem/mem_mdesc.h | 100 - usr/src/lib/fm/topo/modules/sun4v/sun4vpi/Makefile | 44 - usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_bay.c | 496 --- usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_cpu.c | 182 - .../lib/fm/topo/modules/sun4v/sun4vpi/pi_defer.c | 239 -- .../lib/fm/topo/modules/sun4v/sun4vpi/pi_generic.c | 128 - .../fm/topo/modules/sun4v/sun4vpi/pi_hostbridge.c | 84 - .../lib/fm/topo/modules/sun4v/sun4vpi/pi_impl.h | 180 - .../lib/fm/topo/modules/sun4v/sun4vpi/pi_ldom.c | 139 - usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_mem.c | 85 - .../lib/fm/topo/modules/sun4v/sun4vpi/pi_meth.c | 520 --- usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_niu.c | 79 - .../lib/fm/topo/modules/sun4v/sun4vpi/pi_pciexrc.c | 562 --- .../lib/fm/topo/modules/sun4v/sun4vpi/pi_subr.c | 1456 ------- usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_top.c | 61 - .../lib/fm/topo/modules/sun4v/sun4vpi/pi_walker.c | 804 ---- .../lib/fm/topo/modules/sun4v/sun4vpi/sun4vpi.c | 287 -- usr/src/lib/fm/topo/modules/sun4v/xaui/Makefile | 38 - usr/src/lib/fm/topo/modules/sun4v/xaui/xaui.c | 539 --- usr/src/lib/fm/topo/modules/sun4v/xaui/xaui.h | 106 - usr/src/lib/fm/topo/modules/sun4v/zambezi/Makefile | 37 - .../lib/fm/topo/modules/sun4v/zambezi/zambezi.c | 188 - .../consolidation-osnet-osnet-message-files.p5m | 6 +- 358 files changed, 14 insertions(+), 73110 deletions(-) delete mode 100644 usr/src/cmd/fm/dicts/SCF.dict delete mode 100644 usr/src/cmd/fm/dicts/SCF.po delete mode 100644 usr/src/cmd/fm/dicts/SUN4.dict delete mode 100644 usr/src/cmd/fm/dicts/SUN4.po delete mode 100644 usr/src/cmd/fm/dicts/SUN4U.dict delete mode 100644 usr/src/cmd/fm/dicts/SUN4U.po delete mode 100644 usr/src/cmd/fm/dicts/SUN4V.dict delete mode 100644 usr/src/cmd/fm/dicts/SUN4V.po delete mode 100644 usr/src/cmd/fm/eversholt/eftinfo/sparc/Makefile delete mode 100644 usr/src/cmd/fm/eversholt/esc/sparc/Makefile delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/Makefile delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4/Makefile.sun4 delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4/fire.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4u/Makefile delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4u/oberon.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4u/psycho.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4u/schizo.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4u/tomatillo.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4u/xmits.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/Makefile delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/gcpu.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/gmem.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2niu_xaui.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2niu_xfp.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2piu.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/sp.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/vfncx.esc delete mode 100644 usr/src/cmd/fm/eversholt/files/sparc/sun4v/zambezi.esc delete mode 100644 usr/src/cmd/fm/eversholt/native/sparc/Makefile delete mode 100644 usr/src/cmd/fm/fmadm/sparc/Makefile delete mode 100644 usr/src/cmd/fm/fmd/sparc/Makefile delete mode 100644 usr/src/cmd/fm/fmdump/sparc/Makefile delete mode 100644 usr/src/cmd/fm/fminject/sparc/Makefile delete mode 100644 usr/src/cmd/fm/fmstat/sparc/Makefile delete mode 100644 usr/src/cmd/fm/fmtopo/sparc/Makefile delete mode 100644 usr/src/cmd/fm/ipmitopo/sparc/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-CP3060/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-CP3060/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-CP3060/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-CP3260/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-CP3260/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-CP3260/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-T5220/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-T5220/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-T5220/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-T5440/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-T5440/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Netra-T5440/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/cpumem-retire/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/cpumem-retire/cpumem-retire.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/event-transport.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/ex_dscp.c delete mode 100644 usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/ex_dscp.h delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Blade-T6300/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Blade-T6300/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Blade-T6300/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Blade-T6320/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Blade-T6320/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Blade-T6320/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Fire-T200/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Fire-T200/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,Sun-Fire-T200/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,T5140/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,T5140/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,T5140/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/SUNW,USBRDT-5240/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,USBRDT-5240/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/SUNW,USBRDT-5240/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/common/cpumem-retire/cma_cache.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/Makefile.cpumem delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_Lxcache.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_bank.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_bank.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_cpu.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_cpu.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_cpuerr.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_dimm.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_dimm.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_fmri.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_fmri.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_list.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_list.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_main.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_mem.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_mem.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_memerr.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_page.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_page.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_pageerr.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_state.c delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_state.h delete mode 100644 usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cmd_util.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4u/USII-io-diagnosis/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4u/USII-io-diagnosis/USII-io-diagnosis.conf delete mode 100644 usr/src/cmd/fm/modules/sun4u/USII-io-diagnosis/iod_main.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_Lxcache.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_Lxcacheerr.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_cpu_arch.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_dp.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_dp.h delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_dp_page.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_dp_page.h delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_dperr.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_ecache.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_ecache.h delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_hc_opl.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_memerr_arch.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_opl.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_opl.h delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_oplerr.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cpumem-diagnosis.conf delete mode 100644 usr/src/cmd/fm/modules/sun4u/datapath-retire/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4u/datapath-retire/cda.h delete mode 100644 usr/src/cmd/fm/modules/sun4u/datapath-retire/cda_cpu.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/datapath-retire/cda_main.c delete mode 100644 usr/src/cmd/fm/modules/sun4u/datapath-retire/datapath-retire.conf delete mode 100644 usr/src/cmd/fm/modules/sun4v/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-diagnosis/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-diagnosis/cmd_branch.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-diagnosis/cmd_branch.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-diagnosis/cmd_cpu_arch.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-diagnosis/cmd_hc_sun4v.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-diagnosis/cmd_hc_sun4v.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-diagnosis/cmd_memerr_arch.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-diagnosis/cpumem-diagnosis.conf delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-retire/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-retire/cma_cpu_sun4v.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-retire/cma_page_sun4v.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/cpumem-retire/cpumem-retire.conf delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/Makefile.etm delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm.conf delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_ckpt.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_ckpt.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_etm_proto.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_filter.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_filter.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_impl.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_iosvc.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_xport_api.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/etm/etm_xport_api_dd.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/Makefile delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/generic-mem.conf delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_dimm.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_dimm.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_fmri.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_fmri.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_main.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_mem.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_mem.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_memerr.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_page.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_page.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_state.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_state.h delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_util.c delete mode 100644 usr/src/cmd/fm/modules/sun4v/generic-mem/gmem_util.h delete mode 100644 usr/src/cmd/fm/notify/smtp-notify/sparc/Makefile delete mode 100644 usr/src/cmd/fm/notify/snmp-notify/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/cpu/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/cpu/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/dev/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/dev/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/fmd/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/fmd/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/hc/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/hc/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/legacy-hc/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/legacy-hc/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/mem/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/mem/sparc/mem_disc.c delete mode 100644 usr/src/cmd/fm/schemes/mem/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/mod/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/mod/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/pkg/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/pkg/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/svc/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/svc/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/sw/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/sw/sparcv9/Makefile delete mode 100644 usr/src/cmd/fm/schemes/zfs/sparc/Makefile delete mode 100644 usr/src/cmd/fm/schemes/zfs/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libdiagcode/sparc/Makefile delete mode 100644 usr/src/lib/fm/libdiagcode/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libdiskstatus/sparc/Makefile delete mode 100644 usr/src/lib/fm/libdiskstatus/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libfmd_adm/sparc/Makefile delete mode 100644 usr/src/lib/fm/libfmd_adm/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libfmd_agent/sparc/Makefile delete mode 100644 usr/src/lib/fm/libfmd_agent/sparc/fmd_agent_sparc.c delete mode 100644 usr/src/lib/fm/libfmd_agent/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libfmd_log/sparc/Makefile delete mode 100644 usr/src/lib/fm/libfmd_log/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libfmd_msg/sparc/Makefile delete mode 100644 usr/src/lib/fm/libfmd_msg/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libfmd_snmp/sparc/Makefile delete mode 100644 usr/src/lib/fm/libfmd_snmp/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libfmevent/sparc/Makefile delete mode 100644 usr/src/lib/fm/libfmevent/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libfmnotify/sparc/Makefile delete mode 100644 usr/src/lib/fm/libfmnotify/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libldom/Makefile delete mode 100644 usr/src/lib/fm/libldom/Makefile.com delete mode 100644 usr/src/lib/fm/libldom/sparc/Makefile delete mode 100644 usr/src/lib/fm/libldom/sparc/ldmsvcs_utils.c delete mode 100644 usr/src/lib/fm/libldom/sparc/ldmsvcs_utils.h delete mode 100644 usr/src/lib/fm/libldom/sparc/ldom.c delete mode 100644 usr/src/lib/fm/libldom/sparc/ldom.h delete mode 100644 usr/src/lib/fm/libldom/sparc/ldom_alloc.c delete mode 100644 usr/src/lib/fm/libldom/sparc/ldom_alloc.h delete mode 100644 usr/src/lib/fm/libldom/sparc/ldom_utils.c delete mode 100644 usr/src/lib/fm/libldom/sparc/ldom_utils.h delete mode 100644 usr/src/lib/fm/libldom/sparc/ldom_xmpp_client.c delete mode 100644 usr/src/lib/fm/libldom/sparc/ldom_xmpp_client.h delete mode 100644 usr/src/lib/fm/libldom/sparc/mapfile-vers delete mode 100644 usr/src/lib/fm/libldom/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libmdesc/Makefile delete mode 100644 usr/src/lib/fm/libmdesc/Makefile.com delete mode 100644 usr/src/lib/fm/libmdesc/common/mapfile-vers delete mode 100644 usr/src/lib/fm/libmdesc/sparc/Makefile delete mode 100644 usr/src/lib/fm/libmdesc/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/libseslog/sparc/Makefile delete mode 100644 usr/src/lib/fm/libseslog/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/topo/libtopo/sparc/Makefile delete mode 100644 usr/src/lib/fm/topo/libtopo/sparcv9/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Netra-CP3060/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Netra-CP3060/Netra-CP3060-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Netra-CP3260/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Netra-CP3260/Netra-CP3260-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Netra-T5220/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Netra-T5220/Netra-T5220-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Netra-T5440/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Netra-T5440/Netra-T5440-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,SPARC-Enterprise-T5120/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,SPARC-Enterprise-T5120/SPARC-Enterprise-T5120-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,SPARC-Enterprise-T5120/SPARC-Enterprise-T5220-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,SPARC-Enterprise/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,SPARC-Enterprise/SPARC-Enterprise-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Blade-T6300/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Blade-T6300/Sun-Blade-T6300-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Blade-T6320/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Blade-T6320/Sun-Blade-T6320-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Fire-T200/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Fire-T200/Netra-T2000-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Fire-T200/SPARC-Enterprise-T1000-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Fire-T200/SPARC-Enterprise-T2000-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Fire-T200/Sun-Fire-T1000-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Fire-T200/Sun-Fire-T200-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Fire/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,Sun-Fire/Sun-Fire-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,T5140/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,T5140/Sun-Blade-T6340-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,T5140/T5140-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,T5140/T5240-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,T5140/T5440-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,USBRDT-5240/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/SUNW,USBRDT-5240/USBRDT-5240-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/sparc/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/sun4u/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/sun4u/sun4u-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/maps/sun4v/Makefile delete mode 100644 usr/src/lib/fm/topo/maps/sun4v/sun4v-hc-topology.xml delete mode 100644 usr/src/lib/fm/topo/modules/SUNW,SPARC-Enterprise/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/SUNW,SPARC-Enterprise/ioboard/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/SUNW,SPARC-Enterprise/ioboard/opl_hostbridge.c delete mode 100644 usr/src/lib/fm/topo/modules/SUNW,SPARC-Enterprise/ioboard/opl_ioboard.c delete mode 100644 usr/src/lib/fm/topo/modules/SUNW,SPARC-Enterprise/ioboard/opl_topo.h delete mode 100644 usr/src/lib/fm/topo/modules/SUNW,Sun-Fire/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/SUNW,Sun-Fire/ioboard/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/SUNW,Sun-Fire/ioboard/iob_platform.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4/chip/Makefile.chip delete mode 100644 usr/src/lib/fm/topo/modules/sun4/hostbridge/Makefile.hb delete mode 100644 usr/src/lib/fm/topo/modules/sun4/hostbridge/hb_sun4.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4/hostbridge/hb_sun4.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4/ioboard/Makefile.iob delete mode 100644 usr/src/lib/fm/topo/modules/sun4/ioboard/ioboard.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4/ioboard/ioboard.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4/pcibus/Makefile.pci delete mode 100644 usr/src/lib/fm/topo/modules/sun4/pcibus/pci_sun4.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4/pcibus/pci_sun4.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4u/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4u/chip/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4u/chip/chip_sun4u.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4u/hostbridge/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4u/hostbridge/hb_sun4u.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4u/pcibus/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4u/pcibus/pci_sun4u.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4u/pcibus/pci_sun4u.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/chip/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/chip/chip_sun4v.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/cpuboard/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/cpuboard/cpuboard.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/cpuboard/cpuboard_hostbridge.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/cpuboard/cpuboard_topo.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/dimm/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/dimm/dimm_sun4v.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/hostbridge/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/hostbridge/hb_mdesc.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/hostbridge/hb_mdesc.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/hostbridge/hb_rcid.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/hostbridge/hb_rcid.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/hostbridge/hb_sun4v.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/motherboard/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/motherboard/motherboard.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/niu/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/niu/niu.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/pcibus/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/pcibus/pci_sun4v.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/pcibus/pci_sun4v.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/platform-cpu/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/platform-cpu/cpu.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/platform-cpu/cpu_mdesc.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/platform-cpu/cpu_mdesc.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/platform-mem/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/platform-mem/mem.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/platform-mem/mem_mdesc.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/platform-mem/mem_mdesc.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_bay.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_cpu.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_defer.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_generic.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_hostbridge.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_impl.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_ldom.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_mem.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_meth.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_niu.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_pciexrc.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_subr.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_top.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/pi_walker.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/sun4vpi/sun4vpi.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/xaui/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/xaui/xaui.c delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/xaui/xaui.h delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/zambezi/Makefile delete mode 100644 usr/src/lib/fm/topo/modules/sun4v/zambezi/zambezi.c diff --git a/usr/src/cmd/fm/dicts/Makefile b/usr/src/cmd/fm/dicts/Makefile index 93e0303f83..223a770197 100644 --- a/usr/src/cmd/fm/dicts/Makefile +++ b/usr/src/cmd/fm/dicts/Makefile @@ -20,6 +20,7 @@ # # # Copyright (c) 2004, 2010, Oracle and/or its affiliates. All rights reserved. +# Copryight 2022 Garrett D'Amore # include ../../Makefile.cmd @@ -46,21 +47,10 @@ i386_DCNAMES = \ INTEL \ GMCA -sparc_DCNAMES = \ - SCF \ - SUN4 \ - SUN4U \ - SUN4V - DCNAMES = \ $(common_DCNAMES) \ $($(MACH)_DCNAMES) -ALLDCNAMES = \ - $(common_DCNAMES) \ - $(sparc_DCNAMES) \ - $(i386_DCNAMES) - DCFILES = $(DCNAMES:%=%.dict) POFILES = $(DCNAMES:%=%.po) MOFILES = $(DCNAMES:%=%.mo) @@ -71,17 +61,16 @@ ROOTLCDIR = $(ROOTLIB)/locale/C/LC_MESSAGES ROOTDCFILES = $(DCNAMES:%=$(ROOTDCDIR)/%.dict) ROOTPOFILES = $(DCNAMES:%=$(ROOTLCDIR)/%.po) ROOTMOFILES = $(DCNAMES:%=$(ROOTLCDIR)/%.mo) -ROOTALLPOFILES = $(ALLDCNAMES:%=$(ROOTLCDIR)/%.po) FILEMODE = 0444 -$(ROOTALLPOFILES) := FILEMODE = 0644 +$(ROOTPOFILES) := FILEMODE = 0644 DICTCK = ../scripts/dictck DICTCKFLAGS = -b ../scripts/buildcode all: $(MOFILES) -_msg: $(ROOTALLPOFILES) +_msg: $(ROOTPOFILES) $(ROOTDCDIR): $(INS.dir) @@ -115,4 +104,4 @@ clobber: $(RM) $(MOFILES) install: all $(ROOTDCDIR) $(ROOTLCDIR) \ - $(ROOTDCFILES) $(ROOTALLPOFILES) $(ROOTMOFILES) + $(ROOTDCFILES) $(ROOTPOFILES) $(ROOTMOFILES) diff --git a/usr/src/cmd/fm/dicts/SCF.dict b/usr/src/cmd/fm/dicts/SCF.dict deleted file mode 100644 index 6ba8814343..0000000000 --- a/usr/src/cmd/fm/dicts/SCF.dict +++ /dev/null @@ -1,198 +0,0 @@ -# -# Copyright 2007 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -#ident "%Z%%M% %I% %E% SMI" -# -# DO NOT EDIT -- this file is generated by the Event Registry. -# - -FMDICT: name=SCF version=1 maxkey=1 dictid=0x5346 - -fault.chassis.SPARC-Enterprise.if.fe-asic-clk=1 -fault.chassis.SPARC-Enterprise.if.fe-clk-cable=2 -fault.chassis.SPARC-Enterprise.asic.clk.fe=3 -fault.chassis.SPARC-Enterprise.asic.clk.test=4 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.fe=11 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.fe=12 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.strand.fe=13 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.se=14 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.se=15 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.se-offlinereq=16 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.strand.se=17 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.ce=18 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.ce=19 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.ce-offlinereq=20 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.way.ce=21 -upset.chassis.SPARC-Enterprise.cpu.SPARC64-VI.fe=22 -upset.chassis.SPARC-Enterprise.cpu.SPARC64-VI.fe-unexpected-trap=23 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.se-tmo=24 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.se-uncertain=25 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.ce-warn=26 -fault.chassis.SPARC-Enterprise.memory.fe=31 -fault.chassis.SPARC-Enterprise.memory.block.ue=32 -fault.chassis.SPARC-Enterprise.memory.block.mirror.ue=33 -fault.chassis.SPARC-Enterprise.memory.block.pce=34 -fault.chassis.SPARC-Enterprise.memory.dimm.pce=35 -fault.chassis.SPARC-Enterprise.memory.bank.err=36 -fault.chassis.SPARC-Enterprise.asic.flp.fe=41 -fault.chassis.SPARC-Enterprise.asic.flp.ce=42 -upset.chassis.SPARC-Enterprise.io.disk.boot=50 -fault.chassis.SPARC-Enterprise.if.fe-ioc-flp=51 -fault.chassis.SPARC-Enterprise.asic.ioc.fe=52 -upset.chassis.SPARC-Enterprise.asic.ioc.fe-tmo-dma=53 -fault.chassis.SPARC-Enterprise.asic.ioc.ch.fe=54 -fault.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.fe=55 -fault.chassis.SPARC-Enterprise.io.pciex.card.fe=56 -fault.chassis.SPARC-Enterprise.io.pci.card.fe=57 -fault.chassis.SPARC-Enterprise.io.pciex.bridge.fe=58 -fault.chassis.SPARC-Enterprise.io.pciex.switch.fe=59 -fault.chassis.SPARC-Enterprise.io.pci.gbe.fe=60 -fault.chassis.SPARC-Enterprise.io.pci.sas.fe=61 -fault.chassis.SPARC-Enterprise.if.se-ioc-flp=62 -fault.chassis.SPARC-Enterprise.asic.ioc.ch.se=63 -fault.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.se=64 -fault.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.se-no-credit-pci=65 -fault.chassis.SPARC-Enterprise.io.pciex.card.se=66 -fault.chassis.SPARC-Enterprise.io.pci.card.se=67 -fault.chassis.SPARC-Enterprise.io.pciex.bridge.se=68 -fault.chassis.SPARC-Enterprise.io.pciex.switch.se=69 -fault.chassis.SPARC-Enterprise.if.ce-ioc-flp=70 -fault.chassis.SPARC-Enterprise.asic.ioc.ch.ce=71 -fault.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.ce=72 -upset.chassis.SPARC-Enterprise.asic.ioc.ch.boot=73 -upset.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.boot=74 -upset.chassis.SPARC-Enterprise.io.pci.gbe.boot=75 -upset.chassis.SPARC-Enterprise.io.pci.card.boot=76 -upset.chassis.SPARC-Enterprise.io.pciex.card.boot=77 -upset.chassis.SPARC-Enterprise.io.pciex.bridge.boot=78 -upset.chassis.SPARC-Enterprise.io.pciex.switch.boot=79 -upset.chassis.SPARC-Enterprise.io.pci.sas.boot=80 -fault.chassis.jtag.device=81 -fault.chassis.jtag.device-internal=82 -fault.chassis.i2c.device=83 -fault.chassis.i2c.device-internal=84 -fault.chassis.SPARC-Enterprise.asic.mac.fe=91 -fault.chassis.SPARC-Enterprise.asic.mac.bank.fe=92 -fault.chassis.SPARC-Enterprise.asic.mac.se=93 -fault.chassis.SPARC-Enterprise.asic.mac.bank.se=94 -fault.chassis.SPARC-Enterprise.asic.mac.ce=95 -fault.chassis.SPARC-Enterprise.asic.mac.bank.ce=96 -fault.chassis.SPARC-Enterprise.madm.io.se=101 -fault.chassis.SPARC-Enterprise.madm.io.fe=102 -fault.chassis.SPARC-Enterprise.if.fe-mbc-sc=111 -fault.chassis.SPARC-Enterprise.asic.mbc.fe=112 -fault.chassis.SPARC-Enterprise.if.se-mbc-sc=113 -fault.chassis.SPARC-Enterprise.if.se-mbc-xscf=114 -fault.chassis.SPARC-Enterprise.asic.mbc.se=115 -fault.chassis.SPARC-Enterprise.asic.mbc.se-dma=116 -fault.chassis.SPARC-Enterprise.asic.mbc.se-dma-dscp=117 -fault.chassis.SPARC-Enterprise.asic.mbc.se-cmd=118 -fault.chassis.SPARC-Enterprise.if.ce-mbc-sc=119 -fault.chassis.SPARC-Enterprise.asic.mbc.ce=120 -fault.chassis.SPARC-Enterprise.asic.mbc.test=121 -fault.chassis.SPARC-Enterprise.asic.mac.power.fail=131 -fault.chassis.SPARC-Enterprise.asic.sc.power.fail=132 -fault.chassis.SPARC-Enterprise.asic.xb.power.fail=133 -fault.chassis.SPARC-Enterprise.asic.ioc.power.fail=134 -fault.chassis.SPARC-Enterprise.asic.clk.power.fail=135 -fault.chassis.SPARC-Enterprise.asic.cpu.power.fail=136 -fault.chassis.SPARC-Enterprise.asic.flp.power.fail=137 -fault.chassis.SPARC-Enterprise.asic.mbc.power.fail=138 -fault.chassis.SPARC-Enterprise.asic.power.fail=139 -fault.chassis.power.warning=140 -fault.chassis.power.undervoltage=141 -fault.chassis.power.power-off=142 -fault.chassis.device.fail=143 -fault.chassis.device.misconfig=144 -fault.chassis.device.missing=145 -fault.chassis.device.inserted=146 -fault.chassis.device.removed=147 -fault.chassis.env.power.loss=148 -fault.chassis.env.power.ups=149 -fault.chassis.SPARC-Enterprise.rci=151 -fault.chassis.SPARC-Enterprise.asic.sc.fe-multicmu=160 -fault.chassis.SPARC-Enterprise.if.fe-cpu-sc=161 -fault.chassis.SPARC-Enterprise.if.fe-sc-cpu=162 -fault.chassis.SPARC-Enterprise.if.fe-sc-xb=163 -fault.chassis.SPARC-Enterprise.if.fe-mac-sc=165 -fault.chassis.SPARC-Enterprise.if.fe-sc-mac=166 -fault.chassis.SPARC-Enterprise.if.fe-macbank-sc=167 -fault.chassis.SPARC-Enterprise.if.fe-ioc-sc=168 -fault.chassis.SPARC-Enterprise.if.fe-sc-ioc=169 -fault.chassis.SPARC-Enterprise.if.fe-sc-sc=170 -fault.chassis.SPARC-Enterprise.asic.sc.fe=171 -fault.chassis.SPARC-Enterprise.asic.sc.se=172 -fault.chassis.SPARC-Enterprise.if.ce-cpu-sc=173 -fault.chassis.SPARC-Enterprise.if.ce-sc-xb=174 -fault.chassis.SPARC-Enterprise.if.ce-mac-sc=175 -fault.chassis.SPARC-Enterprise.if.ce-ioc-sc=176 -fault.chassis.SPARC-Enterprise.if.ce-sc-sc=177 -fault.chassis.SPARC-Enterprise.asic.sc.ce=178 -fault.chassis.SPARC-Enterprise.asic.sc.ce-l2tagcpu=179 -fault.chassis.SPARC-Enterprise.asic.sc.test=180 -defect.chassis.software=181 -upset.chassis.domain.panic=182 -upset.chassis.domain.config=183 -upset.chassis.domain.post=184 -upset.chassis.domain.keepalive.msg-fail=185 -upset.chassis.domain.tty-overflow=186 -upset.chassis.domain.keepalive.panic-fail=187 -upset.chassis.domain.keepalive.xir-fail=188 -upset.chassis.domain.keepalive.reset-fail=189 -fault.chassis.device.fan.tooslow=191 -fault.chassis.device.fan.speedchange=192 -fault.chassis.env.temp.under=193 -fault.chassis.env.temp.over=194 -fault.chassis.env.temp.over-warn=195 -fault.chassis.env.temp.over-fail=196 -fault.chassis.SPARC-Enterprise.if.fe-ioc-xb=201 -fault.chassis.SPARC-Enterprise.if.fe-xb-ioc=202 -fault.chassis.SPARC-Enterprise.if.fe-xb-xbucable=203 -fault.chassis.SPARC-Enterprise.if.fe-xb-xb=204 -upset.chassis.SPARC-Enterprise.if.fe-xb=205 -fault.chassis.SPARC-Enterprise.asic.xb.fe=206 -fault.chassis.SPARC-Enterprise.if.ce-ioc-xb=207 -fault.chassis.SPARC-Enterprise.if.ce-xb-xbucable=208 -fault.chassis.SPARC-Enterprise.if.ce-xb-xb=209 -fault.chassis.SPARC-Enterprise.asic.xb.ce=210 -fault.chassis.SPARC-Enterprise.asic.xb.test=211 -fault.chassis.SPARC-Enterprise.asic.xb.fe-multicmu=212 -fault.chassis.SPARC-Enterprise.xscfu=221 -fault.chassis.device.mismatch=222 -upset.chassis.SPARC-Enterprise.xscfu=223 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.fe=224 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.fe=225 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.strand.fe=226 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.se=227 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.se=228 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.se-offlinereq=229 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.strand.se=230 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.ce=231 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.ce=232 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.ce-offlinereq=233 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.way.ce=234 -upset.chassis.SPARC-Enterprise.cpu.SPARC64-VII.fe=235 -upset.chassis.SPARC-Enterprise.cpu.SPARC64-VII.fe-unexpected-trap=236 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.se-tmo=237 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.se-uncertain=238 -fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.ce-warn=239 diff --git a/usr/src/cmd/fm/dicts/SCF.po b/usr/src/cmd/fm/dicts/SCF.po deleted file mode 100644 index 160a515fdc..0000000000 --- a/usr/src/cmd/fm/dicts/SCF.po +++ /dev/null @@ -1,2713 +0,0 @@ -# -# Copyright 2007 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# DO NOT EDIT -- this file is generated by the Event Registry. -# -# -# code: SCF-8000-1D -# keys: fault.chassis.SPARC-Enterprise.if.fe-asic-clk -# -msgid "SCF-8000-1D.type" -msgstr "Fault" -msgid "SCF-8000-1D.severity" -msgstr "Critical" -msgid "SCF-8000-1D.description" -msgstr "A fatal clock distribution error was detected by an ASIC or a CPU chip.\n Refer to %s for more information." -msgid "SCF-8000-1D.response" -msgstr "An attempt will be made to deconfigure the faulty components after one or more domains are reset.\n" -msgid "SCF-8000-1D.impact" -msgstr "One or more domains will be reset. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8000-1D.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-2Y -# keys: fault.chassis.SPARC-Enterprise.if.fe-clk-cable -# -msgid "SCF-8000-2Y.type" -msgstr "Fault" -msgid "SCF-8000-2Y.severity" -msgstr "Critical" -msgid "SCF-8000-2Y.description" -msgstr "A Clock chip has detected a lack of connectivity between the base cabinet and the expansion cabinet.\n Refer to %s for more information." -msgid "SCF-8000-2Y.response" -msgstr "The entire platform is reset and the active Clock Units are deconfigured during recovery.\n" -msgid "SCF-8000-2Y.impact" -msgstr "The entire platform is reset and the active Clock Units are deconfigured during recovery.\n" -msgid "SCF-8000-2Y.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-33 -# keys: fault.chassis.SPARC-Enterprise.asic.clk.fe -# -msgid "SCF-8000-33.type" -msgstr "Fault" -msgid "SCF-8000-33.severity" -msgstr "Critical" -msgid "SCF-8000-33.description" -msgstr "A fatal error was detected within a Clock chip.\n Refer to %s for more information." -msgid "SCF-8000-33.response" -msgstr "The platform will be reset. If there is redundant clock capability, an attempt will be made to deconfigure \nthe active Clock Unit from service. \n" -msgid "SCF-8000-33.impact" -msgstr "If the platform lacks redundant clock capability, the platform will be powered down and will not\npower up. If the platform has redundant clock capability, the platform will be reset and the\nfaulty Clock Unit will be deconfigured during recovery.\n" -msgid "SCF-8000-33.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-4S -# keys: fault.chassis.SPARC-Enterprise.asic.clk.test -# -msgid "SCF-8000-4S.type" -msgstr "Fault" -msgid "SCF-8000-4S.severity" -msgstr "Critical" -msgid "SCF-8000-4S.description" -msgstr "Fault was detected during poweron self-test, either within a Clock chip with within one of the external\ninterfaces of a Clock chip.\n Refer to %s for more information." -msgid "SCF-8000-4S.response" -msgstr "An attempt will be made to remove the affected components from service. Please consult the detail \nsection of the knowledge article for additional information.\n" -msgid "SCF-8000-4S.impact" -msgstr "The entire platform is reset. If the platform lacks redundant clock capability, the platform will be \npowered down and will not power up. If the platform has redundant clock capability, the platform will be \nreset and the faulty Clock Unit will be deconfigured during recovery.\n" -msgid "SCF-8000-4S.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-CJ -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.fe -# -msgid "SCF-8000-CJ.type" -msgstr "Fault" -msgid "SCF-8000-CJ.severity" -msgstr "Critical" -msgid "SCF-8000-CJ.description" -msgstr "An internal fatal error within a CPU chip was detected.\n Refer to %s for more information." -msgid "SCF-8000-CJ.response" -msgstr "The domain using this CPU will be reset and the CPU chip will be deconfigured.\n" -msgid "SCF-8000-CJ.impact" -msgstr "The CPU chip will be deconfigured after the domain is reset.\n" -msgid "SCF-8000-CJ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-DC -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.fe -# -msgid "SCF-8000-DC.type" -msgstr "Fault" -msgid "SCF-8000-DC.severity" -msgstr "Critical" -msgid "SCF-8000-DC.description" -msgstr "An internal fatal error within a core on a CPU chip was detected.\n Refer to %s for more information." -msgid "SCF-8000-DC.response" -msgstr "The domain using this CPU will be reset and the core will be deconfigured.\n" -msgid "SCF-8000-DC.impact" -msgstr "The domain using this CPU chip is reset.\n" -msgid "SCF-8000-DC.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-EQ -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.strand.fe -# -msgid "SCF-8000-EQ.type" -msgstr "Fault" -msgid "SCF-8000-EQ.severity" -msgstr "Critical" -msgid "SCF-8000-EQ.description" -msgstr "An internal fatal error within a strand on a CPU chip was detected.\n Refer to %s for more information." -msgid "SCF-8000-EQ.response" -msgstr "The domain using this CPU will be reset and the strand will be deconfigured.\n" -msgid "SCF-8000-EQ.impact" -msgstr "The domain using this CPU chip is reset.\n" -msgid "SCF-8000-EQ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-F4 -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.se -# -msgid "SCF-8000-F4.type" -msgstr "Fault" -msgid "SCF-8000-F4.severity" -msgstr "Major" -msgid "SCF-8000-F4.description" -msgstr "An internal non-fatal uncorrectable error within a CPU chip has been detected.\n Refer to %s for more information." -msgid "SCF-8000-F4.response" -msgstr "The CPU chip will be deconfigured after the platform is power cycled or after the domain reboots \nor after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8000-F4.impact" -msgstr "The non-fatal uncorrectable error may cause domain to panic. The CPU chip will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8000-F4.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-GR -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.se -# -msgid "SCF-8000-GR.type" -msgstr "Fault" -msgid "SCF-8000-GR.severity" -msgstr "Major" -msgid "SCF-8000-GR.description" -msgstr "A non-fatal uncorrectable error associated with a core on a CPU chip has been detected.\n Refer to %s for more information." -msgid "SCF-8000-GR.response" -msgstr "The domain software will attempt to offline the core on the CPU chip.\n" -msgid "SCF-8000-GR.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. If the domain\ndoes not panic, the domain software will attempt to offline the core on the CPU chip.\nThe core of the CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8000-GR.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-H3 -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.se-offlinereq -# -msgid "SCF-8000-H3.type" -msgstr "Fault" -msgid "SCF-8000-H3.severity" -msgstr "Major" -msgid "SCF-8000-H3.description" -msgstr "When a non-fatal uncorrectable error occurs on a core on a CPU chip, domain software attempts to\noffline the core. This fault occurs when the number of offline attempts has exceeded an\nacceptable threshold.\n Refer to %s for more information." -msgid "SCF-8000-H3.response" -msgstr "Future non-fatal uncorrectable errors for this core on a CPU chip will not be recorded on the XSCF.\n" -msgid "SCF-8000-H3.impact" -msgstr "The uncorrectable error trap may cause the domain to panic.\n" -msgid "SCF-8000-H3.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-JY -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.strand.se -# -msgid "SCF-8000-JY.type" -msgstr "Fault" -msgid "SCF-8000-JY.severity" -msgstr "Major" -msgid "SCF-8000-JY.description" -msgstr "A non-fatal uncorrectable error has been detected on a strand on a CPU chip.\n Refer to %s for more information." -msgid "SCF-8000-JY.response" -msgstr "The strand on the CPU chip is deconfigured.\n" -msgid "SCF-8000-JY.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic.\n" -msgid "SCF-8000-JY.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-KD -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.ce -# -msgid "SCF-8000-KD.type" -msgstr "Fault" -msgid "SCF-8000-KD.severity" -msgstr "Major" -msgid "SCF-8000-KD.description" -msgstr "The number of correctable errors associated with a CPU chip has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8000-KD.response" -msgstr "The CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8000-KD.impact" -msgstr "No immediate impact. The CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8000-KD.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-LH -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.ce -# -msgid "SCF-8000-LH.type" -msgstr "Fault" -msgid "SCF-8000-LH.severity" -msgstr "Major" -msgid "SCF-8000-LH.description" -msgstr "The number of correctable errors associated with a core on a CPU chip have exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8000-LH.response" -msgstr "A request is sent to the domain software to attempt to offline the core on the CPU chip.\nThe core of the CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8000-LH.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8000-LH.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-MA -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.ce-offlinereq -# -msgid "SCF-8000-MA.type" -msgstr "Fault" -msgid "SCF-8000-MA.severity" -msgstr "Major" -msgid "SCF-8000-MA.description" -msgstr "The number of correctable errors on a core on a CPU chip has exceeded an acceptable threshold. \nThis fault occurs when the number of offline attempts has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8000-MA.response" -msgstr "Future correctable errors for this core on a CPU chip will not be recorded on the XSCF.\n" -msgid "SCF-8000-MA.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8000-MA.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-NP -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.way.ce -# -msgid "SCF-8000-NP.type" -msgstr "Fault" -msgid "SCF-8000-NP.severity" -msgstr "Minor" -msgid "SCF-8000-NP.description" -msgstr "The number of correctable errors within a way of a CPU chip's L2 cache has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8000-NP.response" -msgstr "The way of the CPU chip's cache is deconfigured. The performance of the CPU chip is reduced.\n" -msgid "SCF-8000-NP.impact" -msgstr "There is a performance loss for the CPU chip.\n" -msgid "SCF-8000-NP.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-P5 -# keys: upset.chassis.SPARC-Enterprise.cpu.SPARC64-VI.fe -# -msgid "SCF-8000-P5.type" -msgstr "Upset" -msgid "SCF-8000-P5.severity" -msgstr "Critical" -msgid "SCF-8000-P5.description" -msgstr "A hard-to-diagnose problem was detected by the CPU chip.\n Refer to %s for more information." -msgid "SCF-8000-P5.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8000-P5.impact" -msgstr "The domain may drop to the OpenBoot PROM 'OK' prompt.\n" -msgid "SCF-8000-P5.action" -msgstr "The platform administrator should check to see if any other hardware failure has occurred on the platform.\nIf the problem occurs while running OpenBoot PROM, then the platform administrator should check to make sure that \nthe OpenBoot PROM environment variables have not been set incorrectly. If neither of these courses of action \nprovide a resolution, then the platform administrator should schedule a service action.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-QS -# keys: upset.chassis.SPARC-Enterprise.cpu.SPARC64-VI.fe-unexpected-trap -# -msgid "SCF-8000-QS.type" -msgstr "upset" -msgid "SCF-8000-QS.severity" -msgstr "Critical" -msgid "SCF-8000-QS.description" -msgstr "An unexpected trap with some unknown cause was detected by a CPU chip during POST.\n Refer to %s for more information." -msgid "SCF-8000-QS.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8000-QS.impact" -msgstr "The domain is reset.\n" -msgid "SCF-8000-QS.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-RJ -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.se-tmo -# -msgid "SCF-8000-RJ.type" -msgstr "Fault" -msgid "SCF-8000-RJ.severity" -msgstr "Major" -msgid "SCF-8000-RJ.description" -msgstr "An internal non-fatal uncorrectable error has been detected within the CPU chip.\n Refer to %s for more information." -msgid "SCF-8000-RJ.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8000-RJ.impact" -msgstr "The non-fatal uncorrectable error may cause the domain to panic.\n" -msgid "SCF-8000-RJ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-SE -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.se-uncertain -# -msgid "SCF-8000-SE.type" -msgstr "Fault" -msgid "SCF-8000-SE.severity" -msgstr "Major" -msgid "SCF-8000-SE.description" -msgstr "An internal non-fatal uncorrectable error has been detected within the CPU chip.\n Refer to %s for more information." -msgid "SCF-8000-SE.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8000-SE.impact" -msgstr "The non-fatal uncorrectable error may cause the domain to panic.\n" -msgid "SCF-8000-SE.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-TX -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VI.core.ce-warn -# -msgid "SCF-8000-TX.type" -msgstr "Fault" -msgid "SCF-8000-TX.severity" -msgstr "Minor" -msgid "SCF-8000-TX.description" -msgstr "The number of correctable errors associated with a CPU chip has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8000-TX.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8000-TX.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8000-TX.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8000-YC -# keys: fault.chassis.SPARC-Enterprise.memory.fe -# -msgid "SCF-8000-YC.type" -msgstr "Fault" -msgid "SCF-8000-YC.severity" -msgstr "Major" -msgid "SCF-8000-YC.description" -msgstr "A fatal error in a DIMM was detected by POST.\n Refer to %s for more information." -msgid "SCF-8000-YC.response" -msgstr "The memory associated with the memory bank that contains this\nDIMM is deconfigured.\n" -msgid "SCF-8000-YC.impact" -msgstr "POST is restarted after the memory associated with the memory bank that contains\nthis DIMM has been deconfigured.\n" -msgid "SCF-8000-YC.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-0Q -# keys: fault.chassis.SPARC-Enterprise.memory.block.ue -# -msgid "SCF-8001-0Q.type" -msgstr "Fault" -msgid "SCF-8001-0Q.severity" -msgstr "Major" -msgid "SCF-8001-0Q.description" -msgstr "An uncorrectable memory error (UE) has been detected.\n Refer to %s for more information." -msgid "SCF-8001-0Q.response" -msgstr "The 64MB of memory containing the memory that caused the UE will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed.\n" -msgid "SCF-8001-0Q.impact" -msgstr "The domain will receive an uncorrectable error trap which may cause the domain to panic. \n" -msgid "SCF-8001-0Q.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-1C -# keys: fault.chassis.SPARC-Enterprise.memory.block.mirror.ue -# -msgid "SCF-8001-1C.type" -msgstr "Fault" -msgid "SCF-8001-1C.severity" -msgstr "Major" -msgid "SCF-8001-1C.description" -msgstr "A data compare error has been detected within a MAC chip when memory is in mirror mode.\n Refer to %s for more information." -msgid "SCF-8001-1C.response" -msgstr "The memory associated with the MAC chip will be deconfigured after the platform is power cycled \nor after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8001-1C.impact" -msgstr "The domain will receive an uncorrectable error trap which may cause the domain to panic. \n" -msgid "SCF-8001-1C.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-2R -# keys: fault.chassis.SPARC-Enterprise.memory.block.pce -# -msgid "SCF-8001-2R.type" -msgstr "Fault" -msgid "SCF-8001-2R.severity" -msgstr "Minor" -msgid "SCF-8001-2R.description" -msgstr "A permanent correctable memory error (PCE) has been detected.\n Refer to %s for more information." -msgid "SCF-8001-2R.response" -msgstr "The 64MB chunk of memory that contains the permanent correctable error will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8001-2R.impact" -msgstr "Minimal impact.\n" -msgid "SCF-8001-2R.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-34 -# keys: fault.chassis.SPARC-Enterprise.memory.dimm.pce -# -msgid "SCF-8001-34.type" -msgstr "Fault" -msgid "SCF-8001-34.severity" -msgstr "Minor" -msgid "SCF-8001-34.description" -msgstr "The number of permanent correctable errors (PCE's) on single DIMM exceeds an\nacceptable threshold.\n Refer to %s for more information." -msgid "SCF-8001-34.response" -msgstr "No immediate action is taken and nothing is deconfigured.\n" -msgid "SCF-8001-34.impact" -msgstr "Minimal impact to system.\n" -msgid "SCF-8001-34.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-4X -# keys: fault.chassis.SPARC-Enterprise.memory.bank.err -# -msgid "SCF-8001-4X.type" -msgstr "Fault" -msgid "SCF-8001-4X.severity" -msgstr "Major" -msgid "SCF-8001-4X.description" -msgstr "The number of uncorrectable and correctable errors on single DIMM exceeds an\nacceptable threshold. This fault is detected while running POST.\n Refer to %s for more information." -msgid "SCF-8001-4X.response" -msgstr "The memory associated with the memory bank containing the errors is deconfigured.\n" -msgid "SCF-8001-4X.impact" -msgstr "POST is restarted after the memory associated with the memory bank has been deconfigured.\n" -msgid "SCF-8001-4X.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-9S -# keys: fault.chassis.SPARC-Enterprise.asic.flp.fe -# -msgid "SCF-8001-9S.type" -msgstr "Fault" -msgid "SCF-8001-9S.severity" -msgstr "Critical" -msgid "SCF-8001-9S.description" -msgstr "A fatal error has occurred within a FLP chip.\n Refer to %s for more information." -msgid "SCF-8001-9S.response" -msgstr "A single domain will be reset and the IO Channel associated with the\nFLP chip will be deconfigured during recovery.\n" -msgid "SCF-8001-9S.impact" -msgstr "Domain will be reset.\n" -msgid "SCF-8001-9S.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-AA -# keys: fault.chassis.SPARC-Enterprise.asic.flp.ce -# -msgid "SCF-8001-AA.type" -msgstr "Fault" -msgid "SCF-8001-AA.severity" -msgstr "Major" -msgid "SCF-8001-AA.description" -msgstr "The number of correctable errors associated with a FLP chip has exceeded an\nacceptable threshold.\n Refer to %s for more information." -msgid "SCF-8001-AA.response" -msgstr "The IO Channel associated with the FLP chip will be deconfigured after the platform is power \ncycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8001-AA.impact" -msgstr "No immediate impact. The IO Channel associated with the FLP chip will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is \nperformed.\n" -msgid "SCF-8001-AA.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-KC -# keys: upset.chassis.SPARC-Enterprise.io.disk.boot -# -msgid "SCF-8001-KC.type" -msgstr "upset" -msgid "SCF-8001-KC.severity" -msgstr "Critical" -msgid "SCF-8001-KC.description" -msgstr "Failure to boot illumos on a domain via an internal disk drive on the SAS controller.\n Refer to %s for more information." -msgid "SCF-8001-KC.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8001-KC.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n" -msgid "SCF-8001-KC.action" -msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-LQ -# keys: fault.chassis.SPARC-Enterprise.if.fe-ioc-flp -# -msgid "SCF-8001-LQ.type" -msgstr "Fault" -msgid "SCF-8001-LQ.severity" -msgstr "Critical" -msgid "SCF-8001-LQ.description" -msgstr "A fatal error occurred on the interface between an IOC chip and a FLP chip.\n Refer to %s for more information." -msgid "SCF-8001-LQ.response" -msgstr "The IO Channel associated with the FLP chip will be deconfigured after the domain\nusing the IO Channel is reset.\n" -msgid "SCF-8001-LQ.impact" -msgstr "The domain using the IO Channel associated with the FLP chip is reset. The IO Channel will\ndeconfigured after the domain is reset.\n" -msgid "SCF-8001-LQ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-ME -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.fe -# -msgid "SCF-8001-ME.type" -msgstr "Fault" -msgid "SCF-8001-ME.severity" -msgstr "Critical" -msgid "SCF-8001-ME.description" -msgstr "A fatal error was detected within an IOC chip.\n Refer to %s for more information." -msgid "SCF-8001-ME.response" -msgstr "The IOC chip (two IO Channels) will be deconfigured after the domains (one or two domains) using\nthe IOC chip are reset.\n" -msgid "SCF-8001-ME.impact" -msgstr "The domains (one or two domains) using the IOC chip are reset. The IOC chip (two IO Channels) will be \ndeconfigured after the domains are reset.\n" -msgid "SCF-8001-ME.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-NJ -# keys: upset.chassis.SPARC-Enterprise.asic.ioc.fe-tmo-dma -# -msgid "SCF-8001-NJ.type" -msgstr "Upset" -msgid "SCF-8001-NJ.severity" -msgstr "Critical" -msgid "SCF-8001-NJ.description" -msgstr "A fatal DMA master timeout detected by an IOC chip.\n Refer to %s for more information." -msgid "SCF-8001-NJ.response" -msgstr "The domains (one or two domains) using the IOC chip are reset. No components are deconfigured.\n" -msgid "SCF-8001-NJ.impact" -msgstr "The domains (one or two domains) using the IOC chip are reset.\n" -msgid "SCF-8001-NJ.action" -msgstr "The precise cause of the fault cannot be isolated. Please schedule a repair action.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-P2 -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.ch.fe -# -msgid "SCF-8001-P2.type" -msgstr "Fault" -msgid "SCF-8001-P2.severity" -msgstr "Critical" -msgid "SCF-8001-P2.description" -msgstr "A fatal error was detected within an IOC chip. This fatal error affects only a single\nIO Channel.\n Refer to %s for more information." -msgid "SCF-8001-P2.response" -msgstr "The IO Channel will be deconfigured after the domain is reset.\n" -msgid "SCF-8001-P2.impact" -msgstr "The domain using the IO Channel is reset. The IO Channel will be deconfigured after\nthe domain is reset.\n" -msgid "SCF-8001-P2.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information\n" -# -# code: SCF-8001-QX -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.fe -# -msgid "SCF-8001-QX.type" -msgstr "Fault" -msgid "SCF-8001-QX.severity" -msgstr "Critical" -msgid "SCF-8001-QX.description" -msgstr "A fatal error was detected within an IOC chip. The fatal error affects only one leaf within\nan IO Channel (1/2 an IO Channel).\n Refer to %s for more information." -msgid "SCF-8001-QX.response" -msgstr "The IO Channel leaf (1/2 an IO Channel) will be deconfigured after the domain using the IO\nChannel is reset.\n" -msgid "SCF-8001-QX.impact" -msgstr "The domain using the IO Channel leaf is reset. The IO Channel leaf (1/2 an IO Channel) will be\ndeconfigured after the domain is reset.\n" -msgid "SCF-8001-QX.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-RP -# keys: fault.chassis.SPARC-Enterprise.io.pciex.card.fe -# -msgid "SCF-8001-RP.type" -msgstr "Fault" -msgid "SCF-8001-RP.severity" -msgstr "Critical" -msgid "SCF-8001-RP.description" -msgstr "A fatal error was detected on a PCI-Express card in a PCI slot.\n Refer to %s for more information." -msgid "SCF-8001-RP.response" -msgstr "The PCI-Express card is deconfigured.\n" -msgid "SCF-8001-RP.impact" -msgstr "The domain using the PCI slot is reset.\n" -msgid "SCF-8001-RP.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-SA -# keys: fault.chassis.SPARC-Enterprise.io.pci.card.fe -# -msgid "SCF-8001-SA.type" -msgstr "Fault" -msgid "SCF-8001-SA.severity" -msgstr "Critical" -msgid "SCF-8001-SA.description" -msgstr "A fatal error was detected on a PCI-X card in a PCI slot.\n Refer to %s for more information." -msgid "SCF-8001-SA.response" -msgstr "The PCI-X card is deconfigured.\n" -msgid "SCF-8001-SA.impact" -msgstr "The domain using the PCI slot is reset.\n" -msgid "SCF-8001-SA.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-TS -# keys: fault.chassis.SPARC-Enterprise.io.pciex.bridge.fe -# -msgid "SCF-8001-TS.type" -msgstr "Fault" -msgid "SCF-8001-TS.severity" -msgstr "Critical" -msgid "SCF-8001-TS.description" -msgstr "A fatal error was detected within a PCIe/PCI-X bridge chip.\n Refer to %s for more information." -msgid "SCF-8001-TS.response" -msgstr "All internal I/O behind the PCIe/PCI-X bridge chip is deconfigured (if the\nPCIe/PCI-X bridge chip is located on an IOU or IOUA) or all the PCI-X slots \nin an I/O Boat are deconfigured (if the PCIe/PCI-X bridge chip is located on\nan I/O Boat).\n" -msgid "SCF-8001-TS.impact" -msgstr "The domain using the PCIe/PCI-X bridge chip is reset.\n" -msgid "SCF-8001-TS.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-U5 -# keys: fault.chassis.SPARC-Enterprise.io.pciex.switch.fe -# -msgid "SCF-8001-U5.type" -msgstr "Fault" -msgid "SCF-8001-U5.severity" -msgstr "Critical" -msgid "SCF-8001-U5.description" -msgstr "A fatal error was detected within a PCIe switch chip.\n Refer to %s for more information." -msgid "SCF-8001-U5.response" -msgstr "All internal I/O behind the PCIe switch chip is deconfigured (if the PCIe switch chip\nis located on an IOU) or all the PCI-Express slots or PCI-X slots in an I/O Boat are \ndeconfigured (if the PCIe switch chip is located on an I/O Boat).\n" -msgid "SCF-8001-U5.impact" -msgstr "The domain using the PCIe switch chip is reset.\n" -msgid "SCF-8001-U5.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-VY -# keys: fault.chassis.SPARC-Enterprise.io.pci.gbe.fe -# -msgid "SCF-8001-VY.type" -msgstr "Fault" -msgid "SCF-8001-VY.severity" -msgstr "Critical" -msgid "SCF-8001-VY.description" -msgstr "A fatal error was detected within a Gigabit Ethernet (GbE) controller.\n Refer to %s for more information." -msgid "SCF-8001-VY.response" -msgstr "The Gigabit Ethernet (GbE) controller is deconfigured.\n" -msgid "SCF-8001-VY.impact" -msgstr "The domain using the Gigabit Ethernet (GbE) controller is reset.\n" -msgid "SCF-8001-VY.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-W3 -# keys: fault.chassis.SPARC-Enterprise.io.pci.sas.fe -# -msgid "SCF-8001-W3.type" -msgstr "Fault" -msgid "SCF-8001-W3.severity" -msgstr "Critical" -msgid "SCF-8001-W3.description" -msgstr "A fatal error was detected within a SAS (Serial Attached SCSI) controller.\n Refer to %s for more information." -msgid "SCF-8001-W3.response" -msgstr "The internal SAS devices behind the SAS controller (internal HDDs, internal DVD drives, internal\ntape drives) are deconfigured.\n" -msgid "SCF-8001-W3.impact" -msgstr "The domain using the SAS controller is reset.\n" -msgid "SCF-8001-W3.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-XH -# keys: fault.chassis.SPARC-Enterprise.if.se-ioc-flp -# -msgid "SCF-8001-XH.type" -msgstr "Fault" -msgid "SCF-8001-XH.severity" -msgstr "Major" -msgid "SCF-8001-XH.description" -msgstr "A non-fatal uncorrectable error occurred on the interface between an IOC chip and a FLP chip.\n Refer to %s for more information." -msgid "SCF-8001-XH.response" -msgstr "The IO Channel corresponding to the FLP chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8001-XH.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe IO Channel corresponding to the FLP chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8001-XH.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8001-YD -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.ch.se -# -msgid "SCF-8001-YD.type" -msgstr "Fault" -msgid "SCF-8001-YD.severity" -msgstr "Major" -msgid "SCF-8001-YD.description" -msgstr "A non-fatal uncorrectable error was detected within an IOC chip. This error affects\na single IO Channel.\n Refer to %s for more information." -msgid "SCF-8001-YD.response" -msgstr "The IO Channel will be deconfigured after the platform is power cycled or after the domain reboots or \nafter a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8001-YD.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. The IO Channel will be deconfigured \nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed.\n" -msgid "SCF-8001-YD.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-0X -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.se -# -msgid "SCF-8002-0X.type" -msgstr "Fault" -msgid "SCF-8002-0X.severity" -msgstr "Major" -msgid "SCF-8002-0X.description" -msgstr "Non-fatal uncorrectable error was detected within an IOC chip. This error affects\na single IO Channel leaf (1/2 an IO Channel).\n Refer to %s for more information." -msgid "SCF-8002-0X.response" -msgstr "The IO Channel leaf (1/2 an IO Channel) will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-0X.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe IO Channel leaf (1/2 an IO Channel) will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-0X.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-12 -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.se-no-credit-pci -# -msgid "SCF-8002-12.type" -msgstr "Fault" -msgid "SCF-8002-12.severity" -msgstr "Major" -msgid "SCF-8002-12.description" -msgstr "A non-fatal uncorrectable \"PCI-E card no-credit update\" error has been detected by an IOC chip.\n Refer to %s for more information." -msgid "SCF-8002-12.response" -msgstr "The IO Channel leaf (1/2 an IO Channel) will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-12.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe IO Channel leaf (1/2 an IO Channel) will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-12.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-2J -# keys: fault.chassis.SPARC-Enterprise.io.pciex.card.se -# -msgid "SCF-8002-2J.type" -msgstr "Fault" -msgid "SCF-8002-2J.severity" -msgstr "Major" -msgid "SCF-8002-2J.description" -msgstr "A non-fatal uncorrectable error occurred due to a PCI-Express card in a PCI-Express slot.\n Refer to %s for more information." -msgid "SCF-8002-2J.response" -msgstr "The PCI-Express slot will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-2J.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe PCI-Express slot will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-2J.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-3E -# keys: fault.chassis.SPARC-Enterprise.io.pci.card.se -# -msgid "SCF-8002-3E.type" -msgstr "Fault" -msgid "SCF-8002-3E.severity" -msgstr "Major" -msgid "SCF-8002-3E.description" -msgstr "A non-fatal uncorrectable error occcurred due to a PCI-X card in a PCI slot.\n Refer to %s for more information." -msgid "SCF-8002-3E.response" -msgstr "The PCI-X slot will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-3E.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe PCI-X slot will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-3E.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-4Q -# keys: fault.chassis.SPARC-Enterprise.io.pciex.bridge.se -# -msgid "SCF-8002-4Q.type" -msgstr "Fault" -msgid "SCF-8002-4Q.severity" -msgstr "Major" -msgid "SCF-8002-4Q.description" -msgstr "A non-fatal uncorrectable error was detected within a PCIe/PCI-X bridge chip.\n Refer to %s for more information." -msgid "SCF-8002-4Q.response" -msgstr "All internal I/O behind the PCIe/PCI-X bridge chip is deconfigured (if the\nPCIe/PCI-X bridge chip is located on an IOU or IOUA) or all the PCI-X slots \nin an I/O Boat are deconfigured (if the PCIe/PCI-X bridge chip is located on\nan I/O Boat). The deconfiguration will take place after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-4Q.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nAll internal I/O behind the PCIe/PCI-X bridge chip is deconfigured (if the\nPCIe/PCI-X bridge chip is located on an IOU or IOUA) or all the PCI-X slots \nin an I/O Boat are deconfigured (if the PCIe/PCI-X bridge chip is located on\nan I/O Boat). The deconfiguration will take place after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-4Q.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-5C -# keys: fault.chassis.SPARC-Enterprise.io.pciex.switch.se -# -msgid "SCF-8002-5C.type" -msgstr "Fault" -msgid "SCF-8002-5C.severity" -msgstr "Major" -msgid "SCF-8002-5C.description" -msgstr "A non-fatal uncorrectable error was detected within a PCIe switch chip.\n Refer to %s for more information." -msgid "SCF-8002-5C.response" -msgstr "All internal I/O behind the PCIe switch chip is deconfigured (if the PCIe switch chip\nis located on an IOU) or all the PCI-Express slots or PCI-X slots in an I/O Boat are \ndeconfigured (if the PCIe switch chip is located on an I/O Boat). The deconfiguration\nwill take place after the platform is power cycled or after the domain reboots or after a \nDynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-5C.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nAll internal I/O behind the PCIe switch chip is deconfigured (if the PCIe switch chip\nis located on an IOU) or all the PCI-Express slots or PCI-X slots in an I/O Boat are \ndeconfigured (if the PCIe switch chip is located on an I/O Boat). The deconfiguration\nwill take place after the platform is power cycled or after the domain reboots or after a \nDynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-5C.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-6R -# keys: fault.chassis.SPARC-Enterprise.if.ce-ioc-flp -# -msgid "SCF-8002-6R.type" -msgstr "Fault" -msgid "SCF-8002-6R.severity" -msgstr "Major" -msgid "SCF-8002-6R.description" -msgstr "The number of correctable errors on the interface between an IOC chip and a FLP chip has exceeded \nan acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8002-6R.response" -msgstr "The IO Channel that is associated with the FLP chip will be deconfigured after the platform is power \ncycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-6R.impact" -msgstr "No immediate impact. The IO Channel that is associated with the FLP chip will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is \nperformed.\n" -msgid "SCF-8002-6R.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-74 -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.ch.ce -# -msgid "SCF-8002-74.type" -msgstr "Fault" -msgid "SCF-8002-74.severity" -msgstr "Major" -msgid "SCF-8002-74.description" -msgstr "The number of correctable errors within a IOC Chip has exceeded an acceptable threshold. This fault\naffects a single IO Channel.\n Refer to %s for more information." -msgid "SCF-8002-74.response" -msgstr "The IO Channel is deconfigured after the platform is power cycled or after the domain reboots or after a \nDynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-74.impact" -msgstr "No immediate impact. The IO Channel is deconfigured after the platform is power cycled or after the \ndomain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-74.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-8D -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.ce -# -msgid "SCF-8002-8D.type" -msgstr "Fault" -msgid "SCF-8002-8D.severity" -msgstr "Major" -msgid "SCF-8002-8D.description" -msgstr "The number of correctable errors within a IOC Chip has exceeded an acceptable threshold. This fault\naffects a single IO Channel leaf (1/2 an IO Channel).\n Refer to %s for more information." -msgid "SCF-8002-8D.response" -msgstr "The IO Channel leaf (1/2 an IO Channel) is deconfigured after the platform is power cycled or after \nthe domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-8D.impact" -msgstr "No immediate impact. The IO Channel leaf (1/2 an IO Channel) is deconfigured after the platform is \npower cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-8D.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-9H -# keys: upset.chassis.SPARC-Enterprise.asic.ioc.ch.boot -# -msgid "SCF-8002-9H.type" -msgstr "Upset" -msgid "SCF-8002-9H.severity" -msgstr "Critical" -msgid "SCF-8002-9H.description" -msgstr "Failure to boot illumos on a domain using a device on an IO Channel.\n Refer to %s for more information." -msgid "SCF-8002-9H.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8002-9H.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n" -msgid "SCF-8002-9H.action" -msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary. Please consult the detail section of the \nknowledge article for additional information.\n" -# -# code: SCF-8002-A3 -# keys: upset.chassis.SPARC-Enterprise.asic.ioc.ch.leaf.boot -# -msgid "SCF-8002-A3.type" -msgstr "Upset" -msgid "SCF-8002-A3.severity" -msgstr "Critical" -msgid "SCF-8002-A3.description" -msgstr "Failure to boot illumos on a domain using a device on IO Channel leaf (1/2 an IO Channel).\n Refer to %s for more information." -msgid "SCF-8002-A3.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8002-A3.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n" -msgid "SCF-8002-A3.action" -msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary. Please consult the detail section of the \nknowledge article for additional information.\n" -# -# code: SCF-8002-CY -# keys: upset.chassis.SPARC-Enterprise.io.pci.gbe.boot -# -msgid "SCF-8002-CY.type" -msgstr "Upset" -msgid "SCF-8002-CY.severity" -msgstr "Critical" -msgid "SCF-8002-CY.description" -msgstr "Failure to boot illumos on a domain via GbE.\n Refer to %s for more information." -msgid "SCF-8002-CY.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8002-CY.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n" -msgid "SCF-8002-CY.action" -msgstr "The platform administrator should investigate the cause of the boot\nproblem and schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-D5 -# keys: upset.chassis.SPARC-Enterprise.io.pci.card.boot -# -msgid "SCF-8002-D5.type" -msgstr "Upset" -msgid "SCF-8002-D5.severity" -msgstr "Critical" -msgid "SCF-8002-D5.description" -msgstr "Failure to boot illumos on a domain using a device in a PCI-X slot.\n Refer to %s for more information." -msgid "SCF-8002-D5.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8002-D5.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt\n" -msgid "SCF-8002-D5.action" -msgstr "The platform administrator should investigate the cause of the boot\nproblem and schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-ES -# keys: upset.chassis.SPARC-Enterprise.io.pciex.card.boot -# -msgid "SCF-8002-ES.type" -msgstr "Upset" -msgid "SCF-8002-ES.severity" -msgstr "Critical" -msgid "SCF-8002-ES.description" -msgstr "Failure to boot illumos on a domain using a device in a PCI-Express slot.\n Refer to %s for more information." -msgid "SCF-8002-ES.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8002-ES.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n" -msgid "SCF-8002-ES.action" -msgstr "The platform administrator should investigate the cause of the boot\nproblem and schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-FA -# keys: upset.chassis.SPARC-Enterprise.io.pciex.bridge.boot -# -msgid "SCF-8002-FA.type" -msgstr "Upset" -msgid "SCF-8002-FA.severity" -msgstr "Critical" -msgid "SCF-8002-FA.description" -msgstr "Failure to boot illumos on a domain using a device behind a PCI-Express/PCI-X \nbridge chip. This includes the PCI-X slot and internal I/O on an IOU (if the\nPCI-Express/PCI-X bridge is located on an IOU or IOUA) and the PCI-X slots of\nan I/O Boat (if the PCI-Express/PCI-X bridge is located on an I/O Boat).\n Refer to %s for more information." -msgid "SCF-8002-FA.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8002-FA.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n" -msgid "SCF-8002-FA.action" -msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-GP -# keys: upset.chassis.SPARC-Enterprise.io.pciex.switch.boot -# -msgid "SCF-8002-GP.type" -msgstr "upset" -msgid "SCF-8002-GP.severity" -msgstr "Critical" -msgid "SCF-8002-GP.description" -msgstr "Failure to boot illumos on a domain using a device behind a PCI-Express switch chip.\nThis includes PCI-X slot and internal I/O devices (if the PCI-Express switch chip \nis located on an IOU), and the PCI-Express slots and PCI-X slots on an I/O Boat\n(if the PCI-Express switch chip is located on an I/O Boat).\n Refer to %s for more information." -msgid "SCF-8002-GP.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8002-GP.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n" -msgid "SCF-8002-GP.action" -msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-HE -# keys: upset.chassis.SPARC-Enterprise.io.pci.sas.boot -# -msgid "SCF-8002-HE.type" -msgstr "Upset" -msgid "SCF-8002-HE.severity" -msgstr "Critical" -msgid "SCF-8002-HE.description" -msgstr "Failure to boot illumos on a domain using an internal SAS (Serial Attached\nSCSI) device. This includes the internal hard drives and the internal DVD drives\nand the internal tape drives.\n Refer to %s for more information." -msgid "SCF-8002-HE.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8002-HE.impact" -msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n" -msgid "SCF-8002-HE.action" -msgstr "The platform administrator should investigate the cause of the boot\nproblem and schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-JJ -# keys: fault.chassis.jtag.device -# -msgid "SCF-8002-JJ.type" -msgstr "Fault" -msgid "SCF-8002-JJ.severity" -msgstr "Critical" -msgid "SCF-8002-JJ.description" -msgstr "JTAG read or write failure to a specific chip.\n Refer to %s for more information." -msgid "SCF-8002-JJ.response" -msgstr "The resources associated with the chip will be deconfigured. Please consult the detail section \nof the knowledge article for additional information.\n" -msgid "SCF-8002-JJ.impact" -msgstr "The platform may be reset or a domain may be reset. The platform may be unable to restart.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8002-JJ.action" -msgstr "The platform administrator should schedule a service action to replace\nthe affected Field Replaceable Unit (FRU), the identity of which can be\ndetermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-K2 -# keys: fault.chassis.jtag.device-internal -# -msgid "SCF-8002-K2.type" -msgstr "Fault" -msgid "SCF-8002-K2.severity" -msgstr "Critical" -msgid "SCF-8002-K2.description" -msgstr "JTAG access failure to a specific chip when attempting a reconfiguration operation.\nPlease consult the detail section of the knowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8002-K2.response" -msgstr "The resources associated with the chip will be deconfigured. Please consult the detail section of \nthe knowledge article for additional information.\n" -msgid "SCF-8002-K2.impact" -msgstr "The platform may be reset or a domain may be reset. The platform may become unbootable.\nIt is also possible that some other problem may occur. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8002-K2.action" -msgstr "The platform administrator should schedule a service action to replace\nthe affected Field Replaceable Unit (FRU), the identity of which can be\ndetermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-LX -# keys: fault.chassis.i2c.device -# -msgid "SCF-8002-LX.type" -msgstr "Fault" -msgid "SCF-8002-LX.severity" -msgstr "Critical" -msgid "SCF-8002-LX.description" -msgstr "I2C access failure to an I2C device.\n Refer to %s for more information." -msgid "SCF-8002-LX.response" -msgstr "The resources associated with the I2C device may deconfigured. The speed of all fans on the platform\nmay be raised. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8002-LX.impact" -msgstr "It is possible that the platform will not be able to be be restarted. Please consult the detail section \nof the knowledge article for additional information.\n" -msgid "SCF-8002-LX.action" -msgstr "The platform administrator should schedule a service action to replace\nthe affected Field Replaceable Unit (FRU), the identity of which can be\ndetermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-M4 -# keys: fault.chassis.i2c.device-internal -# -msgid "SCF-8002-M4.type" -msgstr "Fault" -msgid "SCF-8002-M4.severity" -msgstr "Critical" -msgid "SCF-8002-M4.description" -msgstr "I2C access failure to a specific chip when attempting a reconfiguration operation.\nPlease consult the detail section of the knowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8002-M4.response" -msgstr "The resources associated with the chip will be deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8002-M4.impact" -msgstr "One or more domains may be reset. It is also possible that some other problem may occur. \nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8002-M4.action" -msgstr "The platform administrator should schedule a service action to replace\nthe affected Field Replaceable Unit (FRU), the identity of which can be\ndetermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-UD -# keys: fault.chassis.SPARC-Enterprise.asic.mac.fe -# -msgid "SCF-8002-UD.type" -msgstr "Fault" -msgid "SCF-8002-UD.severity" -msgstr "Critical" -msgid "SCF-8002-UD.description" -msgstr "A fatal error was detected within a MAC chip.\n Refer to %s for more information." -msgid "SCF-8002-UD.response" -msgstr "Memory associated within the MAC chip will be deconfigured.\n" -msgid "SCF-8002-UD.impact" -msgstr "Platform may be reset or domains using the MAC chip will be reset.\n" -msgid "SCF-8002-UD.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-VP -# keys: fault.chassis.SPARC-Enterprise.asic.mac.bank.fe -# -msgid "SCF-8002-VP.type" -msgstr "Fault" -msgid "SCF-8002-VP.severity" -msgstr "Critical" -msgid "SCF-8002-VP.description" -msgstr "A fatal error was detected within the part of a MAC chip that controls a memory bank.\n Refer to %s for more information." -msgid "SCF-8002-VP.response" -msgstr "The bank of memory is deconfigured.\n" -msgid "SCF-8002-VP.impact" -msgstr "Domain using the memory bank will be reset.\n" -msgid "SCF-8002-VP.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-WA -# keys: fault.chassis.SPARC-Enterprise.asic.mac.se -# -msgid "SCF-8002-WA.type" -msgstr "Fault" -msgid "SCF-8002-WA.severity" -msgstr "Major" -msgid "SCF-8002-WA.description" -msgstr "A non-fatal uncorrectable error was detected within a MAC chip.\n Refer to %s for more information." -msgid "SCF-8002-WA.response" -msgstr "Memory associated with the MAC chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-WA.impact" -msgstr "The domain may panic, the MAC memory patrol feature may stop working, or access to MAC registers from the\ndomain may fail.\n" -msgid "SCF-8002-WA.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-XS -# keys: fault.chassis.SPARC-Enterprise.asic.mac.bank.se -# -msgid "SCF-8002-XS.type" -msgstr "Fault" -msgid "SCF-8002-XS.severity" -msgstr "Major" -msgid "SCF-8002-XS.description" -msgstr "A non-fatal uncorrectable error was detected within the part of a MAC chip that controls a memory bank.\n Refer to %s for more information." -msgid "SCF-8002-XS.response" -msgstr "Memory associated with this memory bank is deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-XS.impact" -msgstr "The domain will encounter an non-fatal uncorrectable error and the domain may panic.\n" -msgid "SCF-8002-XS.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8002-Y5 -# keys: fault.chassis.SPARC-Enterprise.asic.mac.ce -# -msgid "SCF-8002-Y5.type" -msgstr "Fault" -msgid "SCF-8002-Y5.severity" -msgstr "Major" -msgid "SCF-8002-Y5.description" -msgstr "The number of correctable errors detected within a MAC chip has exceeded an\nacceptable threshold.\n Refer to %s for more information." -msgid "SCF-8002-Y5.response" -msgstr "Memory associated to the MAC will be deconfigured after the platform is power cycled or after \nthe domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-Y5.impact" -msgstr "No immediate impact. Memory associated to the MAC will be deconfigured after the platform is power \ncycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8002-Y5.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-0S -# keys: fault.chassis.SPARC-Enterprise.asic.mac.bank.ce -# -msgid "SCF-8003-0S.type" -msgstr "Fault" -msgid "SCF-8003-0S.severity" -msgstr "Major" -msgid "SCF-8003-0S.description" -msgstr "The number of correctable errors detected within the part of a MAC chip that controls a memory\nbank has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8003-0S.response" -msgstr "Memory associated with the memory bank will be deconfigured after the platform is power cycled or after \nthe domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8003-0S.impact" -msgstr "No immediate impact. Memory associated with the memory bank will be deconfigured after the platform \nis power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8003-0S.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-5D -# keys: fault.chassis.SPARC-Enterprise.madm.io.se -# -msgid "SCF-8003-5D.type" -msgstr "Fault" -msgid "SCF-8003-5D.severity" -msgstr "Major" -msgid "SCF-8003-5D.description" -msgstr "Machine Administration Sofware (MADM) on the domain detected a serious I/O problem.\n Refer to %s for more information." -msgid "SCF-8003-5D.response" -msgstr "No immediate action is taken and nothing is deconfigured.\n" -msgid "SCF-8003-5D.impact" -msgstr "Problem with an I/O device.\n" -msgid "SCF-8003-5D.action" -msgstr "The platform administrator should use the output of the showlogs command to determine\nif a service action is necessary. Please consult the detail section of the knowledge\narticle for additional information.\n" -# -# code: SCF-8003-6Y -# keys: fault.chassis.SPARC-Enterprise.madm.io.fe -# -msgid "SCF-8003-6Y.type" -msgstr "Fault" -msgid "SCF-8003-6Y.severity" -msgstr "Critical" -msgid "SCF-8003-6Y.description" -msgstr "Machine Administration Sofware (MADM) on the domain detected a fatal I/O problem.\n Refer to %s for more information." -msgid "SCF-8003-6Y.response" -msgstr "Nothing is deconfigured on the XSCF, but the domain will deconfigure the I/O device.\n" -msgid "SCF-8003-6Y.impact" -msgstr "Problem with an I/O device.\n" -msgid "SCF-8003-6Y.action" -msgstr "The platform administrator should use the output of the showlogs command to determine\nif a service action is necessary. Please consult the detail section of the knowledge\narticle for additional information.\n" -# -# code: SCF-8003-GJ -# keys: fault.chassis.SPARC-Enterprise.if.fe-mbc-sc -# -msgid "SCF-8003-GJ.type" -msgstr "Fault" -msgid "SCF-8003-GJ.severity" -msgstr "Critical" -msgid "SCF-8003-GJ.description" -msgstr "A fatal error occurred on the interface between a MBC chip and a SC chip.\n Refer to %s for more information." -msgid "SCF-8003-GJ.response" -msgstr "Resources associated with the faulty FRU will be deconfigured. Please consult the \ndetail section of the knowledge article for additional information.\n" -msgid "SCF-8003-GJ.impact" -msgstr "Either the platform or a domain is reset. The platform may become unbootable.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8003-GJ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-HA -# keys: fault.chassis.SPARC-Enterprise.asic.mbc.fe -# -msgid "SCF-8003-HA.type" -msgstr "Fault" -msgid "SCF-8003-HA.severity" -msgstr "Critical" -msgid "SCF-8003-HA.description" -msgstr "A fatal error was detected within a MBC chip.\n Refer to %s for more information." -msgid "SCF-8003-HA.response" -msgstr "Resources associated with the faulty FRU will be deconfigured. Please consult the \ndetail section of the knowledge article for additional information.\n" -msgid "SCF-8003-HA.impact" -msgstr "Either the platform will be reset or a domain may be reset. The platform may become unbootable.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8003-HA.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-JP -# keys: fault.chassis.SPARC-Enterprise.if.se-mbc-sc -# -msgid "SCF-8003-JP.type" -msgstr "Fault" -msgid "SCF-8003-JP.severity" -msgstr "Critical" -msgid "SCF-8003-JP.description" -msgstr "A non-fatal uncorrectable error occurred on the interface between a MBC chip and a SC chip.\n Refer to %s for more information." -msgid "SCF-8003-JP.response" -msgstr "No immediate action is taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconfigured after the platform is\npower cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed. This resource deconfiguration may cause the platform to become\nunbootable. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8003-JP.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \n" -msgid "SCF-8003-JP.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-K5 -# keys: fault.chassis.SPARC-Enterprise.if.se-mbc-xscf -# -msgid "SCF-8003-K5.type" -msgstr "Fault" -msgid "SCF-8003-K5.severity" -msgstr "Critical" -msgid "SCF-8003-K5.description" -msgstr "A non-fatal uncorrectable error occurred on the interface between a MBC chip and the XSCF.\n Refer to %s for more information." -msgid "SCF-8003-K5.response" -msgstr "No immediate action is taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconfigured after the platform is\npower cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed. This resource deconfiguration may cause the platform to become\nunbootable. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8003-K5.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \n" -msgid "SCF-8003-K5.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-LS -# keys: fault.chassis.SPARC-Enterprise.asic.mbc.se -# -msgid "SCF-8003-LS.type" -msgstr "Fault" -msgid "SCF-8003-LS.severity" -msgstr "Critical" -msgid "SCF-8003-LS.description" -msgstr "A non-fatal uncorrectable error was detected within a MBC chip.\n Refer to %s for more information." -msgid "SCF-8003-LS.response" -msgstr "No immediate action is taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconfigured after the platform is\npower cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed. This resource deconfiguration may cause the platform to become\nunbootable. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8003-LS.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \n" -msgid "SCF-8003-LS.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-M3 -# keys: fault.chassis.SPARC-Enterprise.asic.mbc.se-dma -# -msgid "SCF-8003-M3.type" -msgstr "Fault" -msgid "SCF-8003-M3.severity" -msgstr "Major" -msgid "SCF-8003-M3.description" -msgstr "An uncorrectable error was detected on a DMA channel between two MBC chips on two\ndifferent FRUs. Please consult the detail section of the knowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8003-M3.response" -msgstr "There are two DMA channels between MBC chips. If the first DMA channel fails, the system\nwill switch to using the second DMA channel. If the second DMA channel fails, then the\nFRU with the MBC chip becomes unmanageable. If the second DMA channel fails, then resources\nassociated with the FRU with the MBC chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nDeconfiguration of these resources may reduce system performance or may cause the\nplatform to become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8003-M3.impact" -msgstr "If it is the second DMA channel for the MBC chip that has failed, the XSCF will no longer be able \nto contact the chips and devices that are connected to the faulty MBC chip.\n" -msgid "SCF-8003-M3.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-NY -# keys: fault.chassis.SPARC-Enterprise.asic.mbc.se-dma-dscp -# -msgid "SCF-8003-NY.type" -msgstr "Fault" -msgid "SCF-8003-NY.severity" -msgstr "Major" -msgid "SCF-8003-NY.description" -msgstr "A non-fatal uncorrectable internal error was detected on the DMA interface used by DSCP \non a MBC chip.\n Refer to %s for more information." -msgid "SCF-8003-NY.response" -msgstr "DSCP will switch to use some other XSB's DMA interface, if there is an operational DMA interface\non another XSB in this domain. Otherwise, the system will continue to use the existing DMA interface.\nThe XSB with this DMA interface will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8003-NY.impact" -msgstr "The domain may encounter an uncorrectable error, but the domain will not panic.\n" -msgid "SCF-8003-NY.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-PD -# keys: fault.chassis.SPARC-Enterprise.asic.mbc.se-cmd -# -msgid "SCF-8003-PD.type" -msgstr "Fault" -msgid "SCF-8003-PD.severity" -msgstr "Major" -msgid "SCF-8003-PD.description" -msgstr "XSCF software detected a problem on the command interface between the XSCF and an XSB.\n Refer to %s for more information." -msgid "SCF-8003-PD.response" -msgstr "If the problem can be isolated to a specific XSB, the system will switch to use some other XSB's \ncommand interface, if there is an operational command interface on another XSB in this domain. Otherwise, \nthe system will continue to use the existing command interface. The XSB with this command interface will \nbe deconfigured after the platform is power cycled or after the domain reboots or after a Dynamic \nReconfiguration operation is performed. If the problem cannot be isolated to a specific XSB, no\ndeconfiguration is performed. Please consult the detail section of the knowledge article for additional \ninformation.\n" -msgid "SCF-8003-PD.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8003-PD.action" -msgstr "If the problem can be isolated to a specific XSB, schedule a repair action to replace the affected \nField Replaceable Unit (FRU), the identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-QH -# keys: fault.chassis.SPARC-Enterprise.if.ce-mbc-sc -# -msgid "SCF-8003-QH.type" -msgstr "Fault" -msgid "SCF-8003-QH.severity" -msgstr "Major" -msgid "SCF-8003-QH.description" -msgstr "The number of correctable errors on the interface between a MBC chip and a SC chip has exceeded \nan acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8003-QH.response" -msgstr "Resources associated with this SC chip (this includes CPU chips, memory, and I/O) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration \noperation is performed. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8003-QH.impact" -msgstr "No immediate action. Resources associated with this SC chip (this includes CPU chips, memory, and I/O) \nwill be deconfigured after the platform is power cycled or after the domain reboots or after a Dynamic \nReconfiguration operation is performed. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8003-QH.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-RR -# keys: fault.chassis.SPARC-Enterprise.asic.mbc.ce -# -msgid "SCF-8003-RR.type" -msgstr "Fault" -msgid "SCF-8003-RR.severity" -msgstr "Major" -msgid "SCF-8003-RR.description" -msgstr "The number of correctable errors within the SRAM of a MBC chip has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8003-RR.response" -msgstr "The resources associated with this MBC chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8003-RR.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8003-RR.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8003-S4 -# keys: fault.chassis.SPARC-Enterprise.asic.mbc.test -# -msgid "SCF-8003-S4.type" -msgstr "Fault" -msgid "SCF-8003-S4.severity" -msgstr "Major" -msgid "SCF-8003-S4.description" -msgstr "An error was detected within the section of a MBC chip dealing with a specific\nXSB. This error is detected during self-test.\n Refer to %s for more information." -msgid "SCF-8003-S4.response" -msgstr "The XSB is deconfigured.\n" -msgid "SCF-8003-S4.impact" -msgstr "No immediate impact. The XSB is deconfigured.\n" -msgid "SCF-8003-S4.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-3Y -# keys: fault.chassis.SPARC-Enterprise.asic.mac.power.fail -# -msgid "SCF-8004-3Y.type" -msgstr "Fault" -msgid "SCF-8004-3Y.severity" -msgstr "Critical" -msgid "SCF-8004-3Y.description" -msgstr "The MAC chip has detected it does not have sufficient power to continue operating.\n Refer to %s for more information." -msgid "SCF-8004-3Y.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8004-3Y.impact" -msgstr "The domain using the MAC chip will be reset.\n" -msgid "SCF-8004-3Y.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-45 -# keys: fault.chassis.SPARC-Enterprise.asic.sc.power.fail -# -msgid "SCF-8004-45.type" -msgstr "Fault" -msgid "SCF-8004-45.severity" -msgstr "Critical" -msgid "SCF-8004-45.description" -msgstr "The SC chip has detected it does not have sufficient power to continue operating.\n Refer to %s for more information." -msgid "SCF-8004-45.response" -msgstr "Resources may be deconfigured after a platform reset.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-45.impact" -msgstr "Either the platform or a domain will be reset. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8004-45.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-5S -# keys: fault.chassis.SPARC-Enterprise.asic.xb.power.fail -# -msgid "SCF-8004-5S.type" -msgstr "Fault" -msgid "SCF-8004-5S.severity" -msgstr "Critical" -msgid "SCF-8004-5S.description" -msgstr "The XB chip has detected it does not have sufficient power to continue operating.\n Refer to %s for more information." -msgid "SCF-8004-5S.response" -msgstr "Resources may be deconfigured after a platform reset.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-5S.impact" -msgstr "The platform will be reset.\n" -msgid "SCF-8004-5S.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-6A -# keys: fault.chassis.SPARC-Enterprise.asic.ioc.power.fail -# -msgid "SCF-8004-6A.type" -msgstr "Fault" -msgid "SCF-8004-6A.severity" -msgstr "Critical" -msgid "SCF-8004-6A.description" -msgstr "The IOC chip has detected it does not have sufficient power to continue operating.\n Refer to %s for more information." -msgid "SCF-8004-6A.response" -msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-6A.impact" -msgstr "The domains using the IOC chip will be reset.\n" -msgid "SCF-8004-6A.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-7P -# keys: fault.chassis.SPARC-Enterprise.asic.clk.power.fail -# -msgid "SCF-8004-7P.type" -msgstr "Fault" -msgid "SCF-8004-7P.severity" -msgstr "Critical" -msgid "SCF-8004-7P.description" -msgstr "The Clock chip has detected it does not have sufficient power to continue operating.\n Refer to %s for more information." -msgid "SCF-8004-7P.response" -msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-7P.impact" -msgstr "The platform will be reset.\n" -msgid "SCF-8004-7P.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-8X -# keys: fault.chassis.SPARC-Enterprise.asic.cpu.power.fail -# -msgid "SCF-8004-8X.type" -msgstr "Fault" -msgid "SCF-8004-8X.severity" -msgstr "Critical" -msgid "SCF-8004-8X.description" -msgstr "A CPU chip has detected it does not have sufficient power to continue operating.\n Refer to %s for more information." -msgid "SCF-8004-8X.response" -msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-8X.impact" -msgstr "The domain using the CPU chip will reset.\n" -msgid "SCF-8004-8X.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-92 -# keys: fault.chassis.SPARC-Enterprise.asic.flp.power.fail -# -msgid "SCF-8004-92.type" -msgstr "Fault" -msgid "SCF-8004-92.severity" -msgstr "Critical" -msgid "SCF-8004-92.description" -msgstr "A FLP chip has detected it does not have sufficient power to continue operating.\n Refer to %s for more information." -msgid "SCF-8004-92.response" -msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-92.impact" -msgstr "The domain using the FLP chip will be reset.\n" -msgid "SCF-8004-92.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-AJ -# keys: fault.chassis.SPARC-Enterprise.asic.mbc.power.fail -# -msgid "SCF-8004-AJ.type" -msgstr "Fault" -msgid "SCF-8004-AJ.severity" -msgstr "Critical" -msgid "SCF-8004-AJ.description" -msgstr "A MBC chip has detected it does not have sufficient power to continue operating.\n Refer to %s for more information." -msgid "SCF-8004-AJ.response" -msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-AJ.impact" -msgstr "Either the platform or a domain will be reset. Please consult the detail section of \nthe knowledge article for additional information.\n" -msgid "SCF-8004-AJ.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-CE -# keys: fault.chassis.SPARC-Enterprise.asic.power.fail -# -msgid "SCF-8004-CE.type" -msgstr "Fault" -msgid "SCF-8004-CE.severity" -msgstr "Critical" -msgid "SCF-8004-CE.description" -msgstr "Some ASIC has detected it does not have sufficient power to continue operating. It is unknown\nwhich type of ASIC detected the falure.\n Refer to %s for more information." -msgid "SCF-8004-CE.response" -msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-CE.impact" -msgstr "Either the platform or a domain will be reset. Please consult the detail section of \nthe knowledge article for additional information.\n" -msgid "SCF-8004-CE.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-DQ -# keys: fault.chassis.power.warning -# -msgid "SCF-8004-DQ.type" -msgstr "Fault" -msgid "SCF-8004-DQ.severity" -msgstr "Minor" -msgid "SCF-8004-DQ.description" -msgstr "An undervoltage or overvoltage warning was detected by a device or FRU.\n Refer to %s for more information." -msgid "SCF-8004-DQ.response" -msgstr "Nothing is deconfigured and no action is taken as a result of this warning.\n" -msgid "SCF-8004-DQ.impact" -msgstr "None.\n" -msgid "SCF-8004-DQ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-EC -# keys: fault.chassis.power.undervoltage -# -msgid "SCF-8004-EC.type" -msgstr "Fault" -msgid "SCF-8004-EC.severity" -msgstr "Critical" -msgid "SCF-8004-EC.description" -msgstr "A serious undervoltage failure has occurred on a device or FRU.\n Refer to %s for more information." -msgid "SCF-8004-EC.response" -msgstr "The device or FRU will be deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8004-EC.impact" -msgstr "Domains may be reset, platform may become unbootable, or the platform may be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-EC.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-FR -# keys: fault.chassis.power.power-off -# -msgid "SCF-8004-FR.type" -msgstr "Fault" -msgid "SCF-8004-FR.severity" -msgstr "Critical" -msgid "SCF-8004-FR.description" -msgstr "An attempt to power-off a FRU or a device has failed during a power-off sequence. \nPlease consult the detail section of the knowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8004-FR.response" -msgstr "The poweroff sequence continues. The FRU or device will be deconfigured and will\nnot be powered up during the next power-on sequence. Please consult the detail section \nof the knowledge article for additional information.\n" -msgid "SCF-8004-FR.impact" -msgstr "Platform may become unbootable. Please consult the detail section of the knowledge \narticle for additional information.\n" -msgid "SCF-8004-FR.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-G4 -# keys: fault.chassis.device.fail -# -msgid "SCF-8004-G4.type" -msgstr "Fault" -msgid "SCF-8004-G4.severity" -msgstr "Critical" -msgid "SCF-8004-G4.description" -msgstr "A component in a FRU has signaled it has failed. Please consult the detail section of \nthe knowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8004-G4.response" -msgstr "The component in the FRU will be deconfigured (which may cause the FRU to be deconfigured). Please \nconsult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-G4.impact" -msgstr "Domains may be reset, the platform may become unbootable, or the platform may be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-G4.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-HY -# keys: fault.chassis.device.misconfig -# -msgid "SCF-8004-HY.type" -msgstr "Fault" -msgid "SCF-8004-HY.severity" -msgstr "Critical" -msgid "SCF-8004-HY.description" -msgstr "An misconfigured FRU or device has been detected during powerup. Please consult the detail \nsection of the knowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8004-HY.response" -msgstr "The misconfigured FRU or device will not be powered up. Please consult the detail section of \nthe knowledge article for additional information.\n" -msgid "SCF-8004-HY.impact" -msgstr "The misconfigured FRU or device will not be powered up. The platform may not powerup.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-HY.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-J3 -# keys: fault.chassis.device.missing -# -msgid "SCF-8004-J3.type" -msgstr "Fault" -msgid "SCF-8004-J3.severity" -msgstr "Critical" -msgid "SCF-8004-J3.description" -msgstr "A FRU or device is missing or could not be detected during powerup. Please consult the detail section \nof the knowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8004-J3.response" -msgstr "If the device is not redundant, powerup of the FRU will be rejected.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-J3.impact" -msgstr "The powerup request for FRU or device may be rejected, or the entire platform may not be powered up.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-J3.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-KH -# keys: fault.chassis.device.inserted -# -msgid "SCF-8004-KH.type" -msgstr "Fault" -msgid "SCF-8004-KH.severity" -msgstr "Minor" -msgid "SCF-8004-KH.description" -msgstr "A FRU's presence was unexpectedly detected. This may be caused by insertion\nof the FRU without following the correct procedure. Please consult the detail section of the \nknowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8004-KH.response" -msgstr "Nothing is deconfigured and no immediate action is taken. The FRU will not be\nconfigured into the system.\n" -msgid "SCF-8004-KH.impact" -msgstr "None.\n" -msgid "SCF-8004-KH.action" -msgstr "If the FRU was inserted without following correct procedure, please use the\ncorrect procedure. Otherwise, schedule a repair action to replace the affected Field \nReplaceable Unit (FRU), the identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-LD -# keys: fault.chassis.device.removed -# -msgid "SCF-8004-LD.type" -msgstr "Fault" -msgid "SCF-8004-LD.severity" -msgstr "Major" -msgid "SCF-8004-LD.description" -msgstr "A FRU's presence detect signal has suddenly disappeared. This may be caused\nby removal of the FRU without following the correct procedure.\nPlease consult the detail section of the knowledge article for additional information.\n Refer to %s for more information." -msgid "SCF-8004-LD.response" -msgstr "The FRU will be deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8004-LD.impact" -msgstr "The platform may be reset, or the platform may be powered down, or a domain may be reset.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-LD.action" -msgstr "If the FRU has not been removed without following the correct procedure,\nschedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8004-MP -# keys: fault.chassis.env.power.loss -# -msgid "SCF-8004-MP.type" -msgstr "Fault" -msgid "SCF-8004-MP.severity" -msgstr "Major" -msgid "SCF-8004-MP.description" -msgstr "PSU has detected a loss of AC power.\n Refer to %s for more information." -msgid "SCF-8004-MP.response" -msgstr "The PSU will be deconfigured. If sufficient operational PSU's remain, the fan speeds of\nall fans will be increased. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8004-MP.impact" -msgstr "If there are insufficient operational PSU's, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-MP.action" -msgstr "The platform administrator should check the AC power connections and schedule a \nservice action, if necessary. Please consult the detail section of the knowledge article \nfor additional information.\n" -# -# code: SCF-8004-NA -# keys: fault.chassis.env.power.ups -# -msgid "SCF-8004-NA.type" -msgstr "Fault" -msgid "SCF-8004-NA.severity" -msgstr "Major" -msgid "SCF-8004-NA.description" -msgstr "Problems have been detected with an external UPS.\n Refer to %s for more information." -msgid "SCF-8004-NA.response" -msgstr "Nothing is deconfigured and no immediate action is taken.\n" -msgid "SCF-8004-NA.impact" -msgstr "None.\n" -msgid "SCF-8004-NA.action" -msgstr "The platform administrator should investigate the UPS.\n" -# -# code: SCF-8004-Q5 -# keys: fault.chassis.SPARC-Enterprise.rci -# -msgid "SCF-8004-Q5.type" -msgstr "Fault" -msgid "SCF-8004-Q5.severity" -msgstr "Critical" -msgid "SCF-8004-Q5.description" -msgstr "Error detected by an RCI device on the RCI Network.\n Refer to %s for more information." -msgid "SCF-8004-Q5.response" -msgstr "Nothing is deconfigured. The entire system may be powered down or there may be no \ncommunication with RCI devices. Please consult the detail section of the knowledge article \nfor additional information.\n" -msgid "SCF-8004-Q5.impact" -msgstr "The entire system may be powered down or there may be no communication with RCI devices.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8004-Q5.action" -msgstr "The platform administrator should use the output of the showlogs command to determine\nwhat type of service action is necessary. Please consult the detail section of the knowledge\narticle for additional information.\n" -# -# code: SCF-8005-0C -# keys: fault.chassis.SPARC-Enterprise.asic.sc.fe-multicmu -# -msgid "SCF-8005-0C.type" -msgstr "Fault" -msgid "SCF-8005-0C.severity" -msgstr "Critical" -msgid "SCF-8005-0C.description" -msgstr "A fatal error was detected within a SC chip. This error may affect multiple CMU's.\n Refer to %s for more information." -msgid "SCF-8005-0C.response" -msgstr "The CMU that contains this SC chip and all its associated IO are deconfigured.\n" -msgid "SCF-8005-0C.impact" -msgstr "One or more domains are reset. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8005-0C.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-1Q -# keys: fault.chassis.SPARC-Enterprise.if.fe-cpu-sc -# -msgid "SCF-8005-1Q.type" -msgstr "Fault" -msgid "SCF-8005-1Q.severity" -msgstr "Critical" -msgid "SCF-8005-1Q.description" -msgstr "A fatal error occurred on the interface between a CPU chip and a SC chip.\n Refer to %s for more information." -msgid "SCF-8005-1Q.response" -msgstr "The CPU chip is deconfigured.\n" -msgid "SCF-8005-1Q.impact" -msgstr "The single domain using the CPU chip is reset.\n" -msgid "SCF-8005-1Q.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-24 -# keys: fault.chassis.SPARC-Enterprise.if.fe-sc-cpu -# -msgid "SCF-8005-24.type" -msgstr "Fault" -msgid "SCF-8005-24.severity" -msgstr "Critical" -msgid "SCF-8005-24.description" -msgstr "A fatal error occurred on the interface between a SC chip and a CPU chip.\n Refer to %s for more information." -msgid "SCF-8005-24.response" -msgstr "The CPU chip is deconfigured.\n" -msgid "SCF-8005-24.impact" -msgstr "The single domain using the CPU chip is reset.\n" -msgid "SCF-8005-24.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-3R -# keys: fault.chassis.SPARC-Enterprise.if.fe-sc-xb -# -msgid "SCF-8005-3R.type" -msgstr "Fault" -msgid "SCF-8005-3R.severity" -msgstr "Critical" -msgid "SCF-8005-3R.description" -msgstr "A fatal error occurred on the interface between a SC chip and a XB chip.\n Refer to %s for more information." -msgid "SCF-8005-3R.response" -msgstr "The CMU containing the SC chip along with all its associated IO is deconfigured.\n" -msgid "SCF-8005-3R.impact" -msgstr "All domains using the CMU are reset.\n" -msgid "SCF-8005-3R.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-5X -# keys: fault.chassis.SPARC-Enterprise.if.fe-mac-sc -# -msgid "SCF-8005-5X.type" -msgstr "Fault" -msgid "SCF-8005-5X.severity" -msgstr "Critical" -msgid "SCF-8005-5X.description" -msgstr "A fatal error occurred on the interface between a MAC chip and a SC chip.\n Refer to %s for more information." -msgid "SCF-8005-5X.response" -msgstr "Memory associated with the MAC chip is deconfigured.\n" -msgid "SCF-8005-5X.impact" -msgstr "One or more domains will be reset. Please consult the detail section of the knowledge \narticle for additional information.\n" -msgid "SCF-8005-5X.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-6E -# keys: fault.chassis.SPARC-Enterprise.if.fe-sc-mac -# -msgid "SCF-8005-6E.type" -msgstr "Fault" -msgid "SCF-8005-6E.severity" -msgstr "Critical" -msgid "SCF-8005-6E.description" -msgstr "A fatal error occurred on the interface between a SC chip and a MAC chip.\n Refer to %s for more information." -msgid "SCF-8005-6E.response" -msgstr "Memory associated with the MAC chip is deconfigured.\n" -msgid "SCF-8005-6E.impact" -msgstr "One or more domains will be reset. Please consult the detail section of the knowledge \narticle for additional information.\n" -msgid "SCF-8005-6E.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-7J -# keys: fault.chassis.SPARC-Enterprise.if.fe-macbank-sc -# -msgid "SCF-8005-7J.type" -msgstr "Fault" -msgid "SCF-8005-7J.severity" -msgstr "Critical" -msgid "SCF-8005-7J.description" -msgstr "A fatal error occurred on the interface between a SC chip and the portion of the MAC chip \ninterfaces with a single memory bank.\n Refer to %s for more information." -msgid "SCF-8005-7J.response" -msgstr "Memory associated with the memory bank is deconfigured.\n" -msgid "SCF-8005-7J.impact" -msgstr "One or more domains will be reset. Please consult the detail section of the knowledge \narticle for additional information.\n" -msgid "SCF-8005-7J.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-8S -# keys: fault.chassis.SPARC-Enterprise.if.fe-ioc-sc -# -msgid "SCF-8005-8S.type" -msgstr "Fault" -msgid "SCF-8005-8S.severity" -msgstr "Critical" -msgid "SCF-8005-8S.description" -msgstr "A fatal error occurred on the interface between an IO Channel and a SC chip.\n Refer to %s for more information." -msgid "SCF-8005-8S.response" -msgstr "The IO Channel is deconfigured.\n" -msgid "SCF-8005-8S.impact" -msgstr "The domain that is using the IO Channel is reset.\n" -msgid "SCF-8005-8S.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-95 -# keys: fault.chassis.SPARC-Enterprise.if.fe-sc-ioc -# -msgid "SCF-8005-95.type" -msgstr "Fault" -msgid "SCF-8005-95.severity" -msgstr "Critical" -msgid "SCF-8005-95.description" -msgstr "A fatal error occurred on the interface between a SC chip and an IO Channel.\n Refer to %s for more information." -msgid "SCF-8005-95.response" -msgstr "The IO Channel is deconfigured.\n" -msgid "SCF-8005-95.impact" -msgstr "The domain that is using the IO Channel is reset.\n" -msgid "SCF-8005-95.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-AP -# keys: fault.chassis.SPARC-Enterprise.if.fe-sc-sc -# -msgid "SCF-8005-AP.type" -msgstr "Fault" -msgid "SCF-8005-AP.severity" -msgstr "Critical" -msgid "SCF-8005-AP.description" -msgstr "A fatal error on the interface between two SC chips has occurred.\n Refer to %s for more information." -msgid "SCF-8005-AP.response" -msgstr "Some number of CPU chips, some number of MAC chips, and some amount of IO will be deconfigured.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8005-AP.impact" -msgstr "One or more domains will be reset. The platform may become unbootable. \nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8005-AP.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-CA -# keys: fault.chassis.SPARC-Enterprise.asic.sc.fe -# -msgid "SCF-8005-CA.type" -msgstr "Fault" -msgid "SCF-8005-CA.severity" -msgstr "Critical" -msgid "SCF-8005-CA.description" -msgstr "A fatal error was detected within a SC chip.\n Refer to %s for more information." -msgid "SCF-8005-CA.response" -msgstr "Some number of CPU chips, some number of MAC chips, and some amount of IO will be deconfigured.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8005-CA.impact" -msgstr "One or more domains will be reset. The platform may become unbootable. Please consult the \ndetail section of the knowledge article for additional information.\n" -msgid "SCF-8005-CA.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-DH -# keys: fault.chassis.SPARC-Enterprise.asic.sc.se -# -msgid "SCF-8005-DH.type" -msgstr "Fault" -msgid "SCF-8005-DH.severity" -msgstr "Critical" -msgid "SCF-8005-DH.description" -msgstr "A non-fatal uncorrectable error was detected within a SC chip.\n Refer to %s for more information." -msgid "SCF-8005-DH.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8005-DH.impact" -msgstr "No immediate action is taken as a result of this fault. The domain may not\nbe operational. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8005-DH.action" -msgstr "The platform administrator should investigate and see if there is some other\nhardware fault that might possibly be related to this fault.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-ED -# keys: fault.chassis.SPARC-Enterprise.if.ce-cpu-sc -# -msgid "SCF-8005-ED.type" -msgstr "Fault" -msgid "SCF-8005-ED.severity" -msgstr "Minor" -msgid "SCF-8005-ED.description" -msgstr "The number of correctable errors on the interface between a CPU chip and a SC chip \nhas exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8005-ED.response" -msgstr "The CPU chip is deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8005-ED.impact" -msgstr "No immediate impact. The CPU chip is deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8005-ED.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-FY -# keys: fault.chassis.SPARC-Enterprise.if.ce-sc-xb -# -msgid "SCF-8005-FY.type" -msgstr "Fault" -msgid "SCF-8005-FY.severity" -msgstr "Major" -msgid "SCF-8005-FY.description" -msgstr "The number of correctable errors on the interface between a SC chip and a XB chip \nhas exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8005-FY.response" -msgstr "The CMU and all its associated IO are deconfigured after the platform is power cycled or \nafter the domains using the CMU reboot or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8005-FY.impact" -msgstr "No immediate impact. The CMU and all its associated IO are deconfigured after the platform is power \ncycled or after the domains using the CMU reboot or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8005-FY.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-G3 -# keys: fault.chassis.SPARC-Enterprise.if.ce-mac-sc -# -msgid "SCF-8005-G3.type" -msgstr "Fault" -msgid "SCF-8005-G3.severity" -msgstr "Minor" -msgid "SCF-8005-G3.description" -msgstr "The number of correctable errors on the interface between a MAC chip and a SC chip\nhas exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8005-G3.response" -msgstr "Memory associated with the MAC is deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8005-G3.impact" -msgstr "No immediate impact. Memory associated with the MAC is deconfigured after the platform is power \ncycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8005-G3.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-HR -# keys: fault.chassis.SPARC-Enterprise.if.ce-ioc-sc -# -msgid "SCF-8005-HR.type" -msgstr "Fault" -msgid "SCF-8005-HR.severity" -msgstr "Major" -msgid "SCF-8005-HR.description" -msgstr "The number of correctable errors on the interface between an IO Channel and a SC chip \nhas exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8005-HR.response" -msgstr "The IO Channel is deconfigured after the platform is power cycled or after the domain reboots or after a \nDynamic Reconfiguration operation is performed.\n" -msgid "SCF-8005-HR.impact" -msgstr "No immediate impact. The IO Channel is deconfigured after the platform is power cycled or after the domain \nreboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8005-HR.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-J4 -# keys: fault.chassis.SPARC-Enterprise.if.ce-sc-sc -# -msgid "SCF-8005-J4.type" -msgstr "Fault" -msgid "SCF-8005-J4.severity" -msgstr "Critical" -msgid "SCF-8005-J4.description" -msgstr "The number of correctable errors on the interface between two SC chips has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8005-J4.response" -msgstr "Some resources associated with the SC chips (CPU chips, memory, IO Channels) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8005-J4.impact" -msgstr "No immediate impact. Some resources associated with the SC chips (CPU chips, memory, IO Channels) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8005-J4.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-KQ -# keys: fault.chassis.SPARC-Enterprise.asic.sc.ce -# -msgid "SCF-8005-KQ.type" -msgstr "Fault" -msgid "SCF-8005-KQ.severity" -msgstr "Critical" -msgid "SCF-8005-KQ.description" -msgstr "The number of correctable errors detected within a SC chip has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8005-KQ.response" -msgstr "Some resources associated with the SC chip (CPU chips, memory, IO Channels) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8005-KQ.impact" -msgstr "No immediate impact. Some resources associated with the SC chip (CPU chips, memory, IO Channels) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8005-KQ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-LC -# keys: fault.chassis.SPARC-Enterprise.asic.sc.ce-l2tagcpu -# -msgid "SCF-8005-LC.type" -msgstr "Fault" -msgid "SCF-8005-LC.severity" -msgstr "Minor" -msgid "SCF-8005-LC.description" -msgstr "The number of correctable errors within the L2 cache tags of a SC chip has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8005-LC.response" -msgstr "One of the L2 cache ways is deconfigured for all the CPU chips associated with this SC chip.\n" -msgid "SCF-8005-LC.impact" -msgstr "The domain is unaffected, except for the performance of the CPU chips.\n" -msgid "SCF-8005-LC.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-MJ -# keys: fault.chassis.SPARC-Enterprise.asic.sc.test -# -msgid "SCF-8005-MJ.type" -msgstr "Fault" -msgid "SCF-8005-MJ.severity" -msgstr "Critical" -msgid "SCF-8005-MJ.description" -msgstr "Self-test error detected within a SC chip or a SC chip interface to another chip.\n Refer to %s for more information." -msgid "SCF-8005-MJ.response" -msgstr "Some number of CPU chips, some number of MAC chips, and some amount of IO will be deconfigured.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8005-MJ.impact" -msgstr "Running domains are unaffected by this fault, as this occurs during self-test. The\nplatform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n" -msgid "SCF-8005-MJ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-NE -# keys: defect.chassis.software -# -msgid "SCF-8005-NE.type" -msgstr "Defect" -msgid "SCF-8005-NE.severity" -msgstr "Major" -msgid "SCF-8005-NE.description" -msgstr "An XSCF firmware process has unexpectedly terminated. \n Refer to %s for more information." -msgid "SCF-8005-NE.response" -msgstr "The XSCF firmware will be rebooted.\n" -msgid "SCF-8005-NE.impact" -msgstr "XSCF functionality will be unavailable until the XSCF has restarted.\n" -msgid "SCF-8005-NE.action" -msgstr "Schedule a repair action to upgrade the XCP firmware. Please consult the detail section \nof the knowledge article for additional information.\n" -# -# code: SCF-8005-PX -# keys: upset.chassis.domain.panic -# -msgid "SCF-8005-PX.type" -msgstr "Upset" -msgid "SCF-8005-PX.severity" -msgstr "Major" -msgid "SCF-8005-PX.description" -msgstr "The XSCF has detected that an illumos domain has panic'ed.\n Refer to %s for more information." -msgid "SCF-8005-PX.response" -msgstr "No action is taken due to this fault.\n" -msgid "SCF-8005-PX.impact" -msgstr "The illumos domain has panic'ed.\n" -msgid "SCF-8005-PX.action" -msgstr "The administrator should look at the domain's console to identify the cause of the panic.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-Q2 -# keys: upset.chassis.domain.config -# -msgid "SCF-8005-Q2.type" -msgstr "Upset" -msgid "SCF-8005-Q2.severity" -msgstr "Major" -msgid "SCF-8005-Q2.description" -msgstr "The XSB could not be successfully configured into a domain.\n Refer to %s for more information." -msgid "SCF-8005-Q2.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8005-Q2.impact" -msgstr "XSB is not successfully configured into a domain.\n" -msgid "SCF-8005-Q2.action" -msgstr "The platform administrator should investigate why the XSB could not be configured \ninto the domain. Please consult the detail section of the knowledge article for additional \ninformation.\n" -# -# code: SCF-8005-RA -# keys: upset.chassis.domain.post -# -msgid "SCF-8005-RA.type" -msgstr "Upset" -msgid "SCF-8005-RA.severity" -msgstr "Major" -msgid "SCF-8005-RA.description" -msgstr "The XSCF could not determine whether POST is running correctly on a domain/XSB.\n Refer to %s for more information." -msgid "SCF-8005-RA.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8005-RA.impact" -msgstr "The domain or the XSB will be powered down.\n" -msgid "SCF-8005-RA.action" -msgstr "The platform administrator should check for some sort of fault that could have\ncaused this failure. Please consult the detail section of the knowledge article for additional \ninformation.\n" -# -# code: SCF-8005-SP -# keys: upset.chassis.domain.keepalive.msg-fail -# -msgid "SCF-8005-SP.type" -msgstr "Upset" -msgid "SCF-8005-SP.severity" -msgstr "Major" -msgid "SCF-8005-SP.description" -msgstr "Domain does not respond to XSCF keep-alive messages.\n Refer to %s for more information." -msgid "SCF-8005-SP.response" -msgstr "The XSCF will send a message to the domain asking it to panic.\n" -msgid "SCF-8005-SP.impact" -msgstr "The XSCF will send a message to the domain asking it to panic.\n" -msgid "SCF-8005-SP.action" -msgstr "To investigate potential hardware problems, the platform administrator should\nlook at the fault logs on the XSCF to determine if there is some other hardware\nproblem that may be causing the upset. Please consult the detail section of \nthe knowledge article for additional information.\n" -# -# code: SCF-8005-T5 -# keys: upset.chassis.domain.tty-overflow -# -msgid "SCF-8005-T5.type" -msgstr "Upset" -msgid "SCF-8005-T5.severity" -msgstr "Minor" -msgid "SCF-8005-T5.description" -msgstr "TTY buffer for a domain overflowed, resulting in lost domain console data.\n Refer to %s for more information." -msgid "SCF-8005-T5.response" -msgstr "No action is taken as a result of this fault.\n" -msgid "SCF-8005-T5.impact" -msgstr "Domain console data is lost.\n" -msgid "SCF-8005-T5.action" -msgstr "None. Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8005-US -# keys: upset.chassis.domain.keepalive.panic-fail -# -msgid "SCF-8005-US.type" -msgstr "Upset" -msgid "SCF-8005-US.severity" -msgstr "Major" -msgid "SCF-8005-US.description" -msgstr "Domain did not respond to an XSCF request for it to panic.\n Refer to %s for more information." -msgid "SCF-8005-US.response" -msgstr "The XSCF will send an XIR interrupt to the domain.\n" -msgid "SCF-8005-US.impact" -msgstr "The XSCF will send an XIR interrupt to the domain.\n" -msgid "SCF-8005-US.action" -msgstr "The platform administrator should look at the fault logs on the XSCF to determine if there is \nsome hardware problem that may be causing the upset. Please consult the detail section of \nthe knowledge article for additional information.\n" -# -# code: SCF-8005-V3 -# keys: upset.chassis.domain.keepalive.xir-fail -# -msgid "SCF-8005-V3.type" -msgstr "Upset" -msgid "SCF-8005-V3.severity" -msgstr "Major" -msgid "SCF-8005-V3.description" -msgstr "Domain did not respond to an XIR interrupt sent by the XSCF.\n Refer to %s for more information." -msgid "SCF-8005-V3.response" -msgstr "The XSCF will attempt to reset the domain.\n" -msgid "SCF-8005-V3.impact" -msgstr "The XSCF will attempt to reset the domain.\n" -msgid "SCF-8005-V3.action" -msgstr "The platform administrator should look at the fault logs on the XSCF to determine if there is \nsome hardware problem that may be causing the upset. Please consult the detail section of \nthe knowledge article for additional information.\n" -# -# code: SCF-8005-WY -# keys: upset.chassis.domain.keepalive.reset-fail -# -msgid "SCF-8005-WY.type" -msgstr "Upset" -msgid "SCF-8005-WY.severity" -msgstr "Major" -msgid "SCF-8005-WY.description" -msgstr "Domain does not respond to the XSCF's request to reset itself.\n Refer to %s for more information." -msgid "SCF-8005-WY.response" -msgstr "The XSCF will power the domain down.\n" -msgid "SCF-8005-WY.impact" -msgstr "The XSCF will power the domain down.\n" -msgid "SCF-8005-WY.action" -msgstr "The platform administrator should look at the fault logs on the XSCF to determine if there is \nsome hardware problem that may be causing the upset. Please consult the detail section of \nthe knowledge article for additional information.\n" -# -# code: SCF-8005-YH -# keys: fault.chassis.device.fan.tooslow -# -msgid "SCF-8005-YH.type" -msgstr "Fault" -msgid "SCF-8005-YH.severity" -msgstr "Major" -msgid "SCF-8005-YH.description" -msgstr "The fan rotation speed for a fan is lower is than its predefined threshold or a fan \nhas stopped completely.\n Refer to %s for more information." -msgid "SCF-8005-YH.response" -msgstr "If there are sufficient fans to maintain normal operation, fan speeds for fans on the \nrest of the platform are raised. If there are insufficient fans to maintain normal\noperation, domains are requested to shut down.\n" -msgid "SCF-8005-YH.impact" -msgstr "If there are insufficient fans to maintain normal operation, domains are sent shutdown requests.\nIf the fan is in a PSU, the PSU is deconfigured.\n" -msgid "SCF-8005-YH.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-02 -# keys: fault.chassis.device.fan.speedchange -# -msgid "SCF-8006-02.type" -msgstr "Fault" -msgid "SCF-8006-02.severity" -msgstr "Minor" -msgid "SCF-8006-02.description" -msgstr "Fan rotation speed either dropped below a threshold or rose above a threshold during fan speed change\ntesting.\n Refer to %s for more information." -msgid "SCF-8006-02.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8006-02.impact" -msgstr "No action is taken.\n" -msgid "SCF-8006-02.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-1X -# keys: fault.chassis.env.temp.under -# -msgid "SCF-8006-1X.type" -msgstr "Fault" -msgid "SCF-8006-1X.severity" -msgstr "Critical" -msgid "SCF-8006-1X.description" -msgstr "Under temperature condition detected by the inlet temperature sensor.\n Refer to %s for more information." -msgid "SCF-8006-1X.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8006-1X.impact" -msgstr "System may crash due to ASIC's operating outside their intended temperature ranges.\n" -msgid "SCF-8006-1X.action" -msgstr "The platform administrator should check for the cause of the under temperature condition.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-2E -# keys: fault.chassis.env.temp.over -# -msgid "SCF-8006-2E.type" -msgstr "Fault" -msgid "SCF-8006-2E.severity" -msgstr "Major" -msgid "SCF-8006-2E.description" -msgstr "Over-temperature condition detected by an inlet temperature sensor, exhaust temperature sensor, \nor CPU temperature sensor.\n Refer to %s for more information." -msgid "SCF-8006-2E.response" -msgstr "Fan speed will be raised for all fans on the platform.\n" -msgid "SCF-8006-2E.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8006-2E.action" -msgstr "Platform administrator should investigate the cause of the over-temperature condition.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-3J -# keys: fault.chassis.env.temp.over-warn -# -msgid "SCF-8006-3J.type" -msgstr "Fault" -msgid "SCF-8006-3J.severity" -msgstr "Critical" -msgid "SCF-8006-3J.description" -msgstr "Over-temperature warning condition has been detected by inlet temperature sensor, exhaust temperature \nsensor, or CPU temperature sensor.\n Refer to %s for more information." -msgid "SCF-8006-3J.response" -msgstr "Fan speed will be raised for all fans on the platform. Shutdown messages will be sent to \ndomains on the platform.\n" -msgid "SCF-8006-3J.impact" -msgstr "Shutdown messages will be sent to domains on the platform.\n" -msgid "SCF-8006-3J.action" -msgstr "Platform administrator should investigate the cause of the over-temperature condition.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-4C -# keys: fault.chassis.env.temp.over-fail -# -msgid "SCF-8006-4C.type" -msgstr "Fault" -msgid "SCF-8006-4C.severity" -msgstr "Critical" -msgid "SCF-8006-4C.description" -msgstr "Dangerous over-temperature condition detected by an exhaust temperature sensor or CPU \ntemperature sensor.\n Refer to %s for more information." -msgid "SCF-8006-4C.response" -msgstr "Nothing is deconfigured. Either the platform will be powered down or specific domains will \nbe powered down. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-4C.impact" -msgstr "Either the platform will be powered down or specific domains will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-4C.action" -msgstr "Platform administrator should investigate the cause of the over-temperature condition.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-9D -# keys: fault.chassis.SPARC-Enterprise.if.fe-ioc-xb -# -msgid "SCF-8006-9D.type" -msgstr "Fault" -msgid "SCF-8006-9D.severity" -msgstr "Critical" -msgid "SCF-8006-9D.description" -msgstr "A fatal error occurred on an interface between a XB chip and an IOC chip.\n Refer to %s for more information." -msgid "SCF-8006-9D.response" -msgstr "Either the entire IOC chip or a single IO Channel will be deconfigured,\ndepending upon whether a crossbar way was deconfigured prior to the fault.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-9D.impact" -msgstr "One or two domains will be reset, depending upon whether a crossbar way was deconfigured\nprior to the fault. Please consult the detail section of the knowledge article for additional \ninformation.\n" -msgid "SCF-8006-9D.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-AY -# keys: fault.chassis.SPARC-Enterprise.if.fe-xb-ioc -# -msgid "SCF-8006-AY.type" -msgstr "Fault" -msgid "SCF-8006-AY.severity" -msgstr "Critical" -msgid "SCF-8006-AY.description" -msgstr "A fatal error has occurred on an interface between a SC chip and an IOC chip,\nvia an XB chip.\n Refer to %s for more information." -msgid "SCF-8006-AY.response" -msgstr "Either the entire IOC chip or a single IO Channel will be deconfigured depending upon whether a \ncrossbar way was deconfigured prior to the fault. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8006-AY.impact" -msgstr "One or two domains will be reset, depending upon whether a crossbar way was deconfigured\nprior to the fault. Please consult the detail section of the knowledge article for additional \ninformation.\n" -msgid "SCF-8006-AY.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-C3 -# keys: fault.chassis.SPARC-Enterprise.if.fe-xb-xbucable -# -msgid "SCF-8006-C3.type" -msgstr "Fault" -msgid "SCF-8006-C3.severity" -msgstr "Major" -msgid "SCF-8006-C3.description" -msgstr "A fatal error has been detected on the cable interface between two XBU's.\n Refer to %s for more information." -msgid "SCF-8006-C3.response" -msgstr "If a crossbar way has been deconfigured, the platform is powered down. Otherwise,\na crossbar way is deconfigured. Please consult the detail section of the knowledge \narticle for additional information.\n" -msgid "SCF-8006-C3.impact" -msgstr "The entire platform is reset. If a crossbar way has been deconfigured, the platform is \npowered down. Otherwise, a crossbar way is deconfigured and the platform continues\nto operate with reduced performance. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8006-C3.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-DS -# keys: fault.chassis.SPARC-Enterprise.if.fe-xb-xb -# -msgid "SCF-8006-DS.type" -msgstr "Fault" -msgid "SCF-8006-DS.severity" -msgstr "Critical" -msgid "SCF-8006-DS.description" -msgstr "A fatal error has been detected on the interface between two XB chips.\n Refer to %s for more information." -msgid "SCF-8006-DS.response" -msgstr "If the fault can be isolated to a CMU, the CMU and all its associated IO are deconfigured. \nIf the fault cannot be isolated to a single CMU, if a crossbar way has been deconfigured, the platform \nis powered down. Otherwise, a crossbar way is deconfigured and the platform continues to operate with \nreduced performance. Please consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-DS.impact" -msgstr "If the fault can be isolated to a CMU, then one or more domains are reset and the CMU and all\nits associated IO are deconfigured. If the fault cannot be isolated to a single CMU, the entire platform is \nreset. If a crossbar way has been deconfigured, the platform is powered down. Otherwise, a crossbar way \nis deconfigured and the platform continues to operate with reduced performance.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-DS.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-E5 -# keys: upset.chassis.SPARC-Enterprise.if.fe-xb -# -msgid "SCF-8006-E5.type" -msgstr "Upset" -msgid "SCF-8006-E5.severity" -msgstr "Critical" -msgid "SCF-8006-E5.description" -msgstr "A fatal protocol error detected by a XB chip.\n Refer to %s for more information." -msgid "SCF-8006-E5.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8006-E5.impact" -msgstr "The entire platform is reset.\n" -msgid "SCF-8006-E5.action" -msgstr "The component that is at fault is difficult to determine.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-FP -# keys: fault.chassis.SPARC-Enterprise.asic.xb.fe -# -msgid "SCF-8006-FP.type" -msgstr "Fault" -msgid "SCF-8006-FP.severity" -msgstr "Critical" -msgid "SCF-8006-FP.description" -msgstr "A fatal error was detected within a XB chip.\n Refer to %s for more information." -msgid "SCF-8006-FP.response" -msgstr "Depending upon which part of the XB chip is faulty, either a crossbar way is deconfigured,\nor a CMU and all its associated IO are deconfigured, or an IOC chip is deconfigured,\nor an IO Channel within an IOC chip is deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8006-FP.impact" -msgstr "Depending upon which part of the XB chip is faulty, either the entire platform is\nreset, or one or more domains are reset. If the response includes deconfiguring a crossbar\nway and this is the first crossbar way to be deconfigured, the platform will operate\nwith reduced performance. If the response includes deconfiguring a crossbar way\nand a crossbar way has already been deconfigured, the platform is powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-FP.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-GA -# keys: fault.chassis.SPARC-Enterprise.if.ce-ioc-xb -# -msgid "SCF-8006-GA.type" -msgstr "Fault" -msgid "SCF-8006-GA.severity" -msgstr "Major" -msgid "SCF-8006-GA.description" -msgstr "The number of correctable errors on the interface between an XB chip and an IOC chip\nhas exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8006-GA.response" -msgstr "Depending upon whether a crossbar way has already been deconfigured, either an IOC chip or an\nIOC channel will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-GA.impact" -msgstr "No immediate impact. Depending upon whether a crossbar way has already been deconfigured, either an IOC \nchip or an IOC channel will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-GA.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-HJ -# keys: fault.chassis.SPARC-Enterprise.if.ce-xb-xbucable -# -msgid "SCF-8006-HJ.type" -msgstr "Fault" -msgid "SCF-8006-HJ.severity" -msgstr "Major" -msgid "SCF-8006-HJ.description" -msgstr "The number of correctable errors on the interface between two XB chips communicating\nover an XBU cable has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8006-HJ.response" -msgstr "The crossbar way is deconfigured the next time the platform is restarted. If this is the\nfirst crossbar way to be deconfigured, the platform will operate with reduced performance.\nIf a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-HJ.impact" -msgstr "No immediate impact. The crossbar way is deconfigured the next time the platform is restarted. \nIf this is the first crossbar way to be deconfigured, the platform will operate with reduced \nperformance. If a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-HJ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-JE -# keys: fault.chassis.SPARC-Enterprise.if.ce-xb-xb -# -msgid "SCF-8006-JE.type" -msgstr "Fault" -msgid "SCF-8006-JE.severity" -msgstr "Major" -msgid "SCF-8006-JE.description" -msgstr "The number of correctable errors on the interface between two XB chips on the same XBU\nhas exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8006-JE.response" -msgstr "The crossbar way is deconfigured the next time the platform is restarted. If this is the\nfirst crossbar way to be deconfigured, the platform will operate with reduced performance.\nIf a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-JE.impact" -msgstr "No immediate impact. The crossbar way is deconfigured the next time the platform is restarted. \nIf this is the first crossbar way to be deconfigured, the platform will operate with reduced \nperformance. If a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-JE.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-KX -# keys: fault.chassis.SPARC-Enterprise.asic.xb.ce -# -msgid "SCF-8006-KX.type" -msgstr "Fault" -msgid "SCF-8006-KX.severity" -msgstr "Major" -msgid "SCF-8006-KX.description" -msgstr "The number of correctable errors within a XB chip has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8006-KX.response" -msgstr "The crossbar way is deconfigured the next time the platform is restarted. If this is the\nfirst crossbar way to be deconfigured, the platform will operate with reduced performance.\nIf a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-KX.impact" -msgstr "No immediate impact. The crossbar way is deconfigured the next time the platform is restarted. \nIf this is the first crossbar way to be deconfigured, the platform will operate with reduced \nperformance. If a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-KX.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-L2 -# keys: fault.chassis.SPARC-Enterprise.asic.xb.test -# -msgid "SCF-8006-L2.type" -msgstr "Fault" -msgid "SCF-8006-L2.severity" -msgstr "Major" -msgid "SCF-8006-L2.description" -msgstr "Self-test error detected within a XB chip or within the interface of the\nXB chip to another chip.\n Refer to %s for more information." -msgid "SCF-8006-L2.response" -msgstr "Depending upon which part of the XB chip is faulty, either a crossbar way is deconfigured,\nor a CMU and all its associated IO are deconfigured, or an IOC chip is deconfigured,\nor an IO Channel within an IOC chip is deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n" -msgid "SCF-8006-L2.impact" -msgstr "Depending upon which part of the XB chip is faulty, either the entire platform is\nreset, or one or more domains are reset. If the response includes deconfiguring a crossbar\nway and this is the first crossbar way to be deconfigured, the platform will operate\nwith reduced performance. If the response includes deconfiguring a crossbar way\nand a crossbar way has already been deconfigured, the platform is powered down.\nDomains are not affected, as this fault can only occur while the platform is powering up.\nPlease consult the detail section of the knowledge article for additional information.\n" -msgid "SCF-8006-L2.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-MR -# keys: fault.chassis.SPARC-Enterprise.asic.xb.fe-multicmu -# -msgid "SCF-8006-MR.type" -msgstr "Fault" -msgid "SCF-8006-MR.severity" -msgstr "Critical" -msgid "SCF-8006-MR.description" -msgstr "Fatal error detected within a XB chip. This fatal error may affect multiple CMU's.\n Refer to %s for more information." -msgid "SCF-8006-MR.response" -msgstr "The CMU and all its associated IO are deconfigured.\n" -msgid "SCF-8006-MR.impact" -msgstr "The domains running on the CMU that is deconfigured will be reset. Other\ndomains on the platform may also be reset. The CMU and all its associated \nIO are deconfigured.\n" -msgid "SCF-8006-MR.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-WP -# keys: fault.chassis.SPARC-Enterprise.xscfu -# -msgid "SCF-8006-WP.type" -msgstr "Fault" -msgid "SCF-8006-WP.severity" -msgstr "Major" -msgid "SCF-8006-WP.description" -msgstr "Hardware problem detected within an XSCFU.\n Refer to %s for more information." -msgid "SCF-8006-WP.response" -msgstr "The platform may become unmanageable. The platform may not be able to reboot. If the configuration\nhas redundant XSCFUs, the XSCF software may fail over to the other XSCFU. If the configuration has\nredundant XSCFUs, XSCFU failover may be disabled. Please consult the detail section of the knowledge \narticle for additional information.\n" -msgid "SCF-8006-WP.impact" -msgstr "The domains will continue to run. The platform may become unmanageable. The platform\nmay not be able to reboot. If the configuration has redundant XSCFUs, the XSCF software may\nfail over to the other XSCFU. If the configuration has redundant XSCFUs, XSCFU failover may\nbe disabled. Please consult the detail section of the knowledge article for additional \ninformation.\n" -msgid "SCF-8006-WP.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-X5 -# keys: fault.chassis.device.mismatch -# -msgid "SCF-8006-X5.type" -msgstr "Fault" -msgid "SCF-8006-X5.severity" -msgstr "Critical" -msgid "SCF-8006-X5.description" -msgstr "The XSCFU_C and XSCFU_B have mismatched board numbers. This problem will only\noccur during platform power-on.\n Refer to %s for more information." -msgid "SCF-8006-X5.response" -msgstr "No domains will be allowed to be powered up until the problem is corrected.\n" -msgid "SCF-8006-X5.impact" -msgstr "The entire platform is unbootable.\n" -msgid "SCF-8006-X5.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8006-YS -# keys: upset.chassis.SPARC-Enterprise.xscfu -# -msgid "SCF-8006-YS.type" -msgstr "upset" -msgid "SCF-8006-YS.severity" -msgstr "Minor" -msgid "SCF-8006-YS.description" -msgstr "A hard-to-diagnose failure of the XSCF has occurred.\n Refer to %s for more information." -msgid "SCF-8006-YS.response" -msgstr "The XSCFU will reboot. If the configuration has redundant XSCFU's, the standby XSCFU \nmay take over as the active XSCFU.\n" -msgid "SCF-8006-YS.impact" -msgstr "The XSCFU will reboot. If the configuration has redundant XSCFU's, the standby XSCFU \nmay take over as the active XSCFU. There is no impact to the domains.\n" -msgid "SCF-8006-YS.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-05 -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.fe -# -msgid "SCF-8007-05.type" -msgstr "Fault" -msgid "SCF-8007-05.severity" -msgstr "Critical" -msgid "SCF-8007-05.description" -msgstr "An internal fatal error within a CPU chip was detected.\n Refer to %s for more information." -msgid "SCF-8007-05.response" -msgstr "The domain using this CPU will be reset and the CPU chip will be deconfigured.\n" -msgid "SCF-8007-05.impact" -msgstr "The CPU chip will be deconfigured after the domain is reset.\n" -msgid "SCF-8007-05.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-1S -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.fe -# -msgid "SCF-8007-1S.type" -msgstr "Fault" -msgid "SCF-8007-1S.severity" -msgstr "Critical" -msgid "SCF-8007-1S.description" -msgstr "An internal fatal error within a core on a CPU chip was detected.\n Refer to %s for more information." -msgid "SCF-8007-1S.response" -msgstr "The domain using this CPU will be reset and the core will be deconfigured.\n" -msgid "SCF-8007-1S.impact" -msgstr "The domain using this CPU chip is reset.\n" -msgid "SCF-8007-1S.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-2A -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.strand.fe -# -msgid "SCF-8007-2A.type" -msgstr "Fault" -msgid "SCF-8007-2A.severity" -msgstr "Critical" -msgid "SCF-8007-2A.description" -msgstr "An internal fatal error within a strand on a CPU chip was detected.\n Refer to %s for more information." -msgid "SCF-8007-2A.response" -msgstr "The domain using this CPU will be reset and the strand will be deconfigured.\n" -msgid "SCF-8007-2A.impact" -msgstr "The domain using this CPU chip is reset.\n" -msgid "SCF-8007-2A.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-3P -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.se -# -msgid "SCF-8007-3P.type" -msgstr "Fault" -msgid "SCF-8007-3P.severity" -msgstr "Major" -msgid "SCF-8007-3P.description" -msgstr "An internal non-fatal uncorrectable error within a CPU chip has been detected.\n Refer to %s for more information." -msgid "SCF-8007-3P.response" -msgstr "The CPU chip will be deconfigured after the platform is power cycled or after the domain reboots \nor after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8007-3P.impact" -msgstr "The non-fatal uncorrectable error may cause domain to panic. The CPU chip will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8007-3P.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-4D -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.se -# -msgid "SCF-8007-4D.type" -msgstr "Fault" -msgid "SCF-8007-4D.severity" -msgstr "Major" -msgid "SCF-8007-4D.description" -msgstr "A non-fatal uncorrectable error associated with a core on a CPU chip has been detected.\n Refer to %s for more information." -msgid "SCF-8007-4D.response" -msgstr "The domain software will attempt to offline the core on the CPU chip.\n" -msgid "SCF-8007-4D.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. If the domain\ndoes not panic, the domain software will attempt to offline the core on the CPU chip.\nThe core of the CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8007-4D.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-5H -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.se-offlinereq -# -msgid "SCF-8007-5H.type" -msgstr "Fault" -msgid "SCF-8007-5H.severity" -msgstr "Major" -msgid "SCF-8007-5H.description" -msgstr "When a non-fatal uncorrectable error occurs on a core on a CPU chip, domain software attempts to\noffline the core. This fault occurs when the number of offline attempts has exceeded an\nacceptable threshold.\n Refer to %s for more information." -msgid "SCF-8007-5H.response" -msgstr "Future non-fatal uncorrectable errors for this core on a CPU chip will not be recorded on the XSCF.\n" -msgid "SCF-8007-5H.impact" -msgstr "The uncorrectable error trap may cause the domain to panic.\n" -msgid "SCF-8007-5H.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-63 -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.strand.se -# -msgid "SCF-8007-63.type" -msgstr "Fault" -msgid "SCF-8007-63.severity" -msgstr "Major" -msgid "SCF-8007-63.description" -msgstr "A non-fatal uncorrectable error has been detected on a strand on a CPU chip.\n Refer to %s for more information." -msgid "SCF-8007-63.response" -msgstr "The strand on the CPU chip is deconfigured.\n" -msgid "SCF-8007-63.impact" -msgstr "The non-fatal uncorrectable error trap may cause the domain to panic.\n" -msgid "SCF-8007-63.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-7Y -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.ce -# -msgid "SCF-8007-7Y.type" -msgstr "Fault" -msgid "SCF-8007-7Y.severity" -msgstr "Major" -msgid "SCF-8007-7Y.description" -msgstr "The number of correctable errors associated with a CPU chip has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8007-7Y.response" -msgstr "The CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8007-7Y.impact" -msgstr "No immediate impact. The CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8007-7Y.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-8Q -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.ce -# -msgid "SCF-8007-8Q.type" -msgstr "Fault" -msgid "SCF-8007-8Q.severity" -msgstr "Major" -msgid "SCF-8007-8Q.description" -msgstr "The number of correctable errors associated with a core on a CPU chip have exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8007-8Q.response" -msgstr "A request is sent to the domain software to attempt to offline the core on the CPU chip.\nThe core of the CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n" -msgid "SCF-8007-8Q.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8007-8Q.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-9C -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.ce-offlinereq -# -msgid "SCF-8007-9C.type" -msgstr "Fault" -msgid "SCF-8007-9C.severity" -msgstr "Major" -msgid "SCF-8007-9C.description" -msgstr "The number of correctable errors on a core on a CPU chip has exceeded an acceptable threshold. \nThis fault occurs when the number of offline attempts has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8007-9C.response" -msgstr "Future correctable errors for this core on a CPU chip will not be recorded on the XSCF.\n" -msgid "SCF-8007-9C.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8007-9C.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-AR -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.way.ce -# -msgid "SCF-8007-AR.type" -msgstr "Fault" -msgid "SCF-8007-AR.severity" -msgstr "Minor" -msgid "SCF-8007-AR.description" -msgstr "The number of correctable errors within a way of a CPU chip's L2 cache has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8007-AR.response" -msgstr "The way of the CPU chip's cache is deconfigured. The performance of the CPU chip is reduced.\n" -msgid "SCF-8007-AR.impact" -msgstr "There is a performance loss for the CPU chip.\n" -msgid "SCF-8007-AR.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-C4 -# keys: upset.chassis.SPARC-Enterprise.cpu.SPARC64-VII.fe -# -msgid "SCF-8007-C4.type" -msgstr "Upset" -msgid "SCF-8007-C4.severity" -msgstr "Critical" -msgid "SCF-8007-C4.description" -msgstr "A hard-to-diagnose problem was detected by the CPU chip.\n Refer to %s for more information." -msgid "SCF-8007-C4.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8007-C4.impact" -msgstr "The domain may drop to the OpenBoot PROM 'OK' prompt.\n" -msgid "SCF-8007-C4.action" -msgstr "The platform administrator should check to see if any other hardware failure has occurred on the platform.\nIf the problem occurs while running OpenBoot PROM, then the platform administrator should check to make sure that \nthe OpenBoot PROM environment variables have not been set incorrectly. If neither of these courses of action \nprovide a resolution, then the platform administrator should schedule a service action.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-DX -# keys: upset.chassis.SPARC-Enterprise.cpu.SPARC64-VII.fe-unexpected-trap -# -msgid "SCF-8007-DX.type" -msgstr "upset" -msgid "SCF-8007-DX.severity" -msgstr "Critical" -msgid "SCF-8007-DX.description" -msgstr "An unexpected trap with some unknown cause was detected by a CPU chip during POST.\n Refer to %s for more information." -msgid "SCF-8007-DX.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8007-DX.impact" -msgstr "The domain is reset.\n" -msgid "SCF-8007-DX.action" -msgstr "Please consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-E2 -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.se-tmo -# -msgid "SCF-8007-E2.type" -msgstr "Fault" -msgid "SCF-8007-E2.severity" -msgstr "Major" -msgid "SCF-8007-E2.description" -msgstr "An internal non-fatal uncorrectable error has been detected within the CPU chip.\n Refer to %s for more information." -msgid "SCF-8007-E2.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8007-E2.impact" -msgstr "The non-fatal uncorrectable error may cause the domain to panic.\n" -msgid "SCF-8007-E2.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-FJ -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.se-uncertain -# -msgid "SCF-8007-FJ.type" -msgstr "Fault" -msgid "SCF-8007-FJ.severity" -msgstr "Major" -msgid "SCF-8007-FJ.description" -msgstr "An internal non-fatal uncorrectable error has been detected within the CPU chip.\n Refer to %s for more information." -msgid "SCF-8007-FJ.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8007-FJ.impact" -msgstr "The non-fatal uncorrectable error may cause the domain to panic.\n" -msgid "SCF-8007-FJ.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" -# -# code: SCF-8007-GE -# keys: fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.ce-warn -# -msgid "SCF-8007-GE.type" -msgstr "Fault" -msgid "SCF-8007-GE.severity" -msgstr "Minor" -msgid "SCF-8007-GE.description" -msgstr "The number of correctable errors associated with a CPU chip has exceeded an acceptable threshold.\n Refer to %s for more information." -msgid "SCF-8007-GE.response" -msgstr "Nothing is deconfigured.\n" -msgid "SCF-8007-GE.impact" -msgstr "No immediate impact.\n" -msgid "SCF-8007-GE.action" -msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n" diff --git a/usr/src/cmd/fm/dicts/SUN4.dict b/usr/src/cmd/fm/dicts/SUN4.dict deleted file mode 100644 index 3234ae5aa9..0000000000 --- a/usr/src/cmd/fm/dicts/SUN4.dict +++ /dev/null @@ -1,50 +0,0 @@ -# -# Copyright 2007 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -#ident "%Z%%M% %I% %E% SMI" -# -# DO NOT EDIT -- this file is generated by the Event Registry. -# - -FMDICT: name=SUN4 version=1 maxkey=3 dictid=0x5334 - -fault.io.fire.asic=0 -fault.io.ebus=1 -fault.io.datapath=2 -fault.io.hbus=3 -fault.io.fire.pciex.device=4 -defect.io.fire.pciex.driver=5 -fault.io.datapath fault.io.fire.asic=6 -fault.io.fire.asic fault.io.fire.pciex.device=7 -defect.io.fire.pci.driver defect.io.fire.pciex.driver=8 -fault.io.fire.pci.device fault.io.fire.pciex.device=9 -fault.io.fire.pci.device=10 -defect.io.fire.pciex.driver fault.io.datapath fault.io.fire.asic=11 -fault.io.fire.asic fault.io.fire.pci.device fault.io.fire.pciex.device=12 -fault.io.fire.asic fault.io.fire.pci.device=13 -fault.io.fire.hbus=14 -fault.io.fire.datapath fault.io.fire.hbus=15 -fault.io.fire.hb.sw-config=16 -fault.io.fire.dmc.sw-algorithm=17 -fault.io.fire.dmc.sw-state=18 -fault.io.fire.pec.sw-algorithm=19 diff --git a/usr/src/cmd/fm/dicts/SUN4.po b/usr/src/cmd/fm/dicts/SUN4.po deleted file mode 100644 index b1df0f35b1..0000000000 --- a/usr/src/cmd/fm/dicts/SUN4.po +++ /dev/null @@ -1,345 +0,0 @@ -# -# Copyright 2007 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# DO NOT EDIT -- this file is generated by the Event Registry. -# -# -# code: SUN4-8000-0Y -# keys: fault.io.fire.asic -# -msgid "SUN4-8000-0Y.type" -msgstr "Fault" -msgid "SUN4-8000-0Y.severity" -msgstr "Critical" -msgid "SUN4-8000-0Y.description" -msgstr "A problem was detected in the PCI-Express subsystem.\n Refer to %s for more information." -msgid "SUN4-8000-0Y.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-0Y.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-0Y.action" -msgstr "Schedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support. If this message occurs on a Sun Fire T2000 also refer to the NOTE\nat the end of the Details section below.\n" -# -# code: SUN4-8000-13 -# keys: fault.io.ebus -# -msgid "SUN4-8000-13.type" -msgstr "Fault" -msgid "SUN4-8000-13.severity" -msgstr "Critical" -msgid "SUN4-8000-13.description" -msgstr "A problem was detected in the Ebus. Refer to %s for more information." -msgid "SUN4-8000-13.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-13.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-13.action" -msgstr "Use fmdump -v -u EVENT_ID and fmdump -eV -u \nEVENT_ID to collect information to help illumos personnel \nidentify the device in need of repair. Schedule a repair procedure to replace \nthe affected device.\n" -# -# code: SUN4-8000-2H -# keys: fault.io.datapath -# -msgid "SUN4-8000-2H.type" -msgstr "Fault" -msgid "SUN4-8000-2H.severity" -msgstr "Critical" -msgid "SUN4-8000-2H.description" -msgstr "This is an unexpected diagnosis. Please contact your illumos distribution team for details. Refer to %s for more information." -msgid "SUN4-8000-2H.response" -msgstr "None" -msgid "SUN4-8000-2H.impact" -msgstr "None" -msgid "SUN4-8000-2H.action" -msgstr "None" -# -# code: SUN4-8000-3D -# keys: fault.io.hbus -# -msgid "SUN4-8000-3D.type" -msgstr "Fault" -msgid "SUN4-8000-3D.severity" -msgstr "Critical" -msgid "SUN4-8000-3D.description" -msgstr "A problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4-8000-3D.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-3D.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-3D.action" -msgstr "Use fmdump -v -u EVENT_ID and fmdump -eV -u\nEVENT_ID to collect information to \nhelp illumos personnel identify the device in need of repair. Schedule \na repair procedure to replace the affected device.\n" -# -# code: SUN4-8000-4P -# keys: fault.io.fire.pciex.device -# -msgid "SUN4-8000-4P.type" -msgstr "Fault" -msgid "SUN4-8000-4P.severity" -msgstr "Critical" -msgid "SUN4-8000-4P.description" -msgstr "A problem was detected in the PCI-Express subsystem.\n Refer to %s for more information." -msgid "SUN4-8000-4P.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-4P.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-4P.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support. \nIf this message occurs on a Sun Fire T2000 also refer to the NOTE\nat the end of the Details section below." -# -# code: SUN4-8000-5A -# keys: defect.io.fire.pciex.driver -# -msgid "SUN4-8000-5A.type" -msgstr "Defect" -msgid "SUN4-8000-5A.severity" -msgstr "Critical" -msgid "SUN4-8000-5A.description" -msgstr "A problem was detected in the PCI-Express subsystem software.\n Refer to %s for more information." -msgid "SUN4-8000-5A.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-5A.impact" -msgstr "Loss of services provided by the device instances associated with\nthis problem" -msgid "SUN4-8000-5A.action" -msgstr "Ensure latest driver and patch are installed. Use fmdump -v -u to identify the module/package, or contact your illumos distribution team for support." -# -# code: SUN4-8000-6S -# keys: fault.io.datapath fault.io.fire.asic -# -msgid "SUN4-8000-6S.type" -msgstr "Fault" -msgid "SUN4-8000-6S.severity" -msgstr "Critical" -msgid "SUN4-8000-6S.description" -msgstr "This is an unexpected diagnosis. Please contact your illumos distribution team for details. Refer to %s for more information." -msgid "SUN4-8000-6S.response" -msgstr "None" -msgid "SUN4-8000-6S.impact" -msgstr "None" -msgid "SUN4-8000-6S.action" -msgstr "None" -# -# code: SUN4-8000-75 -# keys: fault.io.fire.asic fault.io.fire.pciex.device -# -msgid "SUN4-8000-75.type" -msgstr "Fault" -msgid "SUN4-8000-75.severity" -msgstr "Critical" -msgid "SUN4-8000-75.description" -msgstr "A problem was detected in the PCI-Express subsystem.\n Refer to %s for more information." -msgid "SUN4-8000-75.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-75.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-75.action" -msgstr "Schedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support. If this message occurs on a Sun Fire T2000 also refer to the NOTE\nat the end of the Details section below.\n" -# -# code: SUN4-8000-8E -# keys: defect.io.fire.pci.driver defect.io.fire.pciex.driver -# -msgid "SUN4-8000-8E.type" -msgstr "Defect" -msgid "SUN4-8000-8E.severity" -msgstr "Critical" -msgid "SUN4-8000-8E.description" -msgstr "A problem was detected in the PCI-Express subsystem software. Refer to %s for more information." -msgid "SUN4-8000-8E.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-8E.impact" -msgstr "Loss of services provided by the device instances associated with this problem" -msgid "SUN4-8000-8E.action" -msgstr "Ensure latest driver and patch are installed. Use fmdump -v -u to identify the module/package, or contact your illumos distribution team for support." -# -# code: SUN4-8000-9J -# keys: fault.io.fire.pci.device fault.io.fire.pciex.device -# -msgid "SUN4-8000-9J.type" -msgstr "Fault" -msgid "SUN4-8000-9J.severity" -msgstr "Critical" -msgid "SUN4-8000-9J.description" -msgstr "This is an unexpected diagnosis. Please contact your illumos distribution team for details. Refer to %s for more information." -msgid "SUN4-8000-9J.response" -msgstr "None" -msgid "SUN4-8000-9J.impact" -msgstr "None" -msgid "SUN4-8000-9J.action" -msgstr "None" -# -# code: SUN4-8000-A2 -# keys: fault.io.fire.pci.device -# -msgid "SUN4-8000-A2.type" -msgstr "Fault" -msgid "SUN4-8000-A2.severity" -msgstr "Critical" -msgid "SUN4-8000-A2.description" -msgstr "A problem was detected in the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4-8000-A2.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-A2.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-A2.action" -msgstr "Schedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4-8000-CX -# keys: defect.io.fire.pciex.driver fault.io.datapath fault.io.fire.asic -# -msgid "SUN4-8000-CX.type" -msgstr "Fault" -msgid "SUN4-8000-CX.severity" -msgstr "Critical" -msgid "SUN4-8000-CX.description" -msgstr "This is an unexpected diagnosis. Please contact your illumos distribution team for details. Refer to %s for more information." -msgid "SUN4-8000-CX.response" -msgstr "None" -msgid "SUN4-8000-CX.impact" -msgstr "None" -msgid "SUN4-8000-CX.action" -msgstr "None" -# -# code: SUN4-8000-D4 -# keys: fault.io.fire.asic fault.io.fire.pci.device fault.io.fire.pciex.device -# -msgid "SUN4-8000-D4.type" -msgstr "Fault" -msgid "SUN4-8000-D4.severity" -msgstr "Critical" -msgid "SUN4-8000-D4.description" -msgstr "A problem has been detected in the PCI/PCI-Express subsystem. Refer to %s for more information." -msgid "SUN4-8000-D4.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-D4.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-D4.action" -msgstr "Schedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support. If this message occurs on a Sun Fire T2000 also refer to the NOTE\nat the end of the Details section below.\n" -# -# code: SUN4-8000-ER -# keys: fault.io.fire.asic fault.io.fire.pci.device -# -msgid "SUN4-8000-ER.type" -msgstr "Fault" -msgid "SUN4-8000-ER.severity" -msgstr "Critical" -msgid "SUN4-8000-ER.description" -msgstr "A problem has been detected in the PCI/PCI-Express subsystem. Refer to %s for more information." -msgid "SUN4-8000-ER.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-ER.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-ER.action" -msgstr "Schedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support. If this message occurs on a Sun Fire T2000 also refer to the NOTE\nat the end of the Details section below.\n" -# -# code: SUN4-8000-FC -# keys: fault.io.fire.hbus -# -msgid "SUN4-8000-FC.type" -msgstr "Fault" -msgid "SUN4-8000-FC.severity" -msgstr "Major" -msgid "SUN4-8000-FC.description" -msgstr "A problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4-8000-FC.response" -msgstr "This fault does not have an automated response agent and thus requires interaction \nfrom the user and/or your illumos distribution team." -msgid "SUN4-8000-FC.impact" -msgstr "Loss of services provided by the device instances associated with this fault" -msgid "SUN4-8000-FC.action" -msgstr "Use fmdump -v -u EVENT_ID and fmdump -eV -u\nEVENT_ID to collect information to \nhelp illumos personnel identify the device in need of repair. Schedule \na repair procedure to replace the affected device.\n" -# -# code: SUN4-8000-GQ -# keys: fault.io.fire.datapath fault.io.fire.hbus -# -msgid "SUN4-8000-GQ.type" -msgstr "Fault" -msgid "SUN4-8000-GQ.severity" -msgstr "Critical" -msgid "SUN4-8000-GQ.description" -msgstr "Fault in either the PCIe asic's internal hostbus or connector between IO and CPU Board\n Refer to %s for more information." -msgid "SUN4-8000-GQ.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4-8000-GQ.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4-8000-GQ.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4-8000-HD -# keys: fault.io.fire.hb.sw-config -# -msgid "SUN4-8000-HD.type" -msgstr "Fault" -msgid "SUN4-8000-HD.severity" -msgstr "Critical" -msgid "SUN4-8000-HD.description" -msgstr "The IO hostbridge's hostbus has been found to be configured improperly\nwhich is preventing the system from functioning properly.\n Refer to %s for more information." -msgid "SUN4-8000-HD.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4-8000-HD.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4-8000-HD.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4-8000-JH -# keys: fault.io.fire.dmc.sw-algorithm -# -msgid "SUN4-8000-JH.type" -msgstr "Fault" -msgid "SUN4-8000-JH.severity" -msgstr "Critical" -msgid "SUN4-8000-JH.description" -msgstr "An uncorrectable software problem was detected in the IO hostbridge's \nData Management Unit which is preventing the system from functioning properly.\n Refer to %s for more information." -msgid "SUN4-8000-JH.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4-8000-JH.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4-8000-JH.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4-8000-K3 -# keys: fault.io.fire.dmc.sw-state -# -msgid "SUN4-8000-K3.type" -msgstr "Fault" -msgid "SUN4-8000-K3.severity" -msgstr "Critical" -msgid "SUN4-8000-K3.description" -msgstr "The IO hostbridge's Data Management Unit has been found to be in an illegal state\nwhich is preventing the system from functioning properly.\n Refer to %s for more information." -msgid "SUN4-8000-K3.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4-8000-K3.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4-8000-K3.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4-8000-LY -# keys: fault.io.fire.pec.sw-algorithm -# -msgid "SUN4-8000-LY.type" -msgstr "Fault" -msgid "SUN4-8000-LY.severity" -msgstr "Critical" -msgid "SUN4-8000-LY.description" -msgstr "An uncorrectable software problem was detected in the IO hostbridge's \nData Management Unit which is preventing the system from functioning properly.\n Refer to %s for more information." -msgid "SUN4-8000-LY.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4-8000-LY.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4-8000-LY.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" diff --git a/usr/src/cmd/fm/dicts/SUN4U.dict b/usr/src/cmd/fm/dicts/SUN4U.dict deleted file mode 100644 index 23d106ad63..0000000000 --- a/usr/src/cmd/fm/dicts/SUN4U.dict +++ /dev/null @@ -1,273 +0,0 @@ -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# DO NOT EDIT -- this file is generated by the Event Registry. -# - -FMDICT: name=SUN4U version=1 maxkey=7 dictid=0x3455 - -fault.memory.page=1 -fault.memory.dimm=2 -fault.memory.bank=3 -fault.cpu.ultraSPARC-III.dcache=4 -fault.cpu.ultraSPARC-III.icache=5 -fault.cpu.ultraSPARC-III.l2cachedata=6 -fault.cpu.ultraSPARC-III.l2cachetag=7 -fault.cpu.ultraSPARC-IIIi.dcache=8 -fault.cpu.ultraSPARC-IIIi.icache=9 -fault.cpu.ultraSPARC-IIIi.l2cachedata=10 -fault.cpu.ultraSPARC-IIIi.l2cachetag=11 -fault.cpu.ultraSPARC-IIIplus.dcache=12 -fault.cpu.ultraSPARC-IIIplus.icache=13 -fault.cpu.ultraSPARC-IIIplus.l2cachedata=14 -fault.cpu.ultraSPARC-IIIplus.l2cachetag=15 -fault.cpu.ultraSPARC-IV.dcache=16 -fault.cpu.ultraSPARC-IV.icache=17 -fault.cpu.ultraSPARC-IV.l2cachedata=18 -fault.cpu.ultraSPARC-IV.l2cachetag=19 -fault.cpu.ultraSPARC-III.fpu=20 -fault.cpu.ultraSPARC-IIIi.fpu=21 -fault.cpu.ultraSPARC-IIIplus.fpu=22 -fault.cpu.ultraSPARC-IV.fpu=23 -fault.cpu.ultraSPARC-IVplus.fpu=24 -fault.cpu.ultraSPARC-IVplus.dcache=25 -fault.cpu.ultraSPARC-IVplus.icache=26 -fault.cpu.ultraSPARC-IVplus.pcache=27 -fault.cpu.ultraSPARC-IVplus.dtlb=28 -fault.cpu.ultraSPARC-IVplus.itlb=29 -fault.cpu.ultraSPARC-IVplus.l2cachedata=30 -fault.cpu.ultraSPARC-IVplus.l2cachetag=31 -fault.cpu.ultraSPARC-IVplus.l3cachedata=32 -fault.cpu.ultraSPARC-IVplus.l3cachetag=33 -defect.ultraSPARC-II.memory.nodiag=34 -fault.memory.datapath=35 -fault.io.datapath=36 -defect.io.pci.driver fault.io.datapath=37 -fault.io.datapath fault.io.pci.bus=38 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus=39 -fault.io.datapath fault.io.pci.device=40 -defect.io.pci.driver fault.io.datapath fault.io.pci.device=41 -fault.io.datapath fault.io.pci.bus fault.io.pci.device=42 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device=43 -fault.io.hbus=44 -defect.io.pci.driver fault.io.hbus=45 -fault.io.hbus fault.io.pci.bus=46 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus=47 -fault.io.hbus fault.io.pci.device=48 -defect.io.pci.driver fault.io.hbus fault.io.pci.device=49 -fault.io.hbus fault.io.pci.bus fault.io.pci.device=50 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device=51 -fault.io.datapath fault.io.hbus=52 -defect.io.pci.driver fault.io.datapath fault.io.hbus=53 -fault.io.datapath fault.io.hbus fault.io.pci.bus=54 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus=55 -fault.io.datapath fault.io.hbus fault.io.pci.device=56 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device=57 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device=58 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device=59 -fault.io.schizo=60 -defect.io.pci.driver fault.io.schizo=61 -fault.io.pci.bus fault.io.schizo=62 -defect.io.pci.driver fault.io.pci.bus fault.io.schizo=63 -fault.io.pci.device fault.io.schizo=64 -defect.io.pci.driver fault.io.pci.device fault.io.schizo=65 -fault.io.pci.bus fault.io.pci.device fault.io.schizo=66 -defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo=67 -fault.io.datapath fault.io.schizo=68 -defect.io.pci.driver fault.io.datapath fault.io.schizo=69 -fault.io.datapath fault.io.pci.bus fault.io.schizo=70 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo=71 -fault.io.datapath fault.io.pci.device fault.io.schizo=72 -defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo=73 -fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo=74 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo=75 -fault.io.hbus fault.io.schizo=76 -defect.io.pci.driver fault.io.hbus fault.io.schizo=77 -fault.io.hbus fault.io.pci.bus fault.io.schizo=78 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo=79 -fault.io.hbus fault.io.pci.device fault.io.schizo=80 -defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo=81 -fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo=82 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo=83 -fault.io.datapath fault.io.hbus fault.io.schizo=84 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo=85 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo=86 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo=87 -fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo=88 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo=89 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo=90 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo=91 -fault.io.xmits=92 -defect.io.pci.driver fault.io.xmits=93 -fault.io.pci.bus fault.io.xmits=94 -defect.io.pci.driver fault.io.pci.bus fault.io.xmits=95 -fault.io.pci.device fault.io.xmits=96 -defect.io.pci.driver fault.io.pci.device fault.io.xmits=97 -fault.io.pci.bus fault.io.pci.device fault.io.xmits=98 -defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.xmits=99 -fault.io.datapath fault.io.xmits=100 -defect.io.pci.driver fault.io.datapath fault.io.xmits=101 -fault.io.datapath fault.io.pci.bus fault.io.xmits=102 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.xmits=103 -fault.io.datapath fault.io.pci.device fault.io.xmits=104 -defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.xmits=105 -fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits=106 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits=107 -fault.io.hbus fault.io.xmits=108 -defect.io.pci.driver fault.io.hbus fault.io.xmits=109 -fault.io.hbus fault.io.pci.bus fault.io.xmits=110 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.xmits=111 -fault.io.hbus fault.io.pci.device fault.io.xmits=112 -defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.xmits=113 -fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits=114 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits=115 -fault.io.datapath fault.io.hbus fault.io.xmits=116 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.xmits=117 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits=118 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits=119 -fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits=120 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits=121 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits=122 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits=123 -fault.io.schizo fault.io.xmits=124 -defect.io.pci.driver fault.io.schizo fault.io.xmits=125 -fault.io.pci.bus fault.io.schizo fault.io.xmits=126 -defect.io.pci.driver fault.io.pci.bus fault.io.schizo fault.io.xmits=127 -fault.io.pci.device fault.io.schizo fault.io.xmits=128 -defect.io.pci.driver fault.io.pci.device fault.io.schizo fault.io.xmits=129 -fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits=130 -defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits=131 -fault.io.datapath fault.io.schizo fault.io.xmits=132 -defect.io.pci.driver fault.io.datapath fault.io.schizo fault.io.xmits=133 -fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits=134 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits=135 -fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits=136 -defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits=137 -fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits=138 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits=139 -fault.io.hbus fault.io.schizo fault.io.xmits=140 -defect.io.pci.driver fault.io.hbus fault.io.schizo fault.io.xmits=141 -fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits=142 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits=143 -fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits=144 -defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits=145 -fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits=146 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits=147 -fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits=148 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits=149 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits=150 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits=151 -fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits=152 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits=153 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits=154 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits=155 -fault.io.psycho=156 -defect.io.pci.driver fault.io.psycho=157 -fault.io.datapath fault.io.psycho=158 -defect.io.pci.driver fault.io.datapath fault.io.psycho=159 -fault.io.hbus fault.io.psycho=160 -defect.io.pci.driver fault.io.hbus fault.io.psycho=161 -fault.io.datapath fault.io.hbus fault.io.psycho=162 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.psycho=163 -fault.io.pci.bus fault.io.psycho=164 -defect.io.pci.driver fault.io.pci.bus fault.io.psycho=165 -fault.io.datapath fault.io.pci.bus fault.io.psycho=166 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.psycho=167 -fault.io.hbus fault.io.pci.bus fault.io.psycho=168 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.psycho=169 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho=170 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho=171 -fault.io.pci.device fault.io.psycho=172 -defect.io.pci.driver fault.io.pci.device fault.io.psycho=173 -fault.io.datapath fault.io.pci.device fault.io.psycho=174 -defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.psycho=175 -fault.io.hbus fault.io.pci.device fault.io.psycho=176 -defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.psycho=177 -fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho=178 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho=179 -fault.io.pci.bus fault.io.pci.device fault.io.psycho=180 -defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.psycho=181 -fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho=182 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho=183 -fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho=184 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho=185 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho=186 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho=187 -fault.io.tomatillo=188 -defect.io.pci.driver fault.io.tomatillo=189 -fault.io.datapath fault.io.tomatillo=190 -defect.io.pci.driver fault.io.datapath fault.io.tomatillo=191 -fault.io.hbus fault.io.tomatillo=192 -defect.io.pci.driver fault.io.hbus fault.io.tomatillo=193 -fault.io.datapath fault.io.hbus fault.io.tomatillo=194 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.tomatillo=195 -fault.io.pci.bus fault.io.tomatillo=196 -defect.io.pci.driver fault.io.pci.bus fault.io.tomatillo=197 -fault.io.datapath fault.io.pci.bus fault.io.tomatillo=198 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.tomatillo=199 -fault.io.hbus fault.io.pci.bus fault.io.tomatillo=200 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.tomatillo=201 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo=202 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo=203 -fault.io.pci.device fault.io.tomatillo=204 -defect.io.pci.driver fault.io.pci.device fault.io.tomatillo=205 -fault.io.datapath fault.io.pci.device fault.io.tomatillo=206 -defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.tomatillo=207 -fault.io.hbus fault.io.pci.device fault.io.tomatillo=208 -defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.tomatillo=209 -fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo=210 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo=211 -fault.io.pci.bus fault.io.pci.device fault.io.tomatillo=212 -defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.tomatillo=213 -fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo=214 -defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo=215 -fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo=216 -defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo=217 -fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo=218 -defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo=219 -fault.cpu.ultraSPARC-IIIiplus.dcache=220 -fault.cpu.ultraSPARC-IIIiplus.icache=221 -fault.cpu.ultraSPARC-IIIiplus.l2cachedata=222 -fault.cpu.ultraSPARC-IIIiplus.l2cachetag=223 -fault.cpu.ultraSPARC-IIIiplus.fpu=224 -fault.asic.cds.dp=225 -fault.asic.dx.dp=226 -fault.asic.sdi.dp=227 -fault.asic.cp.dp=228 -fault.asic.rp.dp=229 -fault.io.oberon=230 -fault.cpu.SPARC64-VI.chip=231 -fault.cpu.SPARC64-VI.core=232 -fault.cpu.SPARC64-VI.strand=233 -fault.io.pci.device-invreq fault.io.tomatillo=234 -fault.cpu.SPARC64-VII.chip=235 -fault.cpu.SPARC64-VII.core=236 -fault.cpu.SPARC64-VII.strand=237 -fault.cpu.ultraSPARC-IVplus.l2cachedata-line=238 -fault.cpu.ultraSPARC-IVplus.l3cachedata-line=239 -fault.cpu.ultraSPARC-IVplus.l2cachetag-line=240 -fault.cpu.ultraSPARC-IVplus.l3cachetag-line=241 -fault.memory.dimm-page-retires-excessive=242 -fault.memory.dimm-ue-imminent=243 -fault.memory.dram-ue-imminent=244 diff --git a/usr/src/cmd/fm/dicts/SUN4U.po b/usr/src/cmd/fm/dicts/SUN4U.po deleted file mode 100644 index 5451b04642..0000000000 --- a/usr/src/cmd/fm/dicts/SUN4U.po +++ /dev/null @@ -1,3930 +0,0 @@ -# -# Copyright 2009 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# DO NOT EDIT -- this file is generated by the Event Registry. -# -# -# code: SUN4U-8000-1A -# keys: fault.memory.page -# -msgid "SUN4U-8000-1A.type" -msgstr "Fault" -msgid "SUN4U-8000-1A.severity" -msgstr "Minor" -msgid "SUN4U-8000-1A.description" -msgstr "The number of errors associated with this memory module continues to exceed acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-1A.response" -msgstr "An attempt will be made to remove this memory page from service." -msgid "SUN4U-8000-1A.impact" -msgstr "The performance of the system may be minimally impacted as a result of removing the memory page from operation." -msgid "SUN4U-8000-1A.action" -msgstr "No repair action is recommended at this time." -# -# code: SUN4U-8000-2S -# keys: fault.memory.dimm -# -msgid "SUN4U-8000-2S.type" -msgstr "Fault" -msgid "SUN4U-8000-2S.severity" -msgstr "Major" -msgid "SUN4U-8000-2S.description" -msgstr "The number of correctable errors associated with this memory module has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-2S.response" -msgstr "Pages of memory associated with this memory module have been removed from service, up to a limit which has now been reached." -msgid "SUN4U-8000-2S.impact" -msgstr "Total system memory capacity has been reduced." -msgid "SUN4U-8000-2S.action" -msgstr "Schedule a repair procedure to replace the affected memory module. Use 'fmadm faulty' to identify the memory module." -# -# code: SUN4U-8000-35 -# keys: fault.memory.bank -# -msgid "SUN4U-8000-35.type" -msgstr "Fault" -msgid "SUN4U-8000-35.severity" -msgstr "Critical" -msgid "SUN4U-8000-35.description" -msgstr "The number of errors associated with this memory module has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-35.response" -msgstr "Pages of memory associated with this memory module are being removed from service as errors are reported." -msgid "SUN4U-8000-35.impact" -msgstr "Total system memory capacity will be reduced as pages are retired." -msgid "SUN4U-8000-35.action" -msgstr "Schedule a repair procedure to replace the affected memory module. Use fmdump -v -u to identify the module." -# -# code: SUN4U-8000-4Y -# keys: fault.cpu.ultraSPARC-III.dcache -# -msgid "SUN4U-8000-4Y.type" -msgstr "Fault" -msgid "SUN4U-8000-4Y.severity" -msgstr "Major" -msgid "SUN4U-8000-4Y.description" -msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-4Y.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-4Y.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-4Y.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-53 -# keys: fault.cpu.ultraSPARC-III.icache -# -msgid "SUN4U-8000-53.type" -msgstr "Fault" -msgid "SUN4U-8000-53.severity" -msgstr "Major" -msgid "SUN4U-8000-53.description" -msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-53.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-53.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-53.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-6H -# keys: fault.cpu.ultraSPARC-III.l2cachedata -# -msgid "SUN4U-8000-6H.type" -msgstr "Fault" -msgid "SUN4U-8000-6H.severity" -msgstr "Major" -msgid "SUN4U-8000-6H.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-6H.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-6H.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-6H.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-7D -# keys: fault.cpu.ultraSPARC-III.l2cachetag -# -msgid "SUN4U-8000-7D.type" -msgstr "Fault" -msgid "SUN4U-8000-7D.severity" -msgstr "Major" -msgid "SUN4U-8000-7D.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-7D.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-7D.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-7D.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-84 -# keys: fault.cpu.ultraSPARC-IIIi.dcache -# -msgid "SUN4U-8000-84.type" -msgstr "Fault" -msgid "SUN4U-8000-84.severity" -msgstr "Major" -msgid "SUN4U-8000-84.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-84.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-84.impact" -msgstr "System performance system may be affected." -msgid "SUN4U-8000-84.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-9R -# keys: fault.cpu.ultraSPARC-IIIi.icache -# -msgid "SUN4U-8000-9R.type" -msgstr "Fault" -msgid "SUN4U-8000-9R.severity" -msgstr "Major" -msgid "SUN4U-8000-9R.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-9R.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-9R.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-9R.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-AC -# keys: fault.cpu.ultraSPARC-IIIi.l2cachedata -# -msgid "SUN4U-8000-AC.type" -msgstr "Fault" -msgid "SUN4U-8000-AC.severity" -msgstr "Major" -msgid "SUN4U-8000-AC.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-AC.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-AC.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-AC.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-CQ -# keys: fault.cpu.ultraSPARC-IIIi.l2cachetag -# -msgid "SUN4U-8000-CQ.type" -msgstr "Fault" -msgid "SUN4U-8000-CQ.severity" -msgstr "Major" -msgid "SUN4U-8000-CQ.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-CQ.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-CQ.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-CQ.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-DE -# keys: fault.cpu.ultraSPARC-IIIplus.dcache -# -msgid "SUN4U-8000-DE.type" -msgstr "Fault" -msgid "SUN4U-8000-DE.severity" -msgstr "Major" -msgid "SUN4U-8000-DE.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-DE.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-DE.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-DE.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-EJ -# keys: fault.cpu.ultraSPARC-IIIplus.icache -# -msgid "SUN4U-8000-EJ.type" -msgstr "Fault" -msgid "SUN4U-8000-EJ.severity" -msgstr "Major" -msgid "SUN4U-8000-EJ.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-EJ.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-EJ.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-EJ.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-F2 -# keys: fault.cpu.ultraSPARC-IIIplus.l2cachedata -# -msgid "SUN4U-8000-F2.type" -msgstr "Fault" -msgid "SUN4U-8000-F2.severity" -msgstr "Major" -msgid "SUN4U-8000-F2.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-F2.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-F2.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-F2.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-GX -# keys: fault.cpu.ultraSPARC-IIIplus.l2cachetag -# -msgid "SUN4U-8000-GX.type" -msgstr "Fault" -msgid "SUN4U-8000-GX.severity" -msgstr "Major" -msgid "SUN4U-8000-GX.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-GX.response" -msgstr "An attempt will be made to remove the affected CPU from service." -msgid "SUN4U-8000-GX.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-GX.action" -msgstr "Schedule a repair procedure to replace the affected CPU. Use fmdump -v -u to identify the CPU." -# -# code: SUN4U-8000-H5 -# keys: fault.cpu.ultraSPARC-IV.dcache -# -msgid "SUN4U-8000-H5.type" -msgstr "Fault" -msgid "SUN4U-8000-H5.severity" -msgstr "Major" -msgid "SUN4U-8000-H5.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-H5.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-H5.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-H5.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-JS -# keys: fault.cpu.ultraSPARC-IV.icache -# -msgid "SUN4U-8000-JS.type" -msgstr "Fault" -msgid "SUN4U-8000-JS.severity" -msgstr "Major" -msgid "SUN4U-8000-JS.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-JS.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-JS.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-JS.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-KA -# keys: fault.cpu.ultraSPARC-IV.l2cachedata -# -msgid "SUN4U-8000-KA.type" -msgstr "Fault" -msgid "SUN4U-8000-KA.severity" -msgstr "Major" -msgid "SUN4U-8000-KA.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-KA.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-KA.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-KA.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-LP -# keys: fault.cpu.ultraSPARC-IV.l2cachetag -# -msgid "SUN4U-8000-LP.type" -msgstr "Fault" -msgid "SUN4U-8000-LP.severity" -msgstr "Major" -msgid "SUN4U-8000-LP.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-LP.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-LP.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-LP.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-MD -# keys: fault.cpu.ultraSPARC-III.fpu -# -msgid "SUN4U-8000-MD.type" -msgstr "Fault" -msgid "SUN4U-8000-MD.severity" -msgstr "Major" -msgid "SUN4U-8000-MD.description" -msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." -msgid "SUN4U-8000-MD.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-MD.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-MD.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-NH -# keys: fault.cpu.ultraSPARC-IIIi.fpu -# -msgid "SUN4U-8000-NH.type" -msgstr "Fault" -msgid "SUN4U-8000-NH.severity" -msgstr "Major" -msgid "SUN4U-8000-NH.description" -msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." -msgid "SUN4U-8000-NH.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-NH.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-NH.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-P3 -# keys: fault.cpu.ultraSPARC-IIIplus.fpu -# -msgid "SUN4U-8000-P3.type" -msgstr "Fault" -msgid "SUN4U-8000-P3.severity" -msgstr "Major" -msgid "SUN4U-8000-P3.description" -msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." -msgid "SUN4U-8000-P3.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-P3.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-P3.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-QY -# keys: fault.cpu.ultraSPARC-IV.fpu -# -msgid "SUN4U-8000-QY.type" -msgstr "Fault" -msgid "SUN4U-8000-QY.severity" -msgstr "Major" -msgid "SUN4U-8000-QY.description" -msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." -msgid "SUN4U-8000-QY.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-QY.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-QY.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-RQ -# keys: fault.cpu.ultraSPARC-IVplus.fpu -# -msgid "SUN4U-8000-RQ.type" -msgstr "Fault" -msgid "SUN4U-8000-RQ.severity" -msgstr "Major" -msgid "SUN4U-8000-RQ.description" -msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." -msgid "SUN4U-8000-RQ.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-RQ.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-RQ.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-SC -# keys: fault.cpu.ultraSPARC-IVplus.dcache -# -msgid "SUN4U-8000-SC.type" -msgstr "Fault" -msgid "SUN4U-8000-SC.severity" -msgstr "Major" -msgid "SUN4U-8000-SC.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-SC.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-SC.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-SC.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-TR -# keys: fault.cpu.ultraSPARC-IVplus.icache -# -msgid "SUN4U-8000-TR.type" -msgstr "Fault" -msgid "SUN4U-8000-TR.severity" -msgstr "Major" -msgid "SUN4U-8000-TR.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-TR.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-TR.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-TR.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-U4 -# keys: fault.cpu.ultraSPARC-IVplus.pcache -# -msgid "SUN4U-8000-U4.type" -msgstr "Fault" -msgid "SUN4U-8000-U4.severity" -msgstr "Major" -msgid "SUN4U-8000-U4.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-U4.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-U4.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-U4.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-VX -# keys: fault.cpu.ultraSPARC-IVplus.dtlb -# -msgid "SUN4U-8000-VX.type" -msgstr "Fault" -msgid "SUN4U-8000-VX.severity" -msgstr "Major" -msgid "SUN4U-8000-VX.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-VX.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-VX.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-VX.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-W2 -# keys: fault.cpu.ultraSPARC-IVplus.itlb -# -msgid "SUN4U-8000-W2.type" -msgstr "Fault" -msgid "SUN4U-8000-W2.severity" -msgstr "Major" -msgid "SUN4U-8000-W2.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-W2.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-W2.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-W2.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-XJ -# keys: fault.cpu.ultraSPARC-IVplus.l2cachedata -# -msgid "SUN4U-8000-XJ.type" -msgstr "Fault" -msgid "SUN4U-8000-XJ.severity" -msgstr "Major" -msgid "SUN4U-8000-XJ.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-XJ.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-XJ.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-XJ.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8000-YE -# keys: fault.cpu.ultraSPARC-IVplus.l2cachetag -# -msgid "SUN4U-8000-YE.type" -msgstr "Fault" -msgid "SUN4U-8000-YE.severity" -msgstr "Major" -msgid "SUN4U-8000-YE.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8000-YE.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8000-YE.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8000-YE.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8001-0J -# keys: fault.cpu.ultraSPARC-IVplus.l3cachedata -# -msgid "SUN4U-8001-0J.type" -msgstr "Fault" -msgid "SUN4U-8001-0J.severity" -msgstr "Major" -msgid "SUN4U-8001-0J.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8001-0J.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8001-0J.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8001-0J.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8001-1E -# keys: fault.cpu.ultraSPARC-IVplus.l3cachetag -# -msgid "SUN4U-8001-1E.type" -msgstr "Fault" -msgid "SUN4U-8001-1E.severity" -msgstr "Major" -msgid "SUN4U-8001-1E.description" -msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8001-1E.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8001-1E.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8001-1E.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8001-2X -# keys: defect.ultraSPARC-II.memory.nodiag -# -msgid "SUN4U-8001-2X.type" -msgstr "Defect" -msgid "SUN4U-8001-2X.severity" -msgstr "Minor" -msgid "SUN4U-8001-2X.description" -msgstr "The illumos Fault Manager received an event from the IO subsystem for which automated diagnosis software is currently unavailable. Refer to %s for more information." -msgid "SUN4U-8001-2X.response" -msgstr "The error information has been saved for examination by your illumos distribution team." -msgid "SUN4U-8001-2X.impact" -msgstr "The error log will need to be manually examined using fmdump(8) in order to determine if any human response is required." -msgid "SUN4U-8001-2X.action" -msgstr "Use fmdump -ev -u to view and record the undiagnosed errors." -# -# code: SUN4U-8001-32 -# keys: fault.memory.datapath -# -msgid "SUN4U-8001-32.type" -msgstr "Fault" -msgid "SUN4U-8001-32.severity" -msgstr "Major" -msgid "SUN4U-8001-32.description" -msgstr "Errors have been detected on multiple memory modules, suggesting that a problem exists somewhere else in the system. Refer to %s for more information." -msgid "SUN4U-8001-32.response" -msgstr "Error reports from the affected components will be logged for examination by your illumos distribution team." -msgid "SUN4U-8001-32.impact" -msgstr "System performance and stability may be affected." -msgid "SUN4U-8001-32.action" -msgstr "Contact your service provider for further diagnosis." -# -# code: SUN4U-8001-4R -# keys: fault.io.datapath -# -msgid "SUN4U-8001-4R.type" -msgstr "Fault" -msgid "SUN4U-8001-4R.severity" -msgstr "Critical" -msgid "SUN4U-8001-4R.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-4R.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-4R.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-4R.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-54 -# keys: defect.io.pci.driver fault.io.datapath -# -msgid "SUN4U-8001-54.type" -msgstr "Fault" -msgid "SUN4U-8001-54.severity" -msgstr "Critical" -msgid "SUN4U-8001-54.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-54.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-54.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-54.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-6Q -# keys: fault.io.datapath fault.io.pci.bus -# -msgid "SUN4U-8001-6Q.type" -msgstr "Fault" -msgid "SUN4U-8001-6Q.severity" -msgstr "Critical" -msgid "SUN4U-8001-6Q.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-6Q.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-6Q.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-6Q.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-7C -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus -# -msgid "SUN4U-8001-7C.type" -msgstr "Fault" -msgid "SUN4U-8001-7C.severity" -msgstr "Critical" -msgid "SUN4U-8001-7C.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-7C.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-7C.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-7C.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-83 -# keys: fault.io.datapath fault.io.pci.device -# -msgid "SUN4U-8001-83.type" -msgstr "Fault" -msgid "SUN4U-8001-83.severity" -msgstr "Critical" -msgid "SUN4U-8001-83.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-83.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-83.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-83.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-9Y -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device -# -msgid "SUN4U-8001-9Y.type" -msgstr "Fault" -msgid "SUN4U-8001-9Y.severity" -msgstr "Critical" -msgid "SUN4U-8001-9Y.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-9Y.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-9Y.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-9Y.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-AD -# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device -# -msgid "SUN4U-8001-AD.type" -msgstr "Fault" -msgid "SUN4U-8001-AD.severity" -msgstr "Critical" -msgid "SUN4U-8001-AD.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-AD.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-AD.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-AD.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-CH -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device -# -msgid "SUN4U-8001-CH.type" -msgstr "Fault" -msgid "SUN4U-8001-CH.severity" -msgstr "Critical" -msgid "SUN4U-8001-CH.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-CH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-CH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-CH.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-DA -# keys: fault.io.hbus -# -msgid "SUN4U-8001-DA.type" -msgstr "Fault" -msgid "SUN4U-8001-DA.severity" -msgstr "Critical" -msgid "SUN4U-8001-DA.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-DA.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-DA.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-DA.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-EP -# keys: defect.io.pci.driver fault.io.hbus -# -msgid "SUN4U-8001-EP.type" -msgstr "Fault" -msgid "SUN4U-8001-EP.severity" -msgstr "Critical" -msgid "SUN4U-8001-EP.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-EP.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-EP.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-EP.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-F5 -# keys: fault.io.hbus fault.io.pci.bus -# -msgid "SUN4U-8001-F5.type" -msgstr "Fault" -msgid "SUN4U-8001-F5.severity" -msgstr "Critical" -msgid "SUN4U-8001-F5.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-F5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-F5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-F5.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-GS -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus -# -msgid "SUN4U-8001-GS.type" -msgstr "Fault" -msgid "SUN4U-8001-GS.severity" -msgstr "Critical" -msgid "SUN4U-8001-GS.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-GS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-GS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-GS.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-H2 -# keys: fault.io.hbus fault.io.pci.device -# -msgid "SUN4U-8001-H2.type" -msgstr "Fault" -msgid "SUN4U-8001-H2.severity" -msgstr "Critical" -msgid "SUN4U-8001-H2.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-H2.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-H2.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-H2.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-JX -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device -# -msgid "SUN4U-8001-JX.type" -msgstr "Fault" -msgid "SUN4U-8001-JX.severity" -msgstr "Critical" -msgid "SUN4U-8001-JX.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-JX.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-JX.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-JX.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-KE -# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device -# -msgid "SUN4U-8001-KE.type" -msgstr "Fault" -msgid "SUN4U-8001-KE.severity" -msgstr "Critical" -msgid "SUN4U-8001-KE.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-KE.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-KE.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-KE.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-LJ -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device -# -msgid "SUN4U-8001-LJ.type" -msgstr "Fault" -msgid "SUN4U-8001-LJ.severity" -msgstr "Critical" -msgid "SUN4U-8001-LJ.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-LJ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-LJ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-LJ.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-MC -# keys: fault.io.datapath fault.io.hbus -# -msgid "SUN4U-8001-MC.type" -msgstr "Fault" -msgid "SUN4U-8001-MC.severity" -msgstr "Critical" -msgid "SUN4U-8001-MC.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-MC.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-MC.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-MC.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-NQ -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus -# -msgid "SUN4U-8001-NQ.type" -msgstr "Fault" -msgid "SUN4U-8001-NQ.severity" -msgstr "Critical" -msgid "SUN4U-8001-NQ.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-NQ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-NQ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-NQ.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-P4 -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus -# -msgid "SUN4U-8001-P4.type" -msgstr "Fault" -msgid "SUN4U-8001-P4.severity" -msgstr "Critical" -msgid "SUN4U-8001-P4.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-P4.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-P4.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-P4.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-QR -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus -# -msgid "SUN4U-8001-QR.type" -msgstr "Fault" -msgid "SUN4U-8001-QR.severity" -msgstr "Critical" -msgid "SUN4U-8001-QR.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-QR.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-QR.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-QR.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-RH -# keys: fault.io.datapath fault.io.hbus fault.io.pci.device -# -msgid "SUN4U-8001-RH.type" -msgstr "Fault" -msgid "SUN4U-8001-RH.severity" -msgstr "Critical" -msgid "SUN4U-8001-RH.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-RH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-RH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-RH.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-SD -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device -# -msgid "SUN4U-8001-SD.type" -msgstr "Fault" -msgid "SUN4U-8001-SD.severity" -msgstr "Critical" -msgid "SUN4U-8001-SD.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-SD.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-SD.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-SD.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-TY -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device -# -msgid "SUN4U-8001-TY.type" -msgstr "Fault" -msgid "SUN4U-8001-TY.severity" -msgstr "Critical" -msgid "SUN4U-8001-TY.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-TY.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-TY.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-TY.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-U3 -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device -# -msgid "SUN4U-8001-U3.type" -msgstr "Fault" -msgid "SUN4U-8001-U3.severity" -msgstr "Critical" -msgid "SUN4U-8001-U3.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-U3.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-U3.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-U3.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-VS -# keys: fault.io.schizo -# -msgid "SUN4U-8001-VS.type" -msgstr "Fault" -msgid "SUN4U-8001-VS.severity" -msgstr "Critical" -msgid "SUN4U-8001-VS.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-VS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-VS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-VS.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-W5 -# keys: defect.io.pci.driver fault.io.schizo -# -msgid "SUN4U-8001-W5.type" -msgstr "Fault" -msgid "SUN4U-8001-W5.severity" -msgstr "Critical" -msgid "SUN4U-8001-W5.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-W5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-W5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-W5.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8001-XP -# keys: fault.io.pci.bus fault.io.schizo -# -msgid "SUN4U-8001-XP.type" -msgstr "Fault" -msgid "SUN4U-8001-XP.severity" -msgstr "Critical" -msgid "SUN4U-8001-XP.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8001-XP.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-XP.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-XP.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8001-YA -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.schizo -# -msgid "SUN4U-8001-YA.type" -msgstr "Fault" -msgid "SUN4U-8001-YA.severity" -msgstr "Critical" -msgid "SUN4U-8001-YA.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8001-YA.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8001-YA.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8001-YA.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-0R -# keys: fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-0R.type" -msgstr "Fault" -msgid "SUN4U-8002-0R.severity" -msgstr "Critical" -msgid "SUN4U-8002-0R.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-0R.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-0R.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-0R.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-14 -# keys: defect.io.pci.driver fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-14.type" -msgstr "Fault" -msgid "SUN4U-8002-14.severity" -msgstr "Critical" -msgid "SUN4U-8002-14.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-14.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-14.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-14.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-2Q -# keys: fault.io.pci.bus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-2Q.type" -msgstr "Fault" -msgid "SUN4U-8002-2Q.severity" -msgstr "Critical" -msgid "SUN4U-8002-2Q.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-2Q.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-2Q.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-2Q.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-3C -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-3C.type" -msgstr "Fault" -msgid "SUN4U-8002-3C.severity" -msgstr "Critical" -msgid "SUN4U-8002-3C.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-3C.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-3C.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-3C.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-4J -# keys: fault.io.datapath fault.io.schizo -# -msgid "SUN4U-8002-4J.type" -msgstr "Fault" -msgid "SUN4U-8002-4J.severity" -msgstr "Critical" -msgid "SUN4U-8002-4J.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-4J.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-4J.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-4J.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-5E -# keys: defect.io.pci.driver fault.io.datapath fault.io.schizo -# -msgid "SUN4U-8002-5E.type" -msgstr "Fault" -msgid "SUN4U-8002-5E.severity" -msgstr "Critical" -msgid "SUN4U-8002-5E.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-5E.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-5E.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-5E.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-6X -# keys: fault.io.datapath fault.io.pci.bus fault.io.schizo -# -msgid "SUN4U-8002-6X.type" -msgstr "Fault" -msgid "SUN4U-8002-6X.severity" -msgstr "Critical" -msgid "SUN4U-8002-6X.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-6X.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-6X.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-6X.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-72 -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo -# -msgid "SUN4U-8002-72.type" -msgstr "Fault" -msgid "SUN4U-8002-72.severity" -msgstr "Critical" -msgid "SUN4U-8002-72.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-72.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-72.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-72.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-8A -# keys: fault.io.datapath fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-8A.type" -msgstr "Fault" -msgid "SUN4U-8002-8A.severity" -msgstr "Critical" -msgid "SUN4U-8002-8A.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-8A.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-8A.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-8A.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-9P -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-9P.type" -msgstr "Fault" -msgid "SUN4U-8002-9P.severity" -msgstr "Critical" -msgid "SUN4U-8002-9P.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-9P.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-9P.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-9P.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-A5 -# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-A5.type" -msgstr "Fault" -msgid "SUN4U-8002-A5.severity" -msgstr "Critical" -msgid "SUN4U-8002-A5.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-A5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-A5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-A5.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-CS -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-CS.type" -msgstr "Fault" -msgid "SUN4U-8002-CS.severity" -msgstr "Critical" -msgid "SUN4U-8002-CS.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-CS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-CS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-CS.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-D3 -# keys: fault.io.hbus fault.io.schizo -# -msgid "SUN4U-8002-D3.type" -msgstr "Fault" -msgid "SUN4U-8002-D3.severity" -msgstr "Critical" -msgid "SUN4U-8002-D3.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-D3.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-D3.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-D3.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-EY -# keys: defect.io.pci.driver fault.io.hbus fault.io.schizo -# -msgid "SUN4U-8002-EY.type" -msgstr "Fault" -msgid "SUN4U-8002-EY.severity" -msgstr "Critical" -msgid "SUN4U-8002-EY.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-EY.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-EY.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-EY.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-FD -# keys: fault.io.hbus fault.io.pci.bus fault.io.schizo -# -msgid "SUN4U-8002-FD.type" -msgstr "Fault" -msgid "SUN4U-8002-FD.severity" -msgstr "Critical" -msgid "SUN4U-8002-FD.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-FD.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-FD.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-FD.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-GH -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo -# -msgid "SUN4U-8002-GH.type" -msgstr "Fault" -msgid "SUN4U-8002-GH.severity" -msgstr "Critical" -msgid "SUN4U-8002-GH.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-GH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-GH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-GH.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-HC -# keys: fault.io.hbus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-HC.type" -msgstr "Fault" -msgid "SUN4U-8002-HC.severity" -msgstr "Critical" -msgid "SUN4U-8002-HC.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-HC.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-HC.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-HC.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-JQ -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-JQ.type" -msgstr "Fault" -msgid "SUN4U-8002-JQ.severity" -msgstr "Critical" -msgid "SUN4U-8002-JQ.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-JQ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-JQ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-JQ.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-K4 -# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-K4.type" -msgstr "Fault" -msgid "SUN4U-8002-K4.severity" -msgstr "Critical" -msgid "SUN4U-8002-K4.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-K4.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-K4.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-K4.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-LR -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-LR.type" -msgstr "Fault" -msgid "SUN4U-8002-LR.severity" -msgstr "Critical" -msgid "SUN4U-8002-LR.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-LR.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-LR.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-LR.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-M2 -# keys: fault.io.datapath fault.io.hbus fault.io.schizo -# -msgid "SUN4U-8002-M2.type" -msgstr "Fault" -msgid "SUN4U-8002-M2.severity" -msgstr "Critical" -msgid "SUN4U-8002-M2.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-M2.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-M2.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-M2.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-NX -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo -# -msgid "SUN4U-8002-NX.type" -msgstr "Fault" -msgid "SUN4U-8002-NX.severity" -msgstr "Critical" -msgid "SUN4U-8002-NX.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-NX.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-NX.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-NX.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-PE -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo -# -msgid "SUN4U-8002-PE.type" -msgstr "Fault" -msgid "SUN4U-8002-PE.severity" -msgstr "Critical" -msgid "SUN4U-8002-PE.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-PE.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-PE.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-PE.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-QJ -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo -# -msgid "SUN4U-8002-QJ.type" -msgstr "Fault" -msgid "SUN4U-8002-QJ.severity" -msgstr "Critical" -msgid "SUN4U-8002-QJ.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-QJ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-QJ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-QJ.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-RS -# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-RS.type" -msgstr "Fault" -msgid "SUN4U-8002-RS.severity" -msgstr "Critical" -msgid "SUN4U-8002-RS.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-RS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-RS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-RS.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-S5 -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-S5.type" -msgstr "Fault" -msgid "SUN4U-8002-S5.severity" -msgstr "Critical" -msgid "SUN4U-8002-S5.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-S5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-S5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-S5.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-TP -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-TP.type" -msgstr "Fault" -msgid "SUN4U-8002-TP.severity" -msgstr "Critical" -msgid "SUN4U-8002-TP.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-TP.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-TP.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-TP.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-UA -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo -# -msgid "SUN4U-8002-UA.type" -msgstr "Fault" -msgid "SUN4U-8002-UA.severity" -msgstr "Critical" -msgid "SUN4U-8002-UA.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-UA.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-UA.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-UA.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-VH -# keys: fault.io.xmits -# -msgid "SUN4U-8002-VH.type" -msgstr "Fault" -msgid "SUN4U-8002-VH.severity" -msgstr "Critical" -msgid "SUN4U-8002-VH.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-VH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-VH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-VH.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-WD -# keys: defect.io.pci.driver fault.io.xmits -# -msgid "SUN4U-8002-WD.type" -msgstr "Fault" -msgid "SUN4U-8002-WD.severity" -msgstr "Critical" -msgid "SUN4U-8002-WD.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-WD.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-WD.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-WD.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8002-XY -# keys: fault.io.pci.bus fault.io.xmits -# -msgid "SUN4U-8002-XY.type" -msgstr "Fault" -msgid "SUN4U-8002-XY.severity" -msgstr "Critical" -msgid "SUN4U-8002-XY.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8002-XY.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-XY.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-XY.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8002-Y3 -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.xmits -# -msgid "SUN4U-8002-Y3.type" -msgstr "Fault" -msgid "SUN4U-8002-Y3.severity" -msgstr "Critical" -msgid "SUN4U-8002-Y3.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8002-Y3.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8002-Y3.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8002-Y3.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-0Y -# keys: fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-0Y.type" -msgstr "Fault" -msgid "SUN4U-8003-0Y.severity" -msgstr "Critical" -msgid "SUN4U-8003-0Y.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-0Y.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-0Y.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-0Y.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-13 -# keys: defect.io.pci.driver fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-13.type" -msgstr "Fault" -msgid "SUN4U-8003-13.severity" -msgstr "Critical" -msgid "SUN4U-8003-13.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-13.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-13.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-13.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-2H -# keys: fault.io.pci.bus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-2H.type" -msgstr "Fault" -msgid "SUN4U-8003-2H.severity" -msgstr "Critical" -msgid "SUN4U-8003-2H.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-2H.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-2H.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-2H.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-3D -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-3D.type" -msgstr "Fault" -msgid "SUN4U-8003-3D.severity" -msgstr "Critical" -msgid "SUN4U-8003-3D.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-3D.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-3D.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-3D.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-4P -# keys: fault.io.datapath fault.io.xmits -# -msgid "SUN4U-8003-4P.type" -msgstr "Fault" -msgid "SUN4U-8003-4P.severity" -msgstr "Critical" -msgid "SUN4U-8003-4P.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-4P.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-4P.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-4P.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-5A -# keys: defect.io.pci.driver fault.io.datapath fault.io.xmits -# -msgid "SUN4U-8003-5A.type" -msgstr "Fault" -msgid "SUN4U-8003-5A.severity" -msgstr "Critical" -msgid "SUN4U-8003-5A.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-5A.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-5A.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-5A.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-6S -# keys: fault.io.datapath fault.io.pci.bus fault.io.xmits -# -msgid "SUN4U-8003-6S.type" -msgstr "Fault" -msgid "SUN4U-8003-6S.severity" -msgstr "Critical" -msgid "SUN4U-8003-6S.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-6S.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-6S.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-6S.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-75 -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.xmits -# -msgid "SUN4U-8003-75.type" -msgstr "Fault" -msgid "SUN4U-8003-75.severity" -msgstr "Critical" -msgid "SUN4U-8003-75.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-75.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-75.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-75.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-8E -# keys: fault.io.datapath fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-8E.type" -msgstr "Fault" -msgid "SUN4U-8003-8E.severity" -msgstr "Critical" -msgid "SUN4U-8003-8E.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-8E.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-8E.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-8E.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-9J -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-9J.type" -msgstr "Fault" -msgid "SUN4U-8003-9J.severity" -msgstr "Critical" -msgid "SUN4U-8003-9J.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-9J.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-9J.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-9J.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-A2 -# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-A2.type" -msgstr "Fault" -msgid "SUN4U-8003-A2.severity" -msgstr "Critical" -msgid "SUN4U-8003-A2.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-A2.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-A2.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-A2.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-CX -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-CX.type" -msgstr "Fault" -msgid "SUN4U-8003-CX.severity" -msgstr "Critical" -msgid "SUN4U-8003-CX.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-CX.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-CX.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-CX.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-D4 -# keys: fault.io.hbus fault.io.xmits -# -msgid "SUN4U-8003-D4.type" -msgstr "Fault" -msgid "SUN4U-8003-D4.severity" -msgstr "Critical" -msgid "SUN4U-8003-D4.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-D4.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-D4.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-D4.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-ER -# keys: defect.io.pci.driver fault.io.hbus fault.io.xmits -# -msgid "SUN4U-8003-ER.type" -msgstr "Fault" -msgid "SUN4U-8003-ER.severity" -msgstr "Critical" -msgid "SUN4U-8003-ER.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-ER.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-ER.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-ER.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-FC -# keys: fault.io.hbus fault.io.pci.bus fault.io.xmits -# -msgid "SUN4U-8003-FC.type" -msgstr "Fault" -msgid "SUN4U-8003-FC.severity" -msgstr "Critical" -msgid "SUN4U-8003-FC.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-FC.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-FC.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-FC.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-GQ -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.xmits -# -msgid "SUN4U-8003-GQ.type" -msgstr "Fault" -msgid "SUN4U-8003-GQ.severity" -msgstr "Critical" -msgid "SUN4U-8003-GQ.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-GQ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-GQ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-GQ.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-HD -# keys: fault.io.hbus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-HD.type" -msgstr "Fault" -msgid "SUN4U-8003-HD.severity" -msgstr "Critical" -msgid "SUN4U-8003-HD.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-HD.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-HD.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-HD.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-JH -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-JH.type" -msgstr "Fault" -msgid "SUN4U-8003-JH.severity" -msgstr "Critical" -msgid "SUN4U-8003-JH.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-JH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-JH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-JH.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-K3 -# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-K3.type" -msgstr "Fault" -msgid "SUN4U-8003-K3.severity" -msgstr "Critical" -msgid "SUN4U-8003-K3.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-K3.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-K3.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-K3.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-LY -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-LY.type" -msgstr "Fault" -msgid "SUN4U-8003-LY.severity" -msgstr "Critical" -msgid "SUN4U-8003-LY.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-LY.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-LY.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-LY.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-M5 -# keys: fault.io.datapath fault.io.hbus fault.io.xmits -# -msgid "SUN4U-8003-M5.type" -msgstr "Fault" -msgid "SUN4U-8003-M5.severity" -msgstr "Critical" -msgid "SUN4U-8003-M5.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-M5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-M5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-M5.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-NS -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.xmits -# -msgid "SUN4U-8003-NS.type" -msgstr "Fault" -msgid "SUN4U-8003-NS.severity" -msgstr "Critical" -msgid "SUN4U-8003-NS.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-NS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-NS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-NS.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-PA -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits -# -msgid "SUN4U-8003-PA.type" -msgstr "Fault" -msgid "SUN4U-8003-PA.severity" -msgstr "Critical" -msgid "SUN4U-8003-PA.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-PA.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-PA.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-PA.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-QP -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits -# -msgid "SUN4U-8003-QP.type" -msgstr "Fault" -msgid "SUN4U-8003-QP.severity" -msgstr "Critical" -msgid "SUN4U-8003-QP.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-QP.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-QP.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-QP.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-RX -# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-RX.type" -msgstr "Fault" -msgid "SUN4U-8003-RX.severity" -msgstr "Critical" -msgid "SUN4U-8003-RX.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-RX.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-RX.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-RX.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-S2 -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-S2.type" -msgstr "Fault" -msgid "SUN4U-8003-S2.severity" -msgstr "Critical" -msgid "SUN4U-8003-S2.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-S2.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-S2.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-S2.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-TJ -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-TJ.type" -msgstr "Fault" -msgid "SUN4U-8003-TJ.severity" -msgstr "Critical" -msgid "SUN4U-8003-TJ.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-TJ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-TJ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-TJ.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-UE -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits -# -msgid "SUN4U-8003-UE.type" -msgstr "Fault" -msgid "SUN4U-8003-UE.severity" -msgstr "Critical" -msgid "SUN4U-8003-UE.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-UE.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-UE.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-UE.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-VQ -# keys: fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8003-VQ.type" -msgstr "Fault" -msgid "SUN4U-8003-VQ.severity" -msgstr "Critical" -msgid "SUN4U-8003-VQ.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-VQ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-VQ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-VQ.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-WC -# keys: defect.io.pci.driver fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8003-WC.type" -msgstr "Fault" -msgid "SUN4U-8003-WC.severity" -msgstr "Critical" -msgid "SUN4U-8003-WC.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-WC.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-WC.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-WC.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8003-XR -# keys: fault.io.pci.bus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8003-XR.type" -msgstr "Fault" -msgid "SUN4U-8003-XR.severity" -msgstr "Critical" -msgid "SUN4U-8003-XR.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8003-XR.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-XR.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-XR.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8003-Y4 -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8003-Y4.type" -msgstr "Fault" -msgid "SUN4U-8003-Y4.severity" -msgstr "Critical" -msgid "SUN4U-8003-Y4.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8003-Y4.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8003-Y4.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8003-Y4.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-0A -# keys: fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-0A.type" -msgstr "Fault" -msgid "SUN4U-8004-0A.severity" -msgstr "Critical" -msgid "SUN4U-8004-0A.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-0A.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-0A.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-0A.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-1P -# keys: defect.io.pci.driver fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-1P.type" -msgstr "Fault" -msgid "SUN4U-8004-1P.severity" -msgstr "Critical" -msgid "SUN4U-8004-1P.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-1P.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-1P.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-1P.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-25 -# keys: fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-25.type" -msgstr "Fault" -msgid "SUN4U-8004-25.severity" -msgstr "Critical" -msgid "SUN4U-8004-25.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-25.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-25.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-25.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-3S -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-3S.type" -msgstr "Fault" -msgid "SUN4U-8004-3S.severity" -msgstr "Critical" -msgid "SUN4U-8004-3S.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-3S.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-3S.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-3S.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-43 -# keys: fault.io.datapath fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-43.type" -msgstr "Fault" -msgid "SUN4U-8004-43.severity" -msgstr "Critical" -msgid "SUN4U-8004-43.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-43.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-43.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-43.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-5Y -# keys: defect.io.pci.driver fault.io.datapath fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-5Y.type" -msgstr "Fault" -msgid "SUN4U-8004-5Y.severity" -msgstr "Critical" -msgid "SUN4U-8004-5Y.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-5Y.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-5Y.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-5Y.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-6D -# keys: fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-6D.type" -msgstr "Fault" -msgid "SUN4U-8004-6D.severity" -msgstr "Critical" -msgid "SUN4U-8004-6D.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-6D.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-6D.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-6D.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-7H -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-7H.type" -msgstr "Fault" -msgid "SUN4U-8004-7H.severity" -msgstr "Critical" -msgid "SUN4U-8004-7H.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-7H.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-7H.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-7H.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-8R -# keys: fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-8R.type" -msgstr "Fault" -msgid "SUN4U-8004-8R.severity" -msgstr "Critical" -msgid "SUN4U-8004-8R.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-8R.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-8R.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-8R.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-94 -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-94.type" -msgstr "Fault" -msgid "SUN4U-8004-94.severity" -msgstr "Critical" -msgid "SUN4U-8004-94.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-94.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-94.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-94.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-AQ -# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-AQ.type" -msgstr "Fault" -msgid "SUN4U-8004-AQ.severity" -msgstr "Critical" -msgid "SUN4U-8004-AQ.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-AQ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-AQ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-AQ.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-CC -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-CC.type" -msgstr "Fault" -msgid "SUN4U-8004-CC.severity" -msgstr "Critical" -msgid "SUN4U-8004-CC.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-CC.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-CC.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-CC.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-DJ -# keys: fault.io.hbus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-DJ.type" -msgstr "Fault" -msgid "SUN4U-8004-DJ.severity" -msgstr "Critical" -msgid "SUN4U-8004-DJ.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-DJ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-DJ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-DJ.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-EE -# keys: defect.io.pci.driver fault.io.hbus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-EE.type" -msgstr "Fault" -msgid "SUN4U-8004-EE.severity" -msgstr "Critical" -msgid "SUN4U-8004-EE.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-EE.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-EE.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-EE.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-FX -# keys: fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-FX.type" -msgstr "Fault" -msgid "SUN4U-8004-FX.severity" -msgstr "Critical" -msgid "SUN4U-8004-FX.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-FX.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-FX.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-FX.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-G2 -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-G2.type" -msgstr "Fault" -msgid "SUN4U-8004-G2.severity" -msgstr "Critical" -msgid "SUN4U-8004-G2.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-G2.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-G2.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-G2.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-HS -# keys: fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-HS.type" -msgstr "Fault" -msgid "SUN4U-8004-HS.severity" -msgstr "Critical" -msgid "SUN4U-8004-HS.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-HS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-HS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-HS.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-J5 -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-J5.type" -msgstr "Fault" -msgid "SUN4U-8004-J5.severity" -msgstr "Critical" -msgid "SUN4U-8004-J5.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-J5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-J5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-J5.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-KP -# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-KP.type" -msgstr "Fault" -msgid "SUN4U-8004-KP.severity" -msgstr "Critical" -msgid "SUN4U-8004-KP.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-KP.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-KP.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-KP.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-LA -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-LA.type" -msgstr "Fault" -msgid "SUN4U-8004-LA.severity" -msgstr "Critical" -msgid "SUN4U-8004-LA.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-LA.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-LA.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-LA.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-MH -# keys: fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-MH.type" -msgstr "Fault" -msgid "SUN4U-8004-MH.severity" -msgstr "Critical" -msgid "SUN4U-8004-MH.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-MH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-MH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-MH.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-ND -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-ND.type" -msgstr "Fault" -msgid "SUN4U-8004-ND.severity" -msgstr "Critical" -msgid "SUN4U-8004-ND.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-ND.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-ND.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-ND.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-PY -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-PY.type" -msgstr "Fault" -msgid "SUN4U-8004-PY.severity" -msgstr "Critical" -msgid "SUN4U-8004-PY.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-PY.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-PY.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-PY.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-Q3 -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-Q3.type" -msgstr "Fault" -msgid "SUN4U-8004-Q3.severity" -msgstr "Critical" -msgid "SUN4U-8004-Q3.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-Q3.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-Q3.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-Q3.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-RC -# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-RC.type" -msgstr "Fault" -msgid "SUN4U-8004-RC.severity" -msgstr "Critical" -msgid "SUN4U-8004-RC.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-RC.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-RC.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-RC.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-SQ -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-SQ.type" -msgstr "Fault" -msgid "SUN4U-8004-SQ.severity" -msgstr "Critical" -msgid "SUN4U-8004-SQ.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-SQ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-SQ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-SQ.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-T4 -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-T4.type" -msgstr "Fault" -msgid "SUN4U-8004-T4.severity" -msgstr "Critical" -msgid "SUN4U-8004-T4.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-T4.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-T4.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-T4.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-UR -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits -# -msgid "SUN4U-8004-UR.type" -msgstr "Fault" -msgid "SUN4U-8004-UR.severity" -msgstr "Critical" -msgid "SUN4U-8004-UR.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-UR.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-UR.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-UR.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-V2 -# keys: fault.io.psycho -# -msgid "SUN4U-8004-V2.type" -msgstr "Fault" -msgid "SUN4U-8004-V2.severity" -msgstr "Critical" -msgid "SUN4U-8004-V2.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-V2.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-V2.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-V2.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-WX -# keys: defect.io.pci.driver fault.io.psycho -# -msgid "SUN4U-8004-WX.type" -msgstr "Fault" -msgid "SUN4U-8004-WX.severity" -msgstr "Critical" -msgid "SUN4U-8004-WX.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-WX.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-WX.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-WX.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8004-XE -# keys: fault.io.datapath fault.io.psycho -# -msgid "SUN4U-8004-XE.type" -msgstr "Fault" -msgid "SUN4U-8004-XE.severity" -msgstr "Critical" -msgid "SUN4U-8004-XE.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8004-XE.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-XE.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-XE.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8004-YJ -# keys: defect.io.pci.driver fault.io.datapath fault.io.psycho -# -msgid "SUN4U-8004-YJ.type" -msgstr "Fault" -msgid "SUN4U-8004-YJ.severity" -msgstr "Critical" -msgid "SUN4U-8004-YJ.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8004-YJ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8004-YJ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8004-YJ.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-0E -# keys: fault.io.hbus fault.io.psycho -# -msgid "SUN4U-8005-0E.type" -msgstr "Fault" -msgid "SUN4U-8005-0E.severity" -msgstr "Critical" -msgid "SUN4U-8005-0E.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-0E.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-0E.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-0E.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-1J -# keys: defect.io.pci.driver fault.io.hbus fault.io.psycho -# -msgid "SUN4U-8005-1J.type" -msgstr "Fault" -msgid "SUN4U-8005-1J.severity" -msgstr "Critical" -msgid "SUN4U-8005-1J.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-1J.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-1J.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-1J.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-22 -# keys: fault.io.datapath fault.io.hbus fault.io.psycho -# -msgid "SUN4U-8005-22.type" -msgstr "Fault" -msgid "SUN4U-8005-22.severity" -msgstr "Critical" -msgid "SUN4U-8005-22.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-22.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-22.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-22.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-3X -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.psycho -# -msgid "SUN4U-8005-3X.type" -msgstr "Fault" -msgid "SUN4U-8005-3X.severity" -msgstr "Critical" -msgid "SUN4U-8005-3X.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-3X.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-3X.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-3X.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-44 -# keys: fault.io.pci.bus fault.io.psycho -# -msgid "SUN4U-8005-44.type" -msgstr "Fault" -msgid "SUN4U-8005-44.severity" -msgstr "Critical" -msgid "SUN4U-8005-44.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-44.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-44.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-44.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-5R -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.psycho -# -msgid "SUN4U-8005-5R.type" -msgstr "Fault" -msgid "SUN4U-8005-5R.severity" -msgstr "Critical" -msgid "SUN4U-8005-5R.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-5R.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-5R.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-5R.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-6C -# keys: fault.io.datapath fault.io.pci.bus fault.io.psycho -# -msgid "SUN4U-8005-6C.type" -msgstr "Fault" -msgid "SUN4U-8005-6C.severity" -msgstr "Critical" -msgid "SUN4U-8005-6C.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-6C.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-6C.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-6C.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-7Q -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.psycho -# -msgid "SUN4U-8005-7Q.type" -msgstr "Fault" -msgid "SUN4U-8005-7Q.severity" -msgstr "Critical" -msgid "SUN4U-8005-7Q.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-7Q.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-7Q.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-7Q.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-8Y -# keys: fault.io.hbus fault.io.pci.bus fault.io.psycho -# -msgid "SUN4U-8005-8Y.type" -msgstr "Fault" -msgid "SUN4U-8005-8Y.severity" -msgstr "Critical" -msgid "SUN4U-8005-8Y.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-8Y.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-8Y.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-8Y.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-93 -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.psycho -# -msgid "SUN4U-8005-93.type" -msgstr "Fault" -msgid "SUN4U-8005-93.severity" -msgstr "Critical" -msgid "SUN4U-8005-93.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-93.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-93.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-93.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-AH -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho -# -msgid "SUN4U-8005-AH.type" -msgstr "Fault" -msgid "SUN4U-8005-AH.severity" -msgstr "Critical" -msgid "SUN4U-8005-AH.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-AH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-AH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-AH.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-CD -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho -# -msgid "SUN4U-8005-CD.type" -msgstr "Fault" -msgid "SUN4U-8005-CD.severity" -msgstr "Critical" -msgid "SUN4U-8005-CD.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-CD.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-CD.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-CD.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-DP -# keys: fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-DP.type" -msgstr "Fault" -msgid "SUN4U-8005-DP.severity" -msgstr "Critical" -msgid "SUN4U-8005-DP.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-DP.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-DP.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-DP.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-EA -# keys: defect.io.pci.driver fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-EA.type" -msgstr "Fault" -msgid "SUN4U-8005-EA.severity" -msgstr "Critical" -msgid "SUN4U-8005-EA.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-EA.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-EA.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-EA.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-FS -# keys: fault.io.datapath fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-FS.type" -msgstr "Fault" -msgid "SUN4U-8005-FS.severity" -msgstr "Critical" -msgid "SUN4U-8005-FS.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-FS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-FS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-FS.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-G5 -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-G5.type" -msgstr "Fault" -msgid "SUN4U-8005-G5.severity" -msgstr "Critical" -msgid "SUN4U-8005-G5.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-G5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-G5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-G5.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-HX -# keys: fault.io.hbus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-HX.type" -msgstr "Fault" -msgid "SUN4U-8005-HX.severity" -msgstr "Critical" -msgid "SUN4U-8005-HX.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-HX.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-HX.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-HX.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-J2 -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-J2.type" -msgstr "Fault" -msgid "SUN4U-8005-J2.severity" -msgstr "Critical" -msgid "SUN4U-8005-J2.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-J2.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-J2.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-J2.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-KJ -# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-KJ.type" -msgstr "Fault" -msgid "SUN4U-8005-KJ.severity" -msgstr "Critical" -msgid "SUN4U-8005-KJ.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-KJ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-KJ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-KJ.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-LE -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-LE.type" -msgstr "Fault" -msgid "SUN4U-8005-LE.severity" -msgstr "Critical" -msgid "SUN4U-8005-LE.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-LE.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-LE.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-LE.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-MQ -# keys: fault.io.pci.bus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-MQ.type" -msgstr "Fault" -msgid "SUN4U-8005-MQ.severity" -msgstr "Critical" -msgid "SUN4U-8005-MQ.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-MQ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-MQ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-MQ.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-NC -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-NC.type" -msgstr "Fault" -msgid "SUN4U-8005-NC.severity" -msgstr "Critical" -msgid "SUN4U-8005-NC.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-NC.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-NC.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-NC.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-PR -# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-PR.type" -msgstr "Fault" -msgid "SUN4U-8005-PR.severity" -msgstr "Critical" -msgid "SUN4U-8005-PR.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-PR.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-PR.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-PR.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-Q4 -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-Q4.type" -msgstr "Fault" -msgid "SUN4U-8005-Q4.severity" -msgstr "Critical" -msgid "SUN4U-8005-Q4.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-Q4.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-Q4.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-Q4.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-RD -# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-RD.type" -msgstr "Fault" -msgid "SUN4U-8005-RD.severity" -msgstr "Critical" -msgid "SUN4U-8005-RD.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-RD.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-RD.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-RD.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-SH -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-SH.type" -msgstr "Fault" -msgid "SUN4U-8005-SH.severity" -msgstr "Critical" -msgid "SUN4U-8005-SH.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-SH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-SH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-SH.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-T3 -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-T3.type" -msgstr "Fault" -msgid "SUN4U-8005-T3.severity" -msgstr "Critical" -msgid "SUN4U-8005-T3.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-T3.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-T3.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-T3.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-UY -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho -# -msgid "SUN4U-8005-UY.type" -msgstr "Fault" -msgid "SUN4U-8005-UY.severity" -msgstr "Critical" -msgid "SUN4U-8005-UY.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-UY.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-UY.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-UY.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-V5 -# keys: fault.io.tomatillo -# -msgid "SUN4U-8005-V5.type" -msgstr "Fault" -msgid "SUN4U-8005-V5.severity" -msgstr "Critical" -msgid "SUN4U-8005-V5.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-V5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-V5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-V5.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-WS -# keys: defect.io.pci.driver fault.io.tomatillo -# -msgid "SUN4U-8005-WS.type" -msgstr "Fault" -msgid "SUN4U-8005-WS.severity" -msgstr "Critical" -msgid "SUN4U-8005-WS.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-WS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-WS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-WS.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8005-XA -# keys: fault.io.datapath fault.io.tomatillo -# -msgid "SUN4U-8005-XA.type" -msgstr "Fault" -msgid "SUN4U-8005-XA.severity" -msgstr "Critical" -msgid "SUN4U-8005-XA.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8005-XA.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-XA.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-XA.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8005-YP -# keys: defect.io.pci.driver fault.io.datapath fault.io.tomatillo -# -msgid "SUN4U-8005-YP.type" -msgstr "Fault" -msgid "SUN4U-8005-YP.severity" -msgstr "Critical" -msgid "SUN4U-8005-YP.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8005-YP.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8005-YP.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8005-YP.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-04 -# keys: fault.io.hbus fault.io.tomatillo -# -msgid "SUN4U-8006-04.type" -msgstr "Fault" -msgid "SUN4U-8006-04.severity" -msgstr "Critical" -msgid "SUN4U-8006-04.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-04.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-04.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-04.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-1R -# keys: defect.io.pci.driver fault.io.hbus fault.io.tomatillo -# -msgid "SUN4U-8006-1R.type" -msgstr "Fault" -msgid "SUN4U-8006-1R.severity" -msgstr "Critical" -msgid "SUN4U-8006-1R.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-1R.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-1R.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-1R.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-2C -# keys: fault.io.datapath fault.io.hbus fault.io.tomatillo -# -msgid "SUN4U-8006-2C.type" -msgstr "Fault" -msgid "SUN4U-8006-2C.severity" -msgstr "Critical" -msgid "SUN4U-8006-2C.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-2C.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-2C.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-2C.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-3Q -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.tomatillo -# -msgid "SUN4U-8006-3Q.type" -msgstr "Fault" -msgid "SUN4U-8006-3Q.severity" -msgstr "Critical" -msgid "SUN4U-8006-3Q.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-3Q.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-3Q.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-3Q.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-4E -# keys: fault.io.pci.bus fault.io.tomatillo -# -msgid "SUN4U-8006-4E.type" -msgstr "Fault" -msgid "SUN4U-8006-4E.severity" -msgstr "Critical" -msgid "SUN4U-8006-4E.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-4E.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-4E.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-4E.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-5J -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.tomatillo -# -msgid "SUN4U-8006-5J.type" -msgstr "Fault" -msgid "SUN4U-8006-5J.severity" -msgstr "Critical" -msgid "SUN4U-8006-5J.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-5J.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-5J.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-5J.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-62 -# keys: fault.io.datapath fault.io.pci.bus fault.io.tomatillo -# -msgid "SUN4U-8006-62.type" -msgstr "Fault" -msgid "SUN4U-8006-62.severity" -msgstr "Critical" -msgid "SUN4U-8006-62.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-62.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-62.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-62.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-7X -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.tomatillo -# -msgid "SUN4U-8006-7X.type" -msgstr "Fault" -msgid "SUN4U-8006-7X.severity" -msgstr "Critical" -msgid "SUN4U-8006-7X.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-7X.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-7X.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-7X.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-8P -# keys: fault.io.hbus fault.io.pci.bus fault.io.tomatillo -# -msgid "SUN4U-8006-8P.type" -msgstr "Fault" -msgid "SUN4U-8006-8P.severity" -msgstr "Critical" -msgid "SUN4U-8006-8P.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-8P.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-8P.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-8P.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-9A -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.tomatillo -# -msgid "SUN4U-8006-9A.type" -msgstr "Fault" -msgid "SUN4U-8006-9A.severity" -msgstr "Critical" -msgid "SUN4U-8006-9A.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-9A.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-9A.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-9A.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-AS -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo -# -msgid "SUN4U-8006-AS.type" -msgstr "Fault" -msgid "SUN4U-8006-AS.severity" -msgstr "Critical" -msgid "SUN4U-8006-AS.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-AS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-AS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-AS.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-C5 -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo -# -msgid "SUN4U-8006-C5.type" -msgstr "Fault" -msgid "SUN4U-8006-C5.severity" -msgstr "Critical" -msgid "SUN4U-8006-C5.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-C5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-C5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-C5.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-DY -# keys: fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-DY.type" -msgstr "Fault" -msgid "SUN4U-8006-DY.severity" -msgstr "Critical" -msgid "SUN4U-8006-DY.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-DY.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-DY.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-DY.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-E3 -# keys: defect.io.pci.driver fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-E3.type" -msgstr "Fault" -msgid "SUN4U-8006-E3.severity" -msgstr "Critical" -msgid "SUN4U-8006-E3.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-E3.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-E3.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-E3.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-FH -# keys: fault.io.datapath fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-FH.type" -msgstr "Fault" -msgid "SUN4U-8006-FH.severity" -msgstr "Critical" -msgid "SUN4U-8006-FH.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-FH.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-FH.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-FH.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-GD -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-GD.type" -msgstr "Fault" -msgid "SUN4U-8006-GD.severity" -msgstr "Critical" -msgid "SUN4U-8006-GD.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-GD.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-GD.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-GD.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-HQ -# keys: fault.io.hbus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-HQ.type" -msgstr "Fault" -msgid "SUN4U-8006-HQ.severity" -msgstr "Critical" -msgid "SUN4U-8006-HQ.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-HQ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-HQ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-HQ.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-JC -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-JC.type" -msgstr "Fault" -msgid "SUN4U-8006-JC.severity" -msgstr "Critical" -msgid "SUN4U-8006-JC.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-JC.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-JC.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-JC.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-KR -# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-KR.type" -msgstr "Fault" -msgid "SUN4U-8006-KR.severity" -msgstr "Critical" -msgid "SUN4U-8006-KR.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-KR.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-KR.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-KR.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-L4 -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-L4.type" -msgstr "Fault" -msgid "SUN4U-8006-L4.severity" -msgstr "Critical" -msgid "SUN4U-8006-L4.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-L4.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-L4.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-L4.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-MX -# keys: fault.io.pci.bus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-MX.type" -msgstr "Fault" -msgid "SUN4U-8006-MX.severity" -msgstr "Critical" -msgid "SUN4U-8006-MX.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-MX.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-MX.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-MX.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-N2 -# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-N2.type" -msgstr "Fault" -msgid "SUN4U-8006-N2.severity" -msgstr "Critical" -msgid "SUN4U-8006-N2.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-N2.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-N2.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-N2.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-PJ -# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-PJ.type" -msgstr "Fault" -msgid "SUN4U-8006-PJ.severity" -msgstr "Critical" -msgid "SUN4U-8006-PJ.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-PJ.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-PJ.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-PJ.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-QE -# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-QE.type" -msgstr "Fault" -msgid "SUN4U-8006-QE.severity" -msgstr "Critical" -msgid "SUN4U-8006-QE.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-QE.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-QE.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-QE.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-R5 -# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-R5.type" -msgstr "Fault" -msgid "SUN4U-8006-R5.severity" -msgstr "Critical" -msgid "SUN4U-8006-R5.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-R5.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-R5.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-R5.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-SS -# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-SS.type" -msgstr "Fault" -msgid "SUN4U-8006-SS.severity" -msgstr "Critical" -msgid "SUN4U-8006-SS.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-SS.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-SS.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-SS.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-TA -# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-TA.type" -msgstr "Fault" -msgid "SUN4U-8006-TA.severity" -msgstr "Critical" -msgid "SUN4U-8006-TA.description" -msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." -msgid "SUN4U-8006-TA.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-TA.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-TA.action" -msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n" -# -# code: SUN4U-8006-UP -# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo -# -msgid "SUN4U-8006-UP.type" -msgstr "Fault" -msgid "SUN4U-8006-UP.severity" -msgstr "Critical" -msgid "SUN4U-8006-UP.description" -msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information." -msgid "SUN4U-8006-UP.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8006-UP.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8006-UP.action" -msgstr "\nUse fmdump -v -u to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is software, then consult\nyour illumos distribution team.\n" -# -# code: SUN4U-8006-VD -# keys: fault.cpu.ultraSPARC-IIIiplus.dcache -# -msgid "SUN4U-8006-VD.type" -msgstr "Fault" -msgid "SUN4U-8006-VD.severity" -msgstr "Major" -msgid "SUN4U-8006-VD.description" -msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8006-VD.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8006-VD.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8006-VD.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8006-WH -# keys: fault.cpu.ultraSPARC-IIIiplus.icache -# -msgid "SUN4U-8006-WH.type" -msgstr "Fault" -msgid "SUN4U-8006-WH.severity" -msgstr "Major" -msgid "SUN4U-8006-WH.description" -msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8006-WH.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8006-WH.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8006-WH.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8006-X3 -# keys: fault.cpu.ultraSPARC-IIIiplus.l2cachedata -# -msgid "SUN4U-8006-X3.type" -msgstr "Fault" -msgid "SUN4U-8006-X3.severity" -msgstr "Major" -msgid "SUN4U-8006-X3.description" -msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8006-X3.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8006-X3.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8006-X3.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8006-YY -# keys: fault.cpu.ultraSPARC-IIIiplus.l2cachetag -# -msgid "SUN4U-8006-YY.type" -msgstr "Fault" -msgid "SUN4U-8006-YY.severity" -msgstr "Major" -msgid "SUN4U-8006-YY.description" -msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8006-YY.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8006-YY.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8006-YY.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8007-03 -# keys: fault.cpu.ultraSPARC-IIIiplus.fpu -# -msgid "SUN4U-8007-03.type" -msgstr "Fault" -msgid "SUN4U-8007-03.severity" -msgstr "Major" -msgid "SUN4U-8007-03.description" -msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8007-03.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4U-8007-03.impact" -msgstr "System performance may be affected." -msgid "SUN4U-8007-03.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4U-8007-1Y -# keys: fault.asic.cds.dp -# -msgid "SUN4U-8007-1Y.type" -msgstr "Fault" -msgid "SUN4U-8007-1Y.severity" -msgstr "Critical" -msgid "SUN4U-8007-1Y.description" -msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." -msgid "SUN4U-8007-1Y.response" -msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" -msgid "SUN4U-8007-1Y.impact" -msgstr "System performace may be affected.\n" -msgid "SUN4U-8007-1Y.action" -msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u can also be used, but the SC is authoritative.\n" -# -# code: SUN4U-8007-2D -# keys: fault.asic.dx.dp -# -msgid "SUN4U-8007-2D.type" -msgstr "Fault" -msgid "SUN4U-8007-2D.severity" -msgstr "Critical" -msgid "SUN4U-8007-2D.description" -msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." -msgid "SUN4U-8007-2D.response" -msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" -msgid "SUN4U-8007-2D.impact" -msgstr "System performace may be affected.\n" -msgid "SUN4U-8007-2D.action" -msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u can also be used, but the SC is authoritative.\n" -# -# code: SUN4U-8007-3H -# keys: fault.asic.sdi.dp -# -msgid "SUN4U-8007-3H.type" -msgstr "Fault" -msgid "SUN4U-8007-3H.severity" -msgstr "Critical" -msgid "SUN4U-8007-3H.description" -msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." -msgid "SUN4U-8007-3H.response" -msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" -msgid "SUN4U-8007-3H.impact" -msgstr "System performace may be affected.\n" -msgid "SUN4U-8007-3H.action" -msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u can also be used, but the SC is authoritative.\n" -# -# code: SUN4U-8007-4A -# keys: fault.asic.cp.dp -# -msgid "SUN4U-8007-4A.type" -msgstr "Fault" -msgid "SUN4U-8007-4A.severity" -msgstr "Critical" -msgid "SUN4U-8007-4A.description" -msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." -msgid "SUN4U-8007-4A.response" -msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" -msgid "SUN4U-8007-4A.impact" -msgstr "System performace may be affected.\n" -msgid "SUN4U-8007-4A.action" -msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u can also be used, but the SC is authoritative.\n" -# -# code: SUN4U-8007-5P -# keys: fault.asic.rp.dp -# -msgid "SUN4U-8007-5P.type" -msgstr "Fault" -msgid "SUN4U-8007-5P.severity" -msgstr "Critical" -msgid "SUN4U-8007-5P.description" -msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." -msgid "SUN4U-8007-5P.response" -msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" -msgid "SUN4U-8007-5P.impact" -msgstr "System performace may be affected.\n" -msgid "SUN4U-8007-5P.action" -msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u can also be used, but the SC is authoritative.\n" -# -# code: SUN4U-8007-65 -# keys: fault.io.oberon -# -msgid "SUN4U-8007-65.type" -msgstr "Fault" -msgid "SUN4U-8007-65.severity" -msgstr "Critical" -msgid "SUN4U-8007-65.description" -msgstr "Oberon PCI-Express hostbridge fault\n Refer to %s for more information." -msgid "SUN4U-8007-65.response" -msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." -msgid "SUN4U-8007-65.impact" -msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." -msgid "SUN4U-8007-65.action" -msgstr "Ensure that the latest drivers and patches are installed, schedule a repair procedure to replace the affected device if necessary, or contact your illumos distribution team for support." -# -# code: SUN4U-8007-7S -# keys: fault.cpu.SPARC64-VI.chip -# -msgid "SUN4U-8007-7S.type" -msgstr "Fault" -msgid "SUN4U-8007-7S.severity" -msgstr "Critical" -msgid "SUN4U-8007-7S.description" -msgstr "The number of errors associated with this CHIP has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8007-7S.response" -msgstr "An attempt will be made to remove the affected CHIP from service." -msgid "SUN4U-8007-7S.impact" -msgstr "The system will not be functioning at the same performance level with the CHIP removal." -msgid "SUN4U-8007-7S.action" -msgstr "Schedule a repair procedure to replace the affected CHIP. Use fmdump -v -u \nto identify the smallest CPU/Strand ID of the affected CORE on this\nCHIP." -# -# code: SUN4U-8007-8J -# keys: fault.cpu.SPARC64-VI.core -# -msgid "SUN4U-8007-8J.type" -msgstr "Fault" -msgid "SUN4U-8007-8J.severity" -msgstr "Critical" -msgid "SUN4U-8007-8J.description" -msgstr "The number of errors associated with this CORE has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8007-8J.response" -msgstr "An attempt will be made to remove the affected CORE from service." -msgid "SUN4U-8007-8J.impact" -msgstr "The system will not be functioning at the same performance level with the CORE removal." -msgid "SUN4U-8007-8J.action" -msgstr "Schedule a repair procedure to replace the affected CORE. Use fmdump -v -u \nto identify the smallest CPU/Strand ID of the affected CORE on this\nCORE.\n" -# -# code: SUN4U-8007-9E -# keys: fault.cpu.SPARC64-VI.strand -# -msgid "SUN4U-8007-9E.type" -msgstr "Fault" -msgid "SUN4U-8007-9E.severity" -msgstr "Critical" -msgid "SUN4U-8007-9E.description" -msgstr "The number of errors associated with this STRAND has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8007-9E.response" -msgstr "An attempt will be made to remove the affected STRAND from service." -msgid "SUN4U-8007-9E.impact" -msgstr "The system will not be functioning at the same performance level with the STRAND removal." -msgid "SUN4U-8007-9E.action" -msgstr "Schedule a repair procedure to replace the affected STRAND. Use fmdump -v -u \nto identify the smallest CPU/Strand ID of the affected CORE on this\nSTRAND.\n" -# -# code: SUN4U-8007-AX -# keys: fault.io.pci.device-invreq fault.io.tomatillo -# -msgid "SUN4U-8007-AX.type" -msgstr "Fault" -msgid "SUN4U-8007-AX.severity" -msgstr "Critical" -msgid "SUN4U-8007-AX.description" -msgstr "Either the transmitting device sent an invalid request or the receiving device failed to respond.\n Refer to %s for more information." -msgid "SUN4U-8007-AX.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4U-8007-AX.impact" -msgstr "Loss of services provided by the device instances associated with this fault\n" -msgid "SUN4U-8007-AX.action" -msgstr "Ensure that the latest drivers and patches are installed. If a plug-in card is involved check for badly-seated cards or bent pins. Otherwise schedule a repair procedure to replace the affected device(s). Use fmdump -v -u to identify the devices or contact your illumos distribution team for support.\n" -# -# code: SUN4U-8007-C2 -# keys: fault.cpu.SPARC64-VII.chip -# -msgid "SUN4U-8007-C2.type" -msgstr "Fault" -msgid "SUN4U-8007-C2.severity" -msgstr "Critical" -msgid "SUN4U-8007-C2.description" -msgstr "The number of errors associated with this CHIP has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8007-C2.response" -msgstr "An attempt will be made to remove the affected CHIP from service." -msgid "SUN4U-8007-C2.impact" -msgstr "The system will not be functioning at the same performance level with the CHIP removal." -msgid "SUN4U-8007-C2.action" -msgstr "Schedule a repair procedure to replace the affected CHIP. Use fmdump -v -u \nto identify the smallest CPU/Strand ID of the affected CORE on this\nCHIP." -# -# code: SUN4U-8007-DR -# keys: fault.cpu.SPARC64-VII.core -# -msgid "SUN4U-8007-DR.type" -msgstr "Fault" -msgid "SUN4U-8007-DR.severity" -msgstr "Critical" -msgid "SUN4U-8007-DR.description" -msgstr "The number of errors associated with this CORE has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8007-DR.response" -msgstr "An attempt will be made to remove the affected CORE from service." -msgid "SUN4U-8007-DR.impact" -msgstr "The system will not be functioning at the same performance level with the CORE removal." -msgid "SUN4U-8007-DR.action" -msgstr "Schedule a repair procedure to replace the affected CORE. Use fmdump -v -u \nto identify the smallest CPU/Strand ID of the affected CORE on this\nCORE.\n" -# -# code: SUN4U-8007-E4 -# keys: fault.cpu.SPARC64-VII.strand -# -msgid "SUN4U-8007-E4.type" -msgstr "Fault" -msgid "SUN4U-8007-E4.severity" -msgstr "Critical" -msgid "SUN4U-8007-E4.description" -msgstr "The number of errors associated with this STRAND has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4U-8007-E4.response" -msgstr "An attempt will be made to remove the affected STRAND from service." -msgid "SUN4U-8007-E4.impact" -msgstr "The system will not be functioning at the same performance level with the STRAND removal." -msgid "SUN4U-8007-E4.action" -msgstr "Schedule a repair procedure to replace the affected STRAND. Use fmdump -v -u \nto identify the smallest CPU/Strand ID of the affected CORE on this\nSTRAND.\n" -# -# code: SUN4U-8007-FQ -# keys: fault.cpu.ultraSPARC-IVplus.l2cachedata-line -# -msgid "SUN4U-8007-FQ.type" -msgstr "Fault" -msgid "SUN4U-8007-FQ.severity" -msgstr "Minor" -msgid "SUN4U-8007-FQ.description" -msgstr "The illumos Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n Refer to %s for more information." -msgid "SUN4U-8007-FQ.response" -msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n" -msgid "SUN4U-8007-FQ.impact" -msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n" -msgid "SUN4U-8007-FQ.action" -msgstr "No repair action is recommended at this time.\n" -# -# code: SUN4U-8007-GC -# keys: fault.cpu.ultraSPARC-IVplus.l3cachedata-line -# -msgid "SUN4U-8007-GC.type" -msgstr "Fault" -msgid "SUN4U-8007-GC.severity" -msgstr "Minor" -msgid "SUN4U-8007-GC.description" -msgstr "The illumos Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n Refer to %s for more information." -msgid "SUN4U-8007-GC.response" -msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n" -msgid "SUN4U-8007-GC.impact" -msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n" -msgid "SUN4U-8007-GC.action" -msgstr "No repair action is recommended at this time.\n" -# -# code: SUN4U-8007-HH -# keys: fault.cpu.ultraSPARC-IVplus.l2cachetag-line -# -msgid "SUN4U-8007-HH.type" -msgstr "Fault" -msgid "SUN4U-8007-HH.severity" -msgstr "Minor" -msgid "SUN4U-8007-HH.description" -msgstr "The illumos Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n Refer to %s for more information." -msgid "SUN4U-8007-HH.response" -msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n" -msgid "SUN4U-8007-HH.impact" -msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n" -msgid "SUN4U-8007-HH.action" -msgstr "No repair action is recommended at this time.\n" -# -# code: SUN4U-8007-JD -# keys: fault.cpu.ultraSPARC-IVplus.l3cachetag-line -# -msgid "SUN4U-8007-JD.type" -msgstr "Fault" -msgid "SUN4U-8007-JD.severity" -msgstr "Minor" -msgid "SUN4U-8007-JD.description" -msgstr "The illumos Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n Refer to %s for more information." -msgid "SUN4U-8007-JD.response" -msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n" -msgid "SUN4U-8007-JD.impact" -msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n" -msgid "SUN4U-8007-JD.action" -msgstr "No repair action is recommended at this time.\n" -# -# code: SUN4U-8007-KY -# keys: fault.memory.dimm-page-retires-excessive -# -msgid "SUN4U-8007-KY.type" -msgstr "Fault" -msgid "SUN4U-8007-KY.severity" -msgstr "Major" -msgid "SUN4U-8007-KY.description" -msgstr "The number of correctable errors associated with this memory module has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4U-8007-KY.response" -msgstr "Pages of memory associated with this memory module have been removed from service, up to a limit which has now been reached.\n" -msgid "SUN4U-8007-KY.impact" -msgstr "Total system memory capacity has been reduced.\n" -msgid "SUN4U-8007-KY.action" -msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n" -# -# code: SUN4U-8007-L3 -# keys: fault.memory.dimm-ue-imminent -# -msgid "SUN4U-8007-L3.type" -msgstr "Fault" -msgid "SUN4U-8007-L3.severity" -msgstr "Critical" -msgid "SUN4U-8007-L3.description" -msgstr "A pattern of correctable errors has been observed suggesting the potential exists that an uncorrectable error may occur.\n Refer to %s for more information." -msgid "SUN4U-8007-L3.response" -msgstr "None at this time.\n" -msgid "SUN4U-8007-L3.impact" -msgstr "None at this time. However, the potential uncorrectable error warrants proactive service action to avoid any unplanned system outages.\n" -msgid "SUN4U-8007-L3.action" -msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n" -# -# code: SUN4U-8007-MS -# keys: fault.memory.dram-ue-imminent -# -msgid "SUN4U-8007-MS.type" -msgstr "Fault" -msgid "SUN4U-8007-MS.severity" -msgstr "Critical" -msgid "SUN4U-8007-MS.description" -msgstr "A pattern of correctable errors has been observed suggesting the potential exists that an uncorrectable error may occur.\n Refer to %s for more information." -msgid "SUN4U-8007-MS.response" -msgstr "None at this time.\n" -msgid "SUN4U-8007-MS.impact" -msgstr "None at this time. However, the potential uncorrectable error warrants proactive service action to avoid any unplanned system outages.\n" -msgid "SUN4U-8007-MS.action" -msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n" diff --git a/usr/src/cmd/fm/dicts/SUN4V.dict b/usr/src/cmd/fm/dicts/SUN4V.dict deleted file mode 100644 index ba51084f36..0000000000 --- a/usr/src/cmd/fm/dicts/SUN4V.dict +++ /dev/null @@ -1,119 +0,0 @@ -# -# Copyright 2009 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# DO NOT EDIT -- this file is generated by the Event Registry. -# - -FMDICT: name=SUN4V version=1 maxkey=3 dictid=0x3456 - -fault.cpu.ultraSPARC-T1.ireg=1 -fault.cpu.ultraSPARC-T1.freg=2 -fault.cpu.ultraSPARC-T1.itlb=3 -fault.cpu.ultraSPARC-T1.dtlb=4 -fault.cpu.ultraSPARC-T1.icache=5 -fault.cpu.ultraSPARC-T1.dcache=6 -fault.cpu.ultraSPARC-T1.mau=7 -fault.cpu.ultraSPARC-T1.l2cachedata=8 -fault.cpu.ultraSPARC-T1.l2cachetag=9 -fault.cpu.ultraSPARC-T1.l2cachectl=10 -fault.memory.page=11 -fault.memory.dimm=12 -fault.memory.bank=13 -fault.memory.link-c=14 -fault.cpu.ultraSPARC-T2.ireg=15 -fault.cpu.ultraSPARC-T2.freg=16 -fault.cpu.ultraSPARC-T2.misc_reg=17 -fault.cpu.ultraSPARC-T2.itlb=18 -fault.cpu.ultraSPARC-T2.dtlb=19 -fault.cpu.ultraSPARC-T2.icache=20 -fault.cpu.ultraSPARC-T2.dcache=21 -fault.cpu.ultraSPARC-T2.mau=22 -fault.cpu.ultraSPARC-T2.l2data-c=23 -fault.cpu.ultraSPARC-T2.l2cachetag=24 -fault.cpu.ultraSPARC-T2.l2cachectl=25 -fault.memory.link-u=26 -fault.cpu.ultraSPARC-T2.l2data-u=27 -fault.cpu.ultraSPARC-T1.l2data-c=28 -fault.cpu.ultraSPARC-T1.l2data-u=29 -fault.memory.datapath=30 -fault.io.n2.ncu=31 -fault.io.n2.dmu=32 -fault.io.n2.niu=33 -fault.io.n2.siu=34 -fault.io.n2.soc=35 -fault.io.n2.crossbar=36 -fault.io.fire.fw-epkt fault.io.fire.sw-epkt fault.io.fire.sw-fw-mismatch=37 -fault.io.vf.ncx=38 -fault.memory.link-f=39 -fault.cpu.ultraSPARC-T2plus.ireg=40 -fault.cpu.ultraSPARC-T2plus.freg=41 -fault.cpu.ultraSPARC-T2plus.misc_reg=42 -fault.cpu.ultraSPARC-T2plus.itlb=43 -fault.cpu.ultraSPARC-T2plus.dtlb=44 -fault.cpu.ultraSPARC-T2plus.icache=45 -fault.cpu.ultraSPARC-T2plus.dcache=46 -fault.cpu.ultraSPARC-T2plus.mau=47 -fault.cpu.ultraSPARC-T2plus.l2data-c=48 -fault.cpu.ultraSPARC-T2plus.l2cachetag=49 -fault.cpu.ultraSPARC-T2plus.l2cachectl=50 -fault.cpu.ultraSPARC-T2plus.l2data-u=51 -fault.cpu.ultraSPARC-T2plus.lfu-f=52 -fault.cpu.ultraSPARC-T2plus.lfu-p=53 -fault.cpu.ultraSPARC-T2plus.lfu-u=54 -fault.asic.ultraSPARC-T2plus.interconnect.opu-u=55 -fault.asic.ultraSPARC-T2plus.interconnect.opu-c=56 -fault.cpu.ultraSPARC-T2plus.chip=57 -fault.asic.ultraSPARC-T2plus.interconnect.lfu-c fault.cpu.ultraSPARC-T2plus.chip=58 -fault.asic.ultraSPARC-T2plus.interconnect.lfu-f fault.cpu.ultraSPARC-T2plus.chip=59 -fault.asic.ultraSPARC-T2plus.interconnect.lfu-u fault.cpu.ultraSPARC-T2plus.chip=60 -fault.asic.ultraSPARC-T2plus.interconnect.lfu-u=61 -fault.asic.ultraSPARC-T2plus.interconnect.gpd-u fault.cpu.ultraSPARC-T2plus.chip=62 -fault.asic.ultraSPARC-T2plus.interconnect.gpd-c fault.cpu.ultraSPARC-T2plus.chip=63 -fault.asic.ultraSPARC-T2plus.interconnect.gpd-c=64 -fault.asic.fpga fault.asic.ultraSPARC-T2plus.interconnect.gpd-c=65 -fault.asic.ultraSPARC-T2plus.interconnect.asu=66 -fault.memory.dimm-page-retires-excessive=67 -fault.memory.dimm-ue-imminent=68 -fault.memory.dram-ue-imminent=69 -fault.cpu.generic-sparc.strand=70 -fault.cpu.generic-sparc.strand-nr=71 -fault.cpu.generic-sparc.strand-uc=72 -fault.cpu.generic-sparc.strand-uc-nr=73 -fault.cpu.generic-sparc.core=74 -fault.cpu.generic-sparc.core-nr=75 -fault.cpu.generic-sparc.core-uc=76 -fault.cpu.generic-sparc.core-uc-nr=77 -fault.cpu.generic-sparc.chip=78 -fault.cpu.generic-sparc.chip-nr=79 -fault.cpu.generic-sparc.chip-uc=80 -fault.cpu.generic-sparc.chip-uc-nr=81 -fault.cpu.generic-sparc.c2c=82 -fault.cpu.generic-sparc.c2c-failover=83 -fault.cpu.generic-sparc.c2c-uc=84 -fault.memory.memlink=85 -fault.memory.memlink-failover=86 -fault.memory.memlink-uc=87 -defect.fw.generic-sparc.addr-oob=88 -defect.fw.generic-sparc.erpt-gen=89 -fault.cpu.generic-sparc.bootbus=90 -fault.sp.failed=91 diff --git a/usr/src/cmd/fm/dicts/SUN4V.po b/usr/src/cmd/fm/dicts/SUN4V.po deleted file mode 100644 index 39c9320a24..0000000000 --- a/usr/src/cmd/fm/dicts/SUN4V.po +++ /dev/null @@ -1,1481 +0,0 @@ -# -# Copyright 2009 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# DO NOT EDIT -- this file is generated by the Event Registry. -# -# -# code: SUN4V-8000-1S -# keys: fault.cpu.ultraSPARC-T1.ireg -# -msgid "SUN4V-8000-1S.type" -msgstr "Fault" -msgid "SUN4V-8000-1S.severity" -msgstr "Minor" -msgid "SUN4V-8000-1S.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-1S.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4V-8000-1S.impact" -msgstr "System performance may be affected." -msgid "SUN4V-8000-1S.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-2A -# keys: fault.cpu.ultraSPARC-T1.freg -# -msgid "SUN4V-8000-2A.type" -msgstr "Fault" -msgid "SUN4V-8000-2A.severity" -msgstr "Major" -msgid "SUN4V-8000-2A.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-2A.response" -msgstr "None" -msgid "SUN4V-8000-2A.impact" -msgstr "System performance may be affected." -msgid "SUN4V-8000-2A.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-3P -# keys: fault.cpu.ultraSPARC-T1.itlb -# -msgid "SUN4V-8000-3P.type" -msgstr "Fault" -msgid "SUN4V-8000-3P.severity" -msgstr "Minor" -msgid "SUN4V-8000-3P.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-3P.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4V-8000-3P.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8000-3P.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-4D -# keys: fault.cpu.ultraSPARC-T1.dtlb -# -msgid "SUN4V-8000-4D.type" -msgstr "Fault" -msgid "SUN4V-8000-4D.severity" -msgstr "Minor" -msgid "SUN4V-8000-4D.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-4D.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4V-8000-4D.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8000-4D.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-5H -# keys: fault.cpu.ultraSPARC-T1.icache -# -msgid "SUN4V-8000-5H.type" -msgstr "Fault" -msgid "SUN4V-8000-5H.severity" -msgstr "Minor" -msgid "SUN4V-8000-5H.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-5H.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4V-8000-5H.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8000-5H.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-63 -# keys: fault.cpu.ultraSPARC-T1.dcache -# -msgid "SUN4V-8000-63.type" -msgstr "Fault" -msgid "SUN4V-8000-63.severity" -msgstr "Minor" -msgid "SUN4V-8000-63.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-63.response" -msgstr "The fault manager will attempt to remove the affected CPU from service." -msgid "SUN4V-8000-63.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8000-63.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-7Y -# keys: fault.cpu.ultraSPARC-T1.mau -# -msgid "SUN4V-8000-7Y.type" -msgstr "Fault" -msgid "SUN4V-8000-7Y.severity" -msgstr "Major" -msgid "SUN4V-8000-7Y.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-7Y.response" -msgstr "None" -msgid "SUN4V-8000-7Y.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8000-7Y.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-8Q -# keys: fault.cpu.ultraSPARC-T1.l2cachedata -# -msgid "SUN4V-8000-8Q.type" -msgstr "Fault" -msgid "SUN4V-8000-8Q.severity" -msgstr "Critical" -msgid "SUN4V-8000-8Q.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-8Q.response" -msgstr "None" -msgid "SUN4V-8000-8Q.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8000-8Q.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-9C -# keys: fault.cpu.ultraSPARC-T1.l2cachetag -# -msgid "SUN4V-8000-9C.type" -msgstr "Fault" -msgid "SUN4V-8000-9C.severity" -msgstr "Critical" -msgid "SUN4V-8000-9C.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-9C.response" -msgstr "None" -msgid "SUN4V-8000-9C.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8000-9C.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-AR -# keys: fault.cpu.ultraSPARC-T1.l2cachectl -# -msgid "SUN4V-8000-AR.type" -msgstr "Fault" -msgid "SUN4V-8000-AR.severity" -msgstr "Critical" -msgid "SUN4V-8000-AR.description" -msgstr "The number of errors associated with this CPU has exceeded \n acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-AR.response" -msgstr "None" -msgid "SUN4V-8000-AR.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8000-AR.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u ." -# -# code: SUN4V-8000-C4 -# keys: fault.memory.page -# -msgid "SUN4V-8000-C4.type" -msgstr "Fault" -msgid "SUN4V-8000-C4.severity" -msgstr "Minor" -msgid "SUN4V-8000-C4.description" -msgstr "The number of errors associated with this memory module continues to exceed acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-C4.response" -msgstr "An attempt will be made to remove this memory page from service." -msgid "SUN4V-8000-C4.impact" -msgstr "The performance of the system may be minimally impacted as a result of removing the memory page from operation." -msgid "SUN4V-8000-C4.action" -msgstr "No repair action is recommended at this time." -# -# code: SUN4V-8000-DX -# keys: fault.memory.dimm -# -msgid "SUN4V-8000-DX.type" -msgstr "Fault" -msgid "SUN4V-8000-DX.severity" -msgstr "Major" -msgid "SUN4V-8000-DX.description" -msgstr "The number of correctable errors associated with this memory module has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-DX.response" -msgstr "Pages of memory associated with this memory module have been removed from service, up to a limit which has now been reached." -msgid "SUN4V-8000-DX.impact" -msgstr "Total system memory capacity has been reduced." -msgid "SUN4V-8000-DX.action" -msgstr "Schedule a repair procedure to replace the affected memory module. Use 'fmadm faulty' to identify the memory module." -# -# code: SUN4V-8000-E2 -# keys: fault.memory.bank -# -msgid "SUN4V-8000-E2.type" -msgstr "Fault" -msgid "SUN4V-8000-E2.severity" -msgstr "Critical" -msgid "SUN4V-8000-E2.description" -msgstr "The number of errors associated with this memory module has exceeded acceptable levels. Refer to %s for more information." -msgid "SUN4V-8000-E2.response" -msgstr "Pages of memory associated with this memory module are being removed from service as errors are reported." -msgid "SUN4V-8000-E2.impact" -msgstr "Total system memory capacity will be reduced as pages are retired." -msgid "SUN4V-8000-E2.action" -msgstr "Schedule a repair procedure to replace the affected memory module. Use fmdump -v -u to identify the module." -# -# code: SUN4V-8000-FJ -# keys: fault.memory.link-c -# -msgid "SUN4V-8000-FJ.type" -msgstr "Fault" -msgid "SUN4V-8000-FJ.severity" -msgstr "Major" -msgid "SUN4V-8000-FJ.description" -msgstr "A problem was detected in the interconnect between a memory DIMM module and\nits memory controller. \n Refer to %s for more information." -msgid "SUN4V-8000-FJ.response" -msgstr "No automated response.\n" -msgid "SUN4V-8000-FJ.impact" -msgstr "System performance may be impacted.\n" -msgid "SUN4V-8000-FJ.action" -msgstr "At a convenient time, try reseating the memory module(s). If the problem persists,\ncontact your hardware support team to schedule part replacement.\n" -# -# code: SUN4V-8000-GE -# keys: fault.cpu.ultraSPARC-T2.ireg -# -msgid "SUN4V-8000-GE.type" -msgstr "Fault" -msgid "SUN4V-8000-GE.severity" -msgstr "Minor" -msgid "SUN4V-8000-GE.description" -msgstr "The number of integer register errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-GE.response" -msgstr "The fault manager will attempt to remove the affected thread\nfrom service.\n" -msgid "SUN4V-8000-GE.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8000-GE.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-HP -# keys: fault.cpu.ultraSPARC-T2.freg -# -msgid "SUN4V-8000-HP.type" -msgstr "Fault" -msgid "SUN4V-8000-HP.severity" -msgstr "Minor" -msgid "SUN4V-8000-HP.description" -msgstr "The number of floating register errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-HP.response" -msgstr "The fault manager will attempt to remove the affected thread\nfrom service.\n" -msgid "SUN4V-8000-HP.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8000-HP.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-JA -# keys: fault.cpu.ultraSPARC-T2.misc_reg -# -msgid "SUN4V-8000-JA.type" -msgstr "Fault" -msgid "SUN4V-8000-JA.severity" -msgstr "Minor" -msgid "SUN4V-8000-JA.description" -msgstr "The number of ancillary register errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-JA.response" -msgstr "The fault manager will attempt to remove the affected thread\nfrom service.\n" -msgid "SUN4V-8000-JA.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8000-JA.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-KS -# keys: fault.cpu.ultraSPARC-T2.itlb -# -msgid "SUN4V-8000-KS.type" -msgstr "Fault" -msgid "SUN4V-8000-KS.severity" -msgstr "Major" -msgid "SUN4V-8000-KS.description" -msgstr "The number of ITLB errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-KS.response" -msgstr "The fault manager will attempt to remove all threads associated with\nthis resource from service.\n" -msgid "SUN4V-8000-KS.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-KS.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-L5 -# keys: fault.cpu.ultraSPARC-T2.dtlb -# -msgid "SUN4V-8000-L5.type" -msgstr "Fault" -msgid "SUN4V-8000-L5.severity" -msgstr "Major" -msgid "SUN4V-8000-L5.description" -msgstr "The number of DTLB errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-L5.response" -msgstr "The fault manager will attempt to remove all threads associated with\nthis resource from service.\n" -msgid "SUN4V-8000-L5.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-L5.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-MY -# keys: fault.cpu.ultraSPARC-T2.icache -# -msgid "SUN4V-8000-MY.type" -msgstr "Fault" -msgid "SUN4V-8000-MY.severity" -msgstr "Major" -msgid "SUN4V-8000-MY.description" -msgstr "The number of I-cache errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-MY.response" -msgstr "The fault manager will attempt to remove all threads associated with\nthis resource from service.\n" -msgid "SUN4V-8000-MY.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-MY.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-N3 -# keys: fault.cpu.ultraSPARC-T2.dcache -# -msgid "SUN4V-8000-N3.type" -msgstr "Fault" -msgid "SUN4V-8000-N3.severity" -msgstr "Major" -msgid "SUN4V-8000-N3.description" -msgstr "The number of D-cache errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-N3.response" -msgstr "The fault manager will attempt to remove all threads associated with\nthis resource from service.\n" -msgid "SUN4V-8000-N3.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-N3.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-PH -# keys: fault.cpu.ultraSPARC-T2.mau -# -msgid "SUN4V-8000-PH.type" -msgstr "Fault" -msgid "SUN4V-8000-PH.severity" -msgstr "Major" -msgid "SUN4V-8000-PH.description" -msgstr "The number of modular arithmetic unit errors associated with this unit has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-PH.response" -msgstr "Cryptographic software will not use this modular arithmetic unit.\n" -msgid "SUN4V-8000-PH.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-PH.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-QD -# keys: fault.cpu.ultraSPARC-T2.l2data-c -# -msgid "SUN4V-8000-QD.type" -msgstr "Fault" -msgid "SUN4V-8000-QD.severity" -msgstr "Critical" -msgid "SUN4V-8000-QD.description" -msgstr "The number of level 2 cache correctable data errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-QD.response" -msgstr "No automated response.\n" -msgid "SUN4V-8000-QD.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-QD.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-R4 -# keys: fault.cpu.ultraSPARC-T2.l2cachetag -# -msgid "SUN4V-8000-R4.type" -msgstr "Fault" -msgid "SUN4V-8000-R4.severity" -msgstr "Critical" -msgid "SUN4V-8000-R4.description" -msgstr "The number of level 2 cache tag errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-R4.response" -msgstr "No automated response.\n" -msgid "SUN4V-8000-R4.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-R4.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-SR -# keys: fault.cpu.ultraSPARC-T2.l2cachectl -# -msgid "SUN4V-8000-SR.type" -msgstr "Fault" -msgid "SUN4V-8000-SR.severity" -msgstr "Critical" -msgid "SUN4V-8000-SR.description" -msgstr "The number of level 2 cache control errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-SR.response" -msgstr "No automated response.\n" -msgid "SUN4V-8000-SR.impact" -msgstr "System performance is likely to be affected. System may be unstable.\n" -msgid "SUN4V-8000-SR.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-TC -# keys: fault.memory.link-u -# -msgid "SUN4V-8000-TC.type" -msgstr "Fault" -msgid "SUN4V-8000-TC.severity" -msgstr "Critical" -msgid "SUN4V-8000-TC.description" -msgstr "A problem was detected in the interconnect between a memory DIMM module and\nits memory controller. \n Refer to %s for more information." -msgid "SUN4V-8000-TC.response" -msgstr "No automated response.\n" -msgid "SUN4V-8000-TC.impact" -msgstr "System performance may be impacted.\n" -msgid "SUN4V-8000-TC.action" -msgstr "At a convenient time, try reseating the memory module. If the problem persists,\ncontact your hardware support team to schedule part replacement.\n" -# -# code: SUN4V-8000-UQ -# keys: fault.cpu.ultraSPARC-T2.l2data-u -# -msgid "SUN4V-8000-UQ.type" -msgstr "Fault" -msgid "SUN4V-8000-UQ.severity" -msgstr "Critical" -msgid "SUN4V-8000-UQ.description" -msgstr "The number of level 2 cache uncorrectable data errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-UQ.response" -msgstr "No automated response.\n" -msgid "SUN4V-8000-UQ.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-UQ.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-VE -# keys: fault.cpu.ultraSPARC-T1.l2data-c -# -msgid "SUN4V-8000-VE.type" -msgstr "Fault" -msgid "SUN4V-8000-VE.severity" -msgstr "Critical" -msgid "SUN4V-8000-VE.description" -msgstr "The number of level 2 cache correctable data errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-VE.response" -msgstr "No automated response.\n" -msgid "SUN4V-8000-VE.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-VE.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-WJ -# keys: fault.cpu.ultraSPARC-T1.l2data-u -# -msgid "SUN4V-8000-WJ.type" -msgstr "Fault" -msgid "SUN4V-8000-WJ.severity" -msgstr "Critical" -msgid "SUN4V-8000-WJ.description" -msgstr "The number of level 2 cache uncorrectable data errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8000-WJ.response" -msgstr "No automated response.\n" -msgid "SUN4V-8000-WJ.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8000-WJ.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8000-X2 -# keys: fault.memory.datapath -# -msgid "SUN4V-8000-X2.type" -msgstr "Fault" -msgid "SUN4V-8000-X2.severity" -msgstr "Major" -msgid "SUN4V-8000-X2.description" -msgstr "Errors have been detected on multiple memory modules, suggesting that a problem exists somewhere else in the system.\n Refer to %s for more information." -msgid "SUN4V-8000-X2.response" -msgstr "Error reports from the affected components will be logged for examination by your illumos distribution team.\n" -msgid "SUN4V-8000-X2.impact" -msgstr "System performance and stability may be affected. \n" -msgid "SUN4V-8000-X2.action" -msgstr "Contact your service provider for further diagnosis.\n" -# -# code: SUN4V-8000-YX -# keys: fault.io.n2.ncu -# -msgid "SUN4V-8000-YX.type" -msgstr "Fault" -msgid "SUN4V-8000-YX.severity" -msgstr "Critical" -msgid "SUN4V-8000-YX.description" -msgstr "A problem was detected in the NCU subsystem of the N2's SOC\n Refer to %s for more information." -msgid "SUN4V-8000-YX.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4V-8000-YX.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4V-8000-YX.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your hardware support team for support.\n" -# -# code: SUN4V-8001-02 -# keys: fault.io.n2.dmu -# -msgid "SUN4V-8001-02.type" -msgstr "Fault" -msgid "SUN4V-8001-02.severity" -msgstr "Critical" -msgid "SUN4V-8001-02.description" -msgstr "A problem was detected in the DMU subsystem of the N2's SOC\n Refer to %s for more information." -msgid "SUN4V-8001-02.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4V-8001-02.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4V-8001-02.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4V-8001-1X -# keys: fault.io.n2.niu -# -msgid "SUN4V-8001-1X.type" -msgstr "Fault" -msgid "SUN4V-8001-1X.severity" -msgstr "Critical" -msgid "SUN4V-8001-1X.description" -msgstr "A problem was detected in the NIU subsystem of the N2's SOC\n Refer to %s for more information." -msgid "SUN4V-8001-1X.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4V-8001-1X.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4V-8001-1X.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4V-8001-2E -# keys: fault.io.n2.siu -# -msgid "SUN4V-8001-2E.type" -msgstr "Fault" -msgid "SUN4V-8001-2E.severity" -msgstr "Critical" -msgid "SUN4V-8001-2E.description" -msgstr "A problem was detected in the SIU subsystem of the N2's SOC\n Refer to %s for more information." -msgid "SUN4V-8001-2E.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4V-8001-2E.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4V-8001-2E.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4V-8001-3J -# keys: fault.io.n2.soc -# -msgid "SUN4V-8001-3J.type" -msgstr "Fault" -msgid "SUN4V-8001-3J.severity" -msgstr "Critical" -msgid "SUN4V-8001-3J.description" -msgstr "A problem was detected in N2's SOC\n Refer to %s for more information." -msgid "SUN4V-8001-3J.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4V-8001-3J.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4V-8001-3J.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4V-8001-4C -# keys: fault.io.n2.crossbar -# -msgid "SUN4V-8001-4C.type" -msgstr "Fault" -msgid "SUN4V-8001-4C.severity" -msgstr "Critical" -msgid "SUN4V-8001-4C.description" -msgstr "A problem was detected in the crossbar of the N2's SOC\n Refer to %s for more information." -msgid "SUN4V-8001-4C.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4V-8001-4C.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4V-8001-4C.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4V-8001-5Q -# keys: fault.io.fire.fw-epkt fault.io.fire.sw-epkt fault.io.fire.sw-fw-mismatch -# -msgid "SUN4V-8001-5Q.type" -msgstr "Fault" -msgid "SUN4V-8001-5Q.severity" -msgstr "Critical" -msgid "SUN4V-8001-5Q.description" -msgstr "An uncorrectable problem was detected in the IO hostbridge in which a mismatch\nin the SW and FW prevents the error to be properly handled.\n Refer to %s for more information." -msgid "SUN4V-8001-5Q.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4V-8001-5Q.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4V-8001-5Q.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4V-8001-64 -# keys: fault.io.vf.ncx -# -msgid "SUN4V-8001-64.type" -msgstr "Fault" -msgid "SUN4V-8001-64.severity" -msgstr "Critical" -msgid "SUN4V-8001-64.description" -msgstr "An uncorrectable problem was detected in the NCX subsystem.\n Refer to %s for more information." -msgid "SUN4V-8001-64.response" -msgstr "One or more device instances may be disabled\n" -msgid "SUN4V-8001-64.impact" -msgstr "Loss of services provided by the device\ninstances associated with this fault\n" -msgid "SUN4V-8001-64.action" -msgstr "Schedule a repair procedure to replace the affected\ndevice if necessary, or contact your illumos distribution team for support.\n" -# -# code: SUN4V-8001-7R -# keys: fault.memory.link-f -# -msgid "SUN4V-8001-7R.type" -msgstr "Fault" -msgid "SUN4V-8001-7R.severity" -msgstr "Major" -msgid "SUN4V-8001-7R.description" -msgstr "A problem was detected in the interconnect between a memory DIMM module and\nits memory controller. A lane failover has taken place.\n Refer to %s for more information." -msgid "SUN4V-8001-7R.response" -msgstr "No automated response.\n" -msgid "SUN4V-8001-7R.impact" -msgstr "System performance may be impacted.\n" -msgid "SUN4V-8001-7R.action" -msgstr "At a convenient time, try reseating the memory module(s). If the problem persists,\ncontact your hardware support team to schedule part replacement.\n" -# -# code: SUN4V-8001-8H -# keys: fault.cpu.ultraSPARC-T2plus.ireg -# -msgid "SUN4V-8001-8H.type" -msgstr "Fault" -msgid "SUN4V-8001-8H.severity" -msgstr "Minor" -msgid "SUN4V-8001-8H.description" -msgstr "The number of integer register errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-8H.response" -msgstr "The fault manager will attempt to remove the affected thread\nfrom service.\n" -msgid "SUN4V-8001-8H.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8001-8H.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-9D -# keys: fault.cpu.ultraSPARC-T2plus.freg -# -msgid "SUN4V-8001-9D.type" -msgstr "Fault" -msgid "SUN4V-8001-9D.severity" -msgstr "Minor" -msgid "SUN4V-8001-9D.description" -msgstr "The number of floating register errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-9D.response" -msgstr "The fault manager will attempt to remove the affected thread\nfrom service.\n" -msgid "SUN4V-8001-9D.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8001-9D.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-AY -# keys: fault.cpu.ultraSPARC-T2plus.misc_reg -# -msgid "SUN4V-8001-AY.type" -msgstr "Fault" -msgid "SUN4V-8001-AY.severity" -msgstr "Minor" -msgid "SUN4V-8001-AY.description" -msgstr "The number of ancillary register errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-AY.response" -msgstr "The fault manager will attempt to remove the affected thread\nfrom service.\n" -msgid "SUN4V-8001-AY.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8001-AY.action" -msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-C3 -# keys: fault.cpu.ultraSPARC-T2plus.itlb -# -msgid "SUN4V-8001-C3.type" -msgstr "Fault" -msgid "SUN4V-8001-C3.severity" -msgstr "Major" -msgid "SUN4V-8001-C3.description" -msgstr "The number of ITLB errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-C3.response" -msgstr "The fault manager will attempt to remove all threads associated with\nthis resource from service.\n" -msgid "SUN4V-8001-C3.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8001-C3.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-DS -# keys: fault.cpu.ultraSPARC-T2plus.dtlb -# -msgid "SUN4V-8001-DS.type" -msgstr "Fault" -msgid "SUN4V-8001-DS.severity" -msgstr "Major" -msgid "SUN4V-8001-DS.description" -msgstr "The number of DTLB errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-DS.response" -msgstr "The fault manager will attempt to remove all threads associated with\nthis resource from service.\n" -msgid "SUN4V-8001-DS.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8001-DS.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-E5 -# keys: fault.cpu.ultraSPARC-T2plus.icache -# -msgid "SUN4V-8001-E5.type" -msgstr "Fault" -msgid "SUN4V-8001-E5.severity" -msgstr "Major" -msgid "SUN4V-8001-E5.description" -msgstr "The number of I-cache errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-E5.response" -msgstr "The fault manager will attempt to remove all threads associated with\nthis resource from service.\n" -msgid "SUN4V-8001-E5.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8001-E5.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-FP -# keys: fault.cpu.ultraSPARC-T2plus.dcache -# -msgid "SUN4V-8001-FP.type" -msgstr "Fault" -msgid "SUN4V-8001-FP.severity" -msgstr "Major" -msgid "SUN4V-8001-FP.description" -msgstr "The number of D-cache errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-FP.response" -msgstr "The fault manager will attempt to remove all threads associated with\nthis resource from service.\n" -msgid "SUN4V-8001-FP.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8001-FP.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-GA -# keys: fault.cpu.ultraSPARC-T2plus.mau -# -msgid "SUN4V-8001-GA.type" -msgstr "Fault" -msgid "SUN4V-8001-GA.severity" -msgstr "Major" -msgid "SUN4V-8001-GA.description" -msgstr "The number of modular arithmetic unit errors associated with this thread has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-GA.response" -msgstr "Cryptographic software will not use this modular arithmetic unit.\n\n" -msgid "SUN4V-8001-GA.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8001-GA.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-HJ -# keys: fault.cpu.ultraSPARC-T2plus.l2data-c -# -msgid "SUN4V-8001-HJ.type" -msgstr "Fault" -msgid "SUN4V-8001-HJ.severity" -msgstr "Critical" -msgid "SUN4V-8001-HJ.description" -msgstr "The number of level 2 cache correctable data errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-HJ.response" -msgstr "No automated response.\n" -msgid "SUN4V-8001-HJ.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8001-HJ.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-JE -# keys: fault.cpu.ultraSPARC-T2plus.l2cachetag -# -msgid "SUN4V-8001-JE.type" -msgstr "Fault" -msgid "SUN4V-8001-JE.severity" -msgstr "Critical" -msgid "SUN4V-8001-JE.description" -msgstr "The number of level 2 cache tag errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-JE.response" -msgstr "No automated response.\n" -msgid "SUN4V-8001-JE.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8001-JE.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-KX -# keys: fault.cpu.ultraSPARC-T2plus.l2cachectl -# -msgid "SUN4V-8001-KX.type" -msgstr "Fault" -msgid "SUN4V-8001-KX.severity" -msgstr "Critical" -msgid "SUN4V-8001-KX.description" -msgstr "The number of level 2 cache control errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-KX.response" -msgstr "No automated response.\n" -msgid "SUN4V-8001-KX.impact" -msgstr "System performance is likely to be affected. System may be unstable.\n" -msgid "SUN4V-8001-KX.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-L2 -# keys: fault.cpu.ultraSPARC-T2plus.l2data-u -# -msgid "SUN4V-8001-L2.type" -msgstr "Fault" -msgid "SUN4V-8001-L2.severity" -msgstr "Critical" -msgid "SUN4V-8001-L2.description" -msgstr "The number of level 2 cache uncorrectable data errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-L2.response" -msgstr "No automated response.\n" -msgid "SUN4V-8001-L2.impact" -msgstr "System performance is likely to be affected. \n" -msgid "SUN4V-8001-L2.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-MR -# keys: fault.cpu.ultraSPARC-T2plus.lfu-f -# -msgid "SUN4V-8001-MR.type" -msgstr "Fault" -msgid "SUN4V-8001-MR.severity" -msgstr "Major" -msgid "SUN4V-8001-MR.description" -msgstr "A CPU chip's Link Framing Unit has stopped using a bad lane.\n Refer to %s for more information." -msgid "SUN4V-8001-MR.response" -msgstr "No other automated response.\n" -msgid "SUN4V-8001-MR.impact" -msgstr "The system's capacity to correct transmission errors between CPU chips has been reduced.\n" -msgid "SUN4V-8001-MR.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-N4 -# keys: fault.cpu.ultraSPARC-T2plus.lfu-p -# -msgid "SUN4V-8001-N4.type" -msgstr "Fault" -msgid "SUN4V-8001-N4.severity" -msgstr "Major" -msgid "SUN4V-8001-N4.description" -msgstr "A CPU chip's Link Framing Unit has encountered a protocol error.\n Refer to %s for more information." -msgid "SUN4V-8001-N4.response" -msgstr "No automated response.\n" -msgid "SUN4V-8001-N4.impact" -msgstr "The system has most likely taken a fatal reset.\n" -msgid "SUN4V-8001-N4.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-PQ -# keys: fault.cpu.ultraSPARC-T2plus.lfu-u -# -msgid "SUN4V-8001-PQ.type" -msgstr "Fault" -msgid "SUN4V-8001-PQ.severity" -msgstr "Major" -msgid "SUN4V-8001-PQ.description" -msgstr "A CPU chip's Link Framing Unit has encountered an unrecoverable lane failure.\n Refer to %s for more information." -msgid "SUN4V-8001-PQ.response" -msgstr "No automated response.\n" -msgid "SUN4V-8001-PQ.impact" -msgstr "The system's integrity is seriously compromised.\n" -msgid "SUN4V-8001-PQ.action" -msgstr "Do not rely on this system for mission-critical tasks.\nSchedule a repair procedure to replace the affected resource, the identity of which can be determined using fmdump -v -u .\n" -# -# code: SUN4V-8001-QC -# keys: fault.asic.ultraSPARC-T2plus.interconnect.opu-u -# -msgid "SUN4V-8001-QC.type" -msgstr "Fault" -msgid "SUN4V-8001-QC.severity" -msgstr "Critical" -msgid "SUN4V-8001-QC.description" -msgstr "The ultraSPARC-T2plus Coherency Interconnect has detected a fatal\ninternal problem.\n Refer to %s for more information." -msgid "SUN4V-8001-QC.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-QC.impact" -msgstr "The system's integrity is compromised.\n" -msgid "SUN4V-8001-QC.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8001-R3 -# keys: fault.asic.ultraSPARC-T2plus.interconnect.opu-c -# -msgid "SUN4V-8001-R3.type" -msgstr "Fault" -msgid "SUN4V-8001-R3.severity" -msgstr "Major" -msgid "SUN4V-8001-R3.description" -msgstr "The ultraSPARC-T2plus Coherency Interconnect has detected an internal problem.\n Refer to %s for more information." -msgid "SUN4V-8001-R3.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-R3.impact" -msgstr "The system's integrity is compromised.\n" -msgid "SUN4V-8001-R3.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8001-SY -# keys: fault.cpu.ultraSPARC-T2plus.chip -# -msgid "SUN4V-8001-SY.type" -msgstr "Fault" -msgid "SUN4V-8001-SY.severity" -msgstr "Critical" -msgid "SUN4V-8001-SY.description" -msgstr "An ultraSPARC-T2plus Interconnect has detected a fatal communication\nproblem with a CPU.\n Refer to %s for more information." -msgid "SUN4V-8001-SY.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-SY.impact" -msgstr "The system's integrity is seriously compromised.\n" -msgid "SUN4V-8001-SY.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8001-TD -# keys: fault.asic.ultraSPARC-T2plus.interconnect.lfu-c fault.cpu.ultraSPARC-T2plus.chip -# -msgid "SUN4V-8001-TD.type" -msgstr "Fault" -msgid "SUN4V-8001-TD.severity" -msgstr "Minor" -msgid "SUN4V-8001-TD.description" -msgstr "The number of CRC errors between an ultraSPARC-T2plus\nCoherency Interconnect and a CPU has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8001-TD.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-TD.impact" -msgstr "The system's integrity is seriously compromised.\n" -msgid "SUN4V-8001-TD.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8001-UH -# keys: fault.asic.ultraSPARC-T2plus.interconnect.lfu-f fault.cpu.ultraSPARC-T2plus.chip -# -msgid "SUN4V-8001-UH.type" -msgstr "Fault" -msgid "SUN4V-8001-UH.severity" -msgstr "Major" -msgid "SUN4V-8001-UH.description" -msgstr "An ultraSPARC-T2plus Coherency Interconnect has detected a single-lane\nfailure communicating with a CPU.\n Refer to %s for more information." -msgid "SUN4V-8001-UH.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-UH.impact" -msgstr "The system's performance may be impacted.\n" -msgid "SUN4V-8001-UH.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8001-VA -# keys: fault.asic.ultraSPARC-T2plus.interconnect.lfu-u fault.cpu.ultraSPARC-T2plus.chip -# -msgid "SUN4V-8001-VA.type" -msgstr "Fault" -msgid "SUN4V-8001-VA.severity" -msgstr "Critical" -msgid "SUN4V-8001-VA.description" -msgstr "An ultraSPARC-T2plus Coherency Interconnect has detected a fatal\nfault commnicating with a CPU.\n Refer to %s for more information." -msgid "SUN4V-8001-VA.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-VA.impact" -msgstr "The system's integrity is seriously compromised.\n" -msgid "SUN4V-8001-VA.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8001-WP -# keys: fault.asic.ultraSPARC-T2plus.interconnect.lfu-u -# -msgid "SUN4V-8001-WP.type" -msgstr "Fault" -msgid "SUN4V-8001-WP.severity" -msgstr "Critical" -msgid "SUN4V-8001-WP.description" -msgstr "An ultraSPARC-T2plus Coherency Interconnect has detected a fatal internal\nfault and has automatically reset.\n Refer to %s for more information." -msgid "SUN4V-8001-WP.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-WP.impact" -msgstr "The system's integrity is seriously compromised.\n" -msgid "SUN4V-8001-WP.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8001-X5 -# keys: fault.asic.ultraSPARC-T2plus.interconnect.gpd-u fault.cpu.ultraSPARC-T2plus.chip -# -msgid "SUN4V-8001-X5.type" -msgstr "Fault" -msgid "SUN4V-8001-X5.severity" -msgstr "Critical" -msgid "SUN4V-8001-X5.description" -msgstr "An ultraSPARC-T2plus Coherency Interconnect has detected a fatal communication\nfault with a CPU.\n Refer to %s for more information." -msgid "SUN4V-8001-X5.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-X5.impact" -msgstr "The system's performance may be compromised.\n" -msgid "SUN4V-8001-X5.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8001-YS -# keys: fault.asic.ultraSPARC-T2plus.interconnect.gpd-c fault.cpu.ultraSPARC-T2plus.chip -# -msgid "SUN4V-8001-YS.type" -msgstr "Fault" -msgid "SUN4V-8001-YS.severity" -msgstr "Major" -msgid "SUN4V-8001-YS.description" -msgstr "An ultraSPARC-T2plus Coherency Interconnect has detected a fault\ncommunicating with a CPU.\n Refer to %s for more information." -msgid "SUN4V-8001-YS.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8001-YS.impact" -msgstr "The system's integrity may be seriously compromised.\n" -msgid "SUN4V-8001-YS.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8002-0C -# keys: fault.asic.ultraSPARC-T2plus.interconnect.gpd-c -# -msgid "SUN4V-8002-0C.type" -msgstr "Fault" -msgid "SUN4V-8002-0C.severity" -msgstr "Major" -msgid "SUN4V-8002-0C.description" -msgstr "The ultraSPARC-T2plus Interconnect has detected a fault communicating\nwith the service processor.\n Refer to %s for more information." -msgid "SUN4V-8002-0C.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8002-0C.impact" -msgstr "The system's performance may be impacted.\n" -msgid "SUN4V-8002-0C.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8002-1Q -# keys: fault.asic.fpga fault.asic.ultraSPARC-T2plus.interconnect.gpd-c -# -msgid "SUN4V-8002-1Q.type" -msgstr "Fault" -msgid "SUN4V-8002-1Q.severity" -msgstr "Major" -msgid "SUN4V-8002-1Q.description" -msgstr "ultraSPARC-T2plus Coherency Interconnect detected a fault on the LPC bus.\n Refer to %s for more information." -msgid "SUN4V-8002-1Q.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8002-1Q.impact" -msgstr "The system's performance may be impacted.\n" -msgid "SUN4V-8002-1Q.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8002-24 -# keys: fault.asic.ultraSPARC-T2plus.interconnect.asu -# -msgid "SUN4V-8002-24.type" -msgstr "Fault" -msgid "SUN4V-8002-24.severity" -msgstr "Critical" -msgid "SUN4V-8002-24.description" -msgstr "An ultraSPARC-T2plus Coherency Interconnect has detected a fatal fault.\n Refer to %s for more information." -msgid "SUN4V-8002-24.response" -msgstr "No automated reponse.\n" -msgid "SUN4V-8002-24.impact" -msgstr "The system's integrity is seriously compromised.\n" -msgid "SUN4V-8002-24.action" -msgstr "Schedule a repair procedure to replace the affected component, the identity\nof which can be determined by using fmdump -v -u .\n" -# -# code: SUN4V-8002-3R -# keys: fault.memory.dimm-page-retires-excessive -# -msgid "SUN4V-8002-3R.type" -msgstr "Fault" -msgid "SUN4V-8002-3R.severity" -msgstr "Major" -msgid "SUN4V-8002-3R.description" -msgstr "The number of correctable errors associated with this memory module has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-3R.response" -msgstr "Pages of memory associated with this memory module have been removed from service, up to a limit which has now been reached.\n" -msgid "SUN4V-8002-3R.impact" -msgstr "Total system memory capacity has been reduced.\n" -msgid "SUN4V-8002-3R.action" -msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n" -# -# code: SUN4V-8002-42 -# keys: fault.memory.dimm-ue-imminent -# -msgid "SUN4V-8002-42.type" -msgstr "Fault" -msgid "SUN4V-8002-42.severity" -msgstr "Critical" -msgid "SUN4V-8002-42.description" -msgstr "A pattern of correctable errors has been observed suggesting the potential exists that an uncorrectable error may occur.\n Refer to %s for more information." -msgid "SUN4V-8002-42.response" -msgstr "None at this time.\n" -msgid "SUN4V-8002-42.impact" -msgstr "None at this time. However, the potential uncorrectable error warrants proactive service action to avoid any unplanned system outages.\n" -msgid "SUN4V-8002-42.action" -msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n" -# -# code: SUN4V-8002-5X -# keys: fault.memory.dram-ue-imminent -# -msgid "SUN4V-8002-5X.type" -msgstr "Fault" -msgid "SUN4V-8002-5X.severity" -msgstr "Critical" -msgid "SUN4V-8002-5X.description" -msgstr "A pattern of correctable errors has been observed suggesting the potential exists that an uncorrectable error may occur.\n Refer to %s for more information." -msgid "SUN4V-8002-5X.response" -msgstr "None at this time.\n" -msgid "SUN4V-8002-5X.impact" -msgstr "None at this time. However, the potential uncorrectable error warrants proactive service action to avoid any unplanned system outages.\n" -msgid "SUN4V-8002-5X.action" -msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n" -# -# code: SUN4V-8002-6E -# keys: fault.cpu.generic-sparc.strand -# -msgid "SUN4V-8002-6E.type" -msgstr "Fault" -msgid "SUN4V-8002-6E.severity" -msgstr "Major" -msgid "SUN4V-8002-6E.description" -msgstr "The number of correctable errors associated with this strand has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-6E.response" -msgstr "The fault manager will attempt to remove the affected strand\nfrom service.\n" -msgid "SUN4V-8002-6E.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-6E.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-7J -# keys: fault.cpu.generic-sparc.strand-nr -# -msgid "SUN4V-8002-7J.type" -msgstr "Fault" -msgid "SUN4V-8002-7J.severity" -msgstr "Major" -msgid "SUN4V-8002-7J.description" -msgstr "The number of correctable errors in internal memory associated with this strand have exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-7J.response" -msgstr "The system may attempt to avoid using internal memory associated with this\nstrand.\n" -msgid "SUN4V-8002-7J.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-7J.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-8S -# keys: fault.cpu.generic-sparc.strand-uc -# -msgid "SUN4V-8002-8S.type" -msgstr "Fault" -msgid "SUN4V-8002-8S.severity" -msgstr "Critical" -msgid "SUN4V-8002-8S.description" -msgstr "This strand has encountered an uncorrectable error.\n Refer to %s for more information." -msgid "SUN4V-8002-8S.response" -msgstr "The fault manager will attempt to remove the affected strand\nfrom service.\n" -msgid "SUN4V-8002-8S.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-8S.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-95 -# keys: fault.cpu.generic-sparc.strand-uc-nr -# -msgid "SUN4V-8002-95.type" -msgstr "Fault" -msgid "SUN4V-8002-95.severity" -msgstr "Critical" -msgid "SUN4V-8002-95.description" -msgstr "Internal memory associated with this strand has encountered an uncorrectable error.\n Refer to %s for more information." -msgid "SUN4V-8002-95.response" -msgstr "The system may attempt to avoid using internal memory associated with\nthis strand.\n" -msgid "SUN4V-8002-95.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-95.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-AP -# keys: fault.cpu.generic-sparc.core -# -msgid "SUN4V-8002-AP.type" -msgstr "Fault" -msgid "SUN4V-8002-AP.severity" -msgstr "Major" -msgid "SUN4V-8002-AP.description" -msgstr "The number of correctable errors associated with this core has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-AP.response" -msgstr "The fault manager will attempt to remove all strands associated with\nthis resource from service.\n" -msgid "SUN4V-8002-AP.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-AP.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-CA -# keys: fault.cpu.generic-sparc.core-nr -# -msgid "SUN4V-8002-CA.type" -msgstr "Fault" -msgid "SUN4V-8002-CA.severity" -msgstr "Major" -msgid "SUN4V-8002-CA.description" -msgstr "The number of correctable errors in internal memory associated with this core have exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-CA.response" -msgstr "The system may attempt to avoid using internal memory associated with this\ncore.\n" -msgid "SUN4V-8002-CA.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-CA.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-DH -# keys: fault.cpu.generic-sparc.core-uc -# -msgid "SUN4V-8002-DH.type" -msgstr "Fault" -msgid "SUN4V-8002-DH.severity" -msgstr "Critical" -msgid "SUN4V-8002-DH.description" -msgstr "This core has encountered an uncorrectable error.\n Refer to %s for more information." -msgid "SUN4V-8002-DH.response" -msgstr "The fault manager will attempt to remove all strands associated with\nthis resource from service.\n" -msgid "SUN4V-8002-DH.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-DH.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-ED -# keys: fault.cpu.generic-sparc.core-uc-nr -# -msgid "SUN4V-8002-ED.type" -msgstr "Fault" -msgid "SUN4V-8002-ED.severity" -msgstr "Critical" -msgid "SUN4V-8002-ED.description" -msgstr "An uncorrectable error has occurred in internal memory associated with this core.\n Refer to %s for more information." -msgid "SUN4V-8002-ED.response" -msgstr "The system may attempt to avoid using internal memory associated with this\ncore.\n" -msgid "SUN4V-8002-ED.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-ED.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-FY -# keys: fault.cpu.generic-sparc.chip -# -msgid "SUN4V-8002-FY.type" -msgstr "Fault" -msgid "SUN4V-8002-FY.severity" -msgstr "Critical" -msgid "SUN4V-8002-FY.description" -msgstr "The number of chip-level correctable errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-FY.response" -msgstr "No automated response.\n" -msgid "SUN4V-8002-FY.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-FY.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-G3 -# keys: fault.cpu.generic-sparc.chip-nr -# -msgid "SUN4V-8002-G3.type" -msgstr "Fault" -msgid "SUN4V-8002-G3.severity" -msgstr "Critical" -msgid "SUN4V-8002-G3.description" -msgstr "The number of correctable errors in internal memory associated with this chip have exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-G3.response" -msgstr "The system may attempt to avoid using internal memory associated with this\nchip.\n" -msgid "SUN4V-8002-G3.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-G3.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-HR -# keys: fault.cpu.generic-sparc.chip-uc -# -msgid "SUN4V-8002-HR.type" -msgstr "Fault" -msgid "SUN4V-8002-HR.severity" -msgstr "Critical" -msgid "SUN4V-8002-HR.description" -msgstr "This chip has encountered a chip-level uncorrectable error.\n Refer to %s for more information." -msgid "SUN4V-8002-HR.response" -msgstr "The system will attempt to retire all strands in this chip.\n" -msgid "SUN4V-8002-HR.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-HR.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-J4 -# keys: fault.cpu.generic-sparc.chip-uc-nr -# -msgid "SUN4V-8002-J4.type" -msgstr "Fault" -msgid "SUN4V-8002-J4.severity" -msgstr "Critical" -msgid "SUN4V-8002-J4.description" -msgstr "Internal memory associated with this chip has encountered an uncorrectable\nerror.\n Refer to %s for more information." -msgid "SUN4V-8002-J4.response" -msgstr "The system may attempt to avoid using internal memory associated with this\nchip.\n" -msgid "SUN4V-8002-J4.impact" -msgstr "System performance may be affected. \n" -msgid "SUN4V-8002-J4.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-KQ -# keys: fault.cpu.generic-sparc.c2c -# -msgid "SUN4V-8002-KQ.type" -msgstr "Fault" -msgid "SUN4V-8002-KQ.severity" -msgstr "Major" -msgid "SUN4V-8002-KQ.description" -msgstr "The number of chip-to-chip recoverable errors has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-KQ.response" -msgstr "No automated response.\n" -msgid "SUN4V-8002-KQ.impact" -msgstr "System performance may be affected.\n" -msgid "SUN4V-8002-KQ.action" -msgstr "Schedule a repair procedure to replace the affected resource(s), the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-LC -# keys: fault.cpu.generic-sparc.c2c-failover -# -msgid "SUN4V-8002-LC.type" -msgstr "Fault" -msgid "SUN4V-8002-LC.severity" -msgstr "Major" -msgid "SUN4V-8002-LC.description" -msgstr "A CRC error has occurred in the interconnect between two CPU chips.\nWhile no data has been lost, a lane failover has taken place.\n Refer to %s for more information." -msgid "SUN4V-8002-LC.response" -msgstr "The hardware has automatically reconfigured the link to isolate the\nfailing lane, and successful retransmission of the data has occurred.\n" -msgid "SUN4V-8002-LC.impact" -msgstr "The system's capacity to correct transmission errors between CPU chips\nhas been reduced.\n" -msgid "SUN4V-8002-LC.action" -msgstr "Schedule a repair procedure to replace the affected resource(s), the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-MJ -# keys: fault.cpu.generic-sparc.c2c-uc -# -msgid "SUN4V-8002-MJ.type" -msgstr "Fault" -msgid "SUN4V-8002-MJ.severity" -msgstr "Critical" -msgid "SUN4V-8002-MJ.description" -msgstr "A chip-to-chip unrecoverable CRC error has occurred.\n Refer to %s for more information." -msgid "SUN4V-8002-MJ.response" -msgstr "The system has halted in order to prevent corruption of data.\nNo further automated response.\n" -msgid "SUN4V-8002-MJ.impact" -msgstr "The system halts and must be restarted. The integrity of this system has\nbeen compromised.\n" -msgid "SUN4V-8002-MJ.action" -msgstr "Schedule a repair procedure to replace the affected resource(s), the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-NE -# keys: fault.memory.memlink -# -msgid "SUN4V-8002-NE.type" -msgstr "Fault" -msgid "SUN4V-8002-NE.severity" -msgstr "Major" -msgid "SUN4V-8002-NE.description" -msgstr "Recoverable CRC errors have occurred in the interconnect between a\nmemory buffer and its memory controller. No data has been lost;\nhowever, the number of CRC errors associated with this memory buffer-controller\npair has exceeded acceptable levels.\n Refer to %s for more information." -msgid "SUN4V-8002-NE.response" -msgstr "The system has recovered from the CRC errors.\n" -msgid "SUN4V-8002-NE.impact" -msgstr "System performance may be impacted by a slight reduction in effective\nmemory bandwidth.\n" -msgid "SUN4V-8002-NE.action" -msgstr "At a convenient time, schedule a repair procedure to replace the affected resource(s), the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-PX -# keys: fault.memory.memlink-failover -# -msgid "SUN4V-8002-PX.type" -msgstr "Fault" -msgid "SUN4V-8002-PX.severity" -msgstr "Major" -msgid "SUN4V-8002-PX.description" -msgstr "A CRC error has occurred in the interconnect between a memory buffer and\nits memory controller. While no data has been lost, a lane failover\nhas taken place.\n Refer to %s for more information." -msgid "SUN4V-8002-PX.response" -msgstr "The hardware has automatically reconfigured the link to isolate the\nfailing lane, and successful retransmission of the data has occurred.\n" -msgid "SUN4V-8002-PX.impact" -msgstr "The system's capacity to correct transmission errors between the memory\nDIMM and its memory controller has been reduced.\n" -msgid "SUN4V-8002-PX.action" -msgstr "At your earliest convenience, schedule a repair procedure to replace the\naffected resource(s), the identity of which can be determined using\n'fmadm faulty'.\n" -# -# code: SUN4V-8002-Q2 -# keys: fault.memory.memlink-uc -# -msgid "SUN4V-8002-Q2.type" -msgstr "Fault" -msgid "SUN4V-8002-Q2.severity" -msgstr "Critical" -msgid "SUN4V-8002-Q2.description" -msgstr "A problem was detected in the interconnect between a memory buffer\nand its memory controller.\n Refer to %s for more information." -msgid "SUN4V-8002-Q2.response" -msgstr "The system crashed to prevent data corruption. Memory in the affected\npartition may have been deconfigured. (Consult system-specific\ndocumentation to find out how to determine if memory has been\ndeconfigured.)\n" -msgid "SUN4V-8002-Q2.impact" -msgstr "If memory has been deconfigured, system performance may be impacted. \n" -msgid "SUN4V-8002-Q2.action" -msgstr "Schedule a repair procedure to replace the appropriate part(s), the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-RA -# keys: defect.fw.generic-sparc.addr-oob -# -msgid "SUN4V-8002-RA.type" -msgstr "Fault" -msgid "SUN4V-8002-RA.severity" -msgstr "Critical" -msgid "SUN4V-8002-RA.description" -msgstr "An address-out-of-bounds error has occurred.\n Refer to %s for more information." -msgid "SUN4V-8002-RA.response" -msgstr "No automated response.\n" -msgid "SUN4V-8002-RA.impact" -msgstr "The system may have taken a fatal reset.\n" -msgid "SUN4V-8002-RA.action" -msgstr "Call your service provider to determine if your system requires a firmware upgrade.\n" -# -# code: SUN4V-8002-SP -# keys: defect.fw.generic-sparc.erpt-gen -# -msgid "SUN4V-8002-SP.type" -msgstr "Fault" -msgid "SUN4V-8002-SP.severity" -msgstr "Major" -msgid "SUN4V-8002-SP.description" -msgstr "The error report generator has received input data that is inconsistent or\nimproperly formatted.\n Refer to %s for more information." -msgid "SUN4V-8002-SP.response" -msgstr "No automated response.\n" -msgid "SUN4V-8002-SP.impact" -msgstr "This error does not affect system operation. The error which\ncould not be reported may have more serious impact which cannot be determined.\n" -msgid "SUN4V-8002-SP.action" -msgstr "Call your service provider to determine if your system requires a firmware\nupgrade. Please retain the error log file.\n" -# -# code: SUN4V-8002-T5 -# keys: fault.cpu.generic-sparc.bootbus -# -msgid "SUN4V-8002-T5.type" -msgstr "Fault" -msgid "SUN4V-8002-T5.severity" -msgstr "Critical" -msgid "SUN4V-8002-T5.description" -msgstr "A system boot bus error has occurred.\n Refer to %s for more information." -msgid "SUN4V-8002-T5.response" -msgstr "No automated response.\n" -msgid "SUN4V-8002-T5.impact" -msgstr "The system's integrity is seriously compromised. Processor chip(s)\nmay be unavailable.\n" -msgid "SUN4V-8002-T5.action" -msgstr "Schedule a repair procedure to replace the affected resource, the identity of which can be determined using 'fmadm faulty'.\n" -# -# code: SUN4V-8002-US -# keys: fault.sp.failed -# -msgid "SUN4V-8002-US.type" -msgstr "Fault" -msgid "SUN4V-8002-US.severity" -msgstr "Critical" -msgid "SUN4V-8002-US.description" -msgstr "The Service Processor failed.\n Refer to %s for more information." -msgid "SUN4V-8002-US.response" -msgstr "No automated response.\n" -msgid "SUN4V-8002-US.impact" -msgstr "Some services such as Fault Diagnosis may be degraded as a result.\n" -msgid "SUN4V-8002-US.action" -msgstr "Schedule a repair procedure for the Service Processor, or contact your illumos distribution team for support.\n" diff --git a/usr/src/cmd/fm/eversholt/eftinfo/sparc/Makefile b/usr/src/cmd/fm/eversholt/eftinfo/sparc/Makefile deleted file mode 100644 index 617fb6a35b..0000000000 --- a/usr/src/cmd/fm/eversholt/eftinfo/sparc/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2004 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/eversholt/esc/sparc/Makefile b/usr/src/cmd/fm/eversholt/esc/sparc/Makefile deleted file mode 100644 index 617fb6a35b..0000000000 --- a/usr/src/cmd/fm/eversholt/esc/sparc/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2004 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/eversholt/files/Makefile b/usr/src/cmd/fm/eversholt/files/Makefile index 9e178bfddc..91757a6a67 100644 --- a/usr/src/cmd/fm/eversholt/files/Makefile +++ b/usr/src/cmd/fm/eversholt/files/Makefile @@ -23,7 +23,6 @@ # Copyright 2004 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # -#ident "%Z%%M% %I% %E% SMI" SUBDIRS=$(MACH) diff --git a/usr/src/cmd/fm/eversholt/files/sparc/Makefile b/usr/src/cmd/fm/eversholt/files/sparc/Makefile deleted file mode 100644 index 0482b12b33..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/Makefile +++ /dev/null @@ -1,42 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright (c) 2004, 2010, Oracle and/or its affiliates. All rights reserved. -# Copyright 2019 Peter Tribble. -# - -SUBDIRS=sun4u sun4v -EFT_COMMON_FILES= \ - disk.eft \ - neptune_xaui.eft \ - neptune_xfp.eft \ - pci.eft \ - pciex.eft \ - pciexrc.eft \ - sca500.eft \ - sca1000.eft \ - sensor.eft \ - storage.eft \ - nic.eft - -include ../../../Makefile.subdirs - -include ../Makefile.com diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4/Makefile.sun4 b/usr/src/cmd/fm/eversholt/files/sparc/sun4/Makefile.sun4 deleted file mode 100644 index b8da67e8d0..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4/Makefile.sun4 +++ /dev/null @@ -1,36 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2005 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -ESC=$(SRC)/cmd/fm/eversholt/esc/$(MACH)/esc - -SUN4DIR= ../sun4 - -SUN4EFTFILES= fire.eft - -%.eft: $(SUN4DIR)/%.esc - $(ESC) -o $@ $< - diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4/fire.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4/fire.esc deleted file mode 100644 index ce5e9b1755..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4/fire.esc +++ /dev/null @@ -1,672 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2009 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma dictionary "SUN4" - -/* - * Eversholt rules for the Fire nexus driver - */ - -#define SW_FIT 5000 /* No real fit rate, SW */ -#define HV_FIT 5000 /* No real fit rate, SW */ -#define SW_HV_MISMATCH_FIT 20000 /* No real fit rate, SW */ -#define HB_FIT 400 -#define HBUS_FIT 400 -#define CPU_FIT 500 -#define PCI_DEV_FIT 1000 -#define PCIEX_DEV_FIT 1000 -#define EBUS_FIT 1000 -#define LINK_EVENTS_COUNT 10 -#define LINK_EVENTS_TIME 1h -#define CE_EVENTS_COUNT 10 -#define CE_EVENTS_TIME 1h - -/* - * Macros for CE Fabric ereports - * - * The current kernel sends ereports with a severity of PF_CE and PF_NO_ERROR. - * However, a simple change in the kernel may end up sending only a severity - * of PF_CE for CE errors. Since both methods are correct, we match on - * an ereport severity of either PF_CE only or PF_CE plus PF_NO_ERROR. - */ -#define PF_NO_ERROR (1 << 0) -#define PF_CE (1 << 1) -#define MATCH_CE ((payloadprop("severity") == PF_CE) || \ - (payloadprop("severity") == (PF_CE | PF_NO_ERROR))) - - -#define MATCH_UNRECOGNIZED ((payloadprop("sysino") == 0) && \ - (payloadprop("ehdl") == 0) && \ - (payloadprop("stick") == 0)) - -/* - * Test for primary or secondary ereports - */ -#define IS_PRIMARY (payloadprop("primary")) -#define IS_SECONDARY (! payloadprop("primary")) - -/* - * payload: imu-rds - * - * Extract the request id, the BDF, value in the IMU RDS log register - * Example: - * 0x7766554433221100 - * ^^^^ - */ -#define IMU_MATCH_BDF(b, d, f) \ - ( IS_PRIMARY && ((payloadprop("imu-rds") >> 32) & 0xFFFF) == \ - ((b << 8) | (d << 3) | f)) - -/*************** - * JBC ereports - ***************/ -event ereport.io.fire.jbc.ape@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.bjc@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ce_asyn@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.cpe@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ebus_to@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ebus_to@hostbridge{within(5s)}; -event ereport.io.fire.jbc.icise@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ijp@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ill_acc@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ill_acc_rd@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ill_bmr@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ill_bmw@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.jbe@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.jtceei@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.jtceer@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.jtceew@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.jte@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.jue@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.mb_pea@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.mb_per@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.mb_pew@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.pio_cpe@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.pio_dpe@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.pio_unmap@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.pio_unmap_rd@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.rd_dpe@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.ue_asyn@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.unsol_intr@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.unsol_rd@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.jbc.wr_dpe@hostbridge/pciexrc{within(5s)}; - -/*************** - * DMC ereports - ***************/ -event ereport.io.fire.dmc.cor_not_en@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.eq_not_en@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.eq_over@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.fatal_not_en@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.msi_mal_err@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.msi_not_en@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.msi_par_err@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.nonfatal_not_en@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.pmeack_not_en@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.pmpme_not_en@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.tbw_dme@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.tbw_dpe@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.tbw_err@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.tbw_ude@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.trn_err@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.ttc_cae@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.dmc.ttc_dpe@hostbridge/pciexrc{within(5s)}; - -/*************** - * TLU Other Event ereports - ***************/ -event ereport.io.fire.pec.crs@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.edp@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.ehp@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.eip@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.erp@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.ihb_pe@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.iip@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.ldn@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.lin@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.lrs@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.lup@hostbridge/pciexrc{within(5s)}; -event ereport.io.fire.pec.mrc@hostbridge/pciexrc{within(5s)}; - -/*************** - * Fire Fabric ereport - * ------------- - * Whenever a leaf device sends an error message (fatal, non-fatal, or CE) to - * root complex, the nexus driver publishes this ereport to log the ereport. - ***************/ -event ereport.io.fire.fabric@pciexbus/pciexdev/pciexfn {within(1s)}; -event ereport.io.fire.fabric@pcibus/pcidev/pcifn {within(1s)}; -event error.io.fire.fabric-sib@hostbridge/pciexrc; -event error.io.fire.fabric@pciexbus/pciexdev/pciexfn; -event error.io.fire.fabric@pcibus/pcidev/pcifn; - -/*************** - * sun4v unknown error packets - * ------------- - * In a sun4v system, if HV sends an epkt to the guest the following wrong - * things can happen. - * o HV sends malformed epkt - * o Guest has coding error and doesn't understand epkt - * o HV and Guest are out of sync. - ***************/ -event ereport.io.fire.epkt@hostbridge/pciexrc {within(5s)}; -event ereport.io.fire.epkt@hostbridge {within(5s)}; - -/****************************** - * Generic Rules Begin Here * - ******************************/ - -/*************** - * Fire Asic HW error - * ------------- - * Errors caused by parity or unexpected behaviors in the asic. - ***************/ -fru hostbridge/pciexrc; -asru hostbridge/pciexrc; -event fault.io.fire.asic@hostbridge/pciexrc, - FITrate=HB_FIT, - ASRU=hostbridge/pciexrc, - FRU=hostbridge/pciexrc; - -event error.io.fire.jbc.asic@hostbridge/pciexrc; -event error.io.fire.dmc.asic@hostbridge/pciexrc; -event error.io.fire.pec.asic@hostbridge/pciexrc; - -prop fault.io.fire.asic@hostbridge/pciexrc (0)-> - error.io.fire.jbc.asic@hostbridge/pciexrc, - error.io.fire.dmc.asic@hostbridge/pciexrc, - error.io.fire.pec.asic@hostbridge/pciexrc; - -/*************** - * Fire PX SW/HV error - * ------------- - * Errors caused by bad SW or HV - ***************/ -event fault.io.fire.sw-epkt@hostbridge/pciexrc, retire=0, response=0, - FITrate=SW_FIT; -event fault.io.fire.fw-epkt@hostbridge/pciexrc, retire=0, response=0, - FITrate=HV_FIT; -event fault.io.fire.sw-fw-mismatch@hostbridge/pciexrc, retire=0, response=0, - FITrate=SW_HV_MISMATCH_FIT; -event fault.io.fire.sw-epkt@hostbridge, retire=0, response=0, - FITrate=SW_FIT; -event fault.io.fire.fw-epkt@hostbridge, retire=0, response=0, - FITrate=HV_FIT; -event fault.io.fire.sw-fw-mismatch@hostbridge, retire=0, response=0, - FITrate=SW_HV_MISMATCH_FIT; -event fault.io.fire.hb.sw-config@hostbridge/pciexrc, retire=0, response=0, - FITrate=SW_FIT; -event fault.io.fire.dmc.sw-algorithm@hostbridge/pciexrc, retire=0, response=0, - FITrate=SW_FIT; -event fault.io.fire.dmc.sw-state@hostbridge/pciexrc, retire=0, response=0, - FITrate=SW_FIT; -event fault.io.fire.pec.sw-algorithm@hostbridge/pciexrc, retire=0, response=0, - FITrate=SW_FIT; - -event error.io.fire.jbc.driver@hostbridge/pciexrc; -event error.io.fire.dmc.driver@hostbridge/pciexrc; -event error.io.fire.dmc.bad_state@hostbridge/pciexrc; - -prop fault.io.fire.sw-epkt@hostbridge/pciexrc, - fault.io.fire.fw-epkt@hostbridge/pciexrc, - fault.io.fire.sw-fw-mismatch@hostbridge/pciexrc->(A) - ereport.io.fire.epkt@hostbridge/pciexrc { MATCH_UNRECOGNIZED }; - -prop fault.io.fire.sw-epkt@hostbridge, - fault.io.fire.fw-epkt@hostbridge, - fault.io.fire.sw-fw-mismatch@hostbridge->(A) - ereport.io.fire.epkt@hostbridge { MATCH_UNRECOGNIZED }; - -prop fault.io.fire.hb.sw-config@hostbridge/pciexrc (0)-> - error.io.fire.jbc.driver@hostbridge/pciexrc; - -prop fault.io.fire.dmc.sw-algorithm@hostbridge/pciexrc (0)-> - error.io.fire.dmc.driver@hostbridge/pciexrc; - -prop fault.io.fire.dmc.sw-state@hostbridge/pciexrc (0)-> - error.io.fire.dmc.bad_state@hostbridge/pciexrc; - -/*************** - * PCI-E/PCI device fault and SW defects - ***************/ -fru pciexbus/pciexdev; -asru pciexbus/pciexdev/pciexfn; -event fault.io.fire.pciex.device@pciexbus/pciexdev/pciexfn, - FRU=pciexbus/pciexdev, - ASRU=pciexbus/pciexdev/pciexfn, - FITrate=PCIEX_DEV_FIT; - -fru pcibus/pcidev; -asru pcibus/pcidev/pcifn; -event fault.io.fire.pci.device@pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, - FRU=pcibus/pcidev, - ASRU=pcibus/pcidev/pcifn; - -/****************************** - * JBC Rules Begin Here * - ******************************/ - -/*************** - * EBUS fault - * ------------- - * Errors involving the ebus - ***************/ -fru hostbridge/pciexrc; -asru hostbridge/pciexrc; -event fault.io.ebus@hostbridge/pciexrc, - FITrate=EBUS_FIT, - FRU=hostbridge/pciexrc, - ASRU=hostbridge/pciexrc; - -/* - * A faulty ebus can cause ebus timeout ebus_to - * ebus_to ereport: - * sun4v: The fmri of the ereport is ioboard/hostbridge - * sun4u: The fmri of the ereport is pciexrc - */ -prop fault.io.ebus@hostbridge/pciexrc (1)-> - ereport.io.fire.jbc.ebus_to@hostbridge, - ereport.io.fire.jbc.ebus_to@hostbridge/pciexrc; - -/*************** - * Fire Asic HW error - * ------------- - * Errors caused by parity or unexpected behaviors in the asic. - ***************/ -prop error.io.fire.jbc.asic@hostbridge/pciexrc (1)-> - ereport.io.fire.jbc.cpe@hostbridge/pciexrc, - ereport.io.fire.jbc.mb_pea@hostbridge/pciexrc, - ereport.io.fire.jbc.mb_per@hostbridge/pciexrc, - ereport.io.fire.jbc.mb_pew@hostbridge/pciexrc, - ereport.io.fire.jbc.pio_cpe@hostbridge/pciexrc, - ereport.io.fire.jbc.pio_dpe@hostbridge/pciexrc; - -/*************** - * JBC Hostbus Link Errors - * ------------- - * Possible Parity Errors caused by bad links traces or cables. - * For instance on Ontarios there is a flex cable. For Chicagos - * it could be the link trace between the CPU and Fire. - ***************/ -event error.io.fire.jbc.bad_link@hostbridge/pciexrc; - -prop error.io.fire.jbc.bad_link@hostbridge/pciexrc (1)-> - ereport.io.fire.jbc.ape@hostbridge/pciexrc, - ereport.io.fire.jbc.bjc@hostbridge/pciexrc, - ereport.io.fire.jbc.rd_dpe@hostbridge/pciexrc, - ereport.io.fire.jbc.wr_dpe@hostbridge/pciexrc; - -/*************** - * JBC Hostbus Errors - * ------------- - * Errors being returned from the hostbus side and detected by fire asic. - ***************/ -fru hostbridge/pciexrc; -asru hostbridge/pciexrc; -event fault.io.fire.hbus@hostbridge/pciexrc, - FITrate=HBUS_FIT, - FRU=hostbridge/pciexrc, - ASRU=hostbridge/pciexrc; - -prop fault.io.fire.hbus@hostbridge/pciexrc (0)-> - error.io.fire.jbc.bad_link@hostbridge/pciexrc, - ereport.io.fire.jbc.icise@hostbridge/pciexrc, - ereport.io.fire.jbc.ill_bmr@hostbridge/pciexrc, - ereport.io.fire.jbc.jtceei@hostbridge/pciexrc, - ereport.io.fire.jbc.jtceer@hostbridge/pciexrc, - ereport.io.fire.jbc.jtceew@hostbridge/pciexrc; - -/*************** - * JBC Datapath Errors - * ------------- - * Errors resulting from the datapath of the hostbus and detected by fire asic. - ***************/ -fru cmp; -asru cmp; -event fault.io.fire.datapath@cmp, - FITrate=CPU_FIT, - FRU=cmp, - ASRU=cmp; - -prop fault.io.fire.datapath@cmp (0)-> - error.io.fire.jbc.bad_link@hostbridge/pciexrc; - -/* Duplicate the above fault prop for cpumodule */ -fru cpumodule/cpu; -asru cpumodule/cpu; -event fault.io.fire.datapath@cpumodule/cpu, - FITrate=CPU_FIT, - FRU=cpumodule/cpu, - ASRU=cpumodule/cpu; - -prop fault.io.fire.datapath@cpumodule/cpu (0)-> - error.io.fire.jbc.bad_link@hostbridge/pciexrc, - ereport.io.fire.jbc.wr_dpe@hostbridge/pciexrc; - -/*************** - * Fire driver is at fault. - * ------------- - * The px driver should not have been in this state. Defect the px driver. - ***************/ -prop error.io.fire.jbc.driver@hostbridge/pciexrc (1)-> - ereport.io.fire.jbc.ijp@hostbridge/pciexrc, - ereport.io.fire.jbc.ill_acc@hostbridge/pciexrc, - ereport.io.fire.jbc.ill_acc_rd@hostbridge/pciexrc, - ereport.io.fire.jbc.ill_bmw@hostbridge/pciexrc, - ereport.io.fire.jbc.jue@hostbridge/pciexrc, - ereport.io.fire.jbc.pio_unmap@hostbridge/pciexrc, - ereport.io.fire.jbc.pio_unmap_rd@hostbridge/pciexrc; - - -/****************************** - * DMC Rules Begin Here * - ******************************/ - -/*************** - * Fire PX SW error - * ------------- - * Errors caused by bad SW - ***************/ -prop error.io.fire.dmc.driver@hostbridge/pciexrc (1)-> - ereport.io.fire.dmc.ttc_cae@hostbridge/pciexrc; - -/*************** - * Unexpected Fire State - * ------------- - * The px driver should not have been in this state. Defect the px driver. - ***************/ -event error.io.fire.dmc.bad_state-mmu@hostbridge/pciexrc; - -prop error.io.fire.dmc.bad_state@hostbridge/pciexrc (1)-> - ereport.io.fire.dmc.cor_not_en@hostbridge/pciexrc, - ereport.io.fire.dmc.eq_not_en@hostbridge/pciexrc, - ereport.io.fire.dmc.fatal_not_en@hostbridge/pciexrc, - ereport.io.fire.dmc.msi_not_en@hostbridge/pciexrc, - ereport.io.fire.dmc.nonfatal_not_en@hostbridge/pciexrc, - ereport.io.fire.dmc.pmeack_not_en@hostbridge/pciexrc, - ereport.io.fire.dmc.pmpme_not_en@hostbridge/pciexrc; - -prop error.io.fire.dmc.bad_state-mmu@hostbridge/pciexrc (1)-> - ereport.io.fire.dmc.tbw_dme@hostbridge/pciexrc, - ereport.io.fire.dmc.trn_err@hostbridge/pciexrc; - -/*************** - * Fire Asic HW error - * ------------- - * Errors caused by parity or unexpected behaviors in the asic. - ***************/ -event error.io.fire.dmc.bad_parity@hostbridge/pciexrc; - -prop error.io.fire.dmc.asic@hostbridge/pciexrc (1)-> - error.io.fire.dmc.bad_parity@hostbridge/pciexrc, - ereport.io.fire.dmc.eq_over@hostbridge/pciexrc; - -/*************** - * Parity errors caused by dmc - * ------------- - * Fire asic error. - ***************/ -event error.io.fire.dmc.bad_parity-mmu@hostbridge/pciexrc; - -prop error.io.fire.dmc.bad_parity@hostbridge/pciexrc (1)-> - ereport.io.fire.dmc.msi_par_err@hostbridge/pciexrc; - -prop error.io.fire.dmc.bad_parity-mmu@hostbridge/pciexrc (1)-> - ereport.io.fire.dmc.tbw_dpe@hostbridge/pciexrc, - ereport.io.fire.dmc.tbw_ude@hostbridge/pciexrc, - ereport.io.fire.dmc.ttc_dpe@hostbridge/pciexrc; - -/*************** - * Malformed MSI - * ------------- - * A non-compliant PCIe/PCI device sent a malformed MSI. - ***************/ -prop fault.io.fire.pciex.device@pciexbus[b]/pciexdev[d]/pciexfn[f] (0) -> - ereport.io.fire.dmc.msi_mal_err@hostbridge/pciexrc - { - IMU_MATCH_BDF(b, d, f) && - is_under(hostbridge/pciexrc, pciexbus[b]/pciexdev[d]/pciexfn[f]) - }; -prop fault.io.fire.pci.device@pcibus[b]/pcidev[d]/pcifn[f] (0) -> - ereport.io.fire.dmc.msi_mal_err@hostbridge/pciexrc - { - IMU_MATCH_BDF(b, d, f) && - is_under(hostbridge/pciexrc, pcibus[b]/pcidev[d]/pcifn[f]) - }; - -/*************** - * Event queue overflow - * ------------- - * Since we don't know which devices are sending too many EQ's, we must - * indict Fire asic and all PCIe/PCI devices - ***************/ -#define PROP_PLAT_FRU "FRU" -#define GET_HB_FRU (confprop(asru(hostbridge/pciexrc), PROP_PLAT_FRU)) -#define GET_PCIE_FRU (confprop(asru(pciexbus[b]/pciexdev[d]/pciexfn[0]), PROP_PLAT_FRU)) -#define GET_PCI_FRU (confprop(asru(pcibus[b]/pcidev[d]/pcifn[0]), PROP_PLAT_FRU)) - -prop fault.io.fire.pciex.device@pciexbus[b]/pciexdev[d]/pciexfn[0] (0) -> - ereport.io.fire.dmc.eq_over@hostbridge/pciexrc - { - /* - * Indict PCI-E FRU(s) under this root complex excluding the - * one that the Fire ASIC resides on. - */ - is_under(hostbridge/pciexrc, pciexbus[b]/pciexdev[d]/pciexfn[0]) && - (GET_HB_FRU != GET_PCIE_FRU) - }; - -prop fault.io.fire.pci.device@pcibus[b]/pcidev[d]/pcifn[0] (0) -> - ereport.io.fire.dmc.eq_over@hostbridge/pciexrc - { - /* - * Indict PCI FRU(s) under this root complex excluding the - * one that the Fire ASIC resides on. - */ - is_under(hostbridge/pciexrc, pcibus[b]/pcidev[d]/pcifn[0]) && - (GET_HB_FRU != GET_PCI_FRU) - }; - -/*************** - * Secondary errors - * ------------- - * These are errors that require logs to be diagnosable. Secondary errors - * do not have logs so, just propagate them to no-diag. - ***************/ -event error.io.fire.dmc.secondary@hostbridge/pciexrc; - -prop error.io.fire.dmc.secondary@hostbridge/pciexrc (0) -> - ereport.io.fire.dmc.msi_mal_err@hostbridge/pciexrc{ IS_SECONDARY }; - -/****************************** - * PEC Rules Begin Here * - ******************************/ - -event error.io.fire.pec.buffer-parity@hostbridge/pciexrc; -event error.io.fire.pec.adjacentnode@hostbridge/pciexrc ; - -/*************** - * Fire PX SW error - * ------------- - * Errors caused by bad SW - ***************/ - -prop fault.io.fire.pec.sw-algorithm@hostbridge/pciexrc (0) -> - ereport.io.fire.pec.crs@hostbridge/pciexrc, - ereport.io.fire.pec.mrc@hostbridge/pciexrc; - -/*************** - * Fire Asic HW error - * ------------- - * Errors caused by parity or unexpected behaviors in the asic. - ***************/ -prop error.io.fire.pec.asic@hostbridge/pciexrc (1)-> - error.io.fire.pec.buffer-parity@hostbridge/pciexrc, - error.io.fire.pec.adjacentnode@hostbridge/pciexrc; - -prop error.io.fire.pec.buffer-parity@hostbridge/pciexrc (1) -> - ereport.io.fire.pec.edp@hostbridge/pciexrc, - ereport.io.fire.pec.ehp@hostbridge/pciexrc, - ereport.io.fire.pec.eip@hostbridge/pciexrc, - ereport.io.fire.pec.erp@hostbridge/pciexrc, - ereport.io.fire.pec.ihb_pe@hostbridge/pciexrc, - ereport.io.fire.pec.iip@hostbridge/pciexrc; - -/*************** - * Failed Links - * ------------- - * They will cause the fabric to be scanned and a fire.fabric ereport - * for the suspected devices will be sent. Do no diagnose these - * ereports and let the fire.fabric ereport be diagnosed. - ***************/ -event ereport.io.fire.link-events-trip@hostbridge/pciexrc ; - -engine serd.io.fire.link-events@hostbridge/pciexrc, - N=LINK_EVENTS_COUNT, T=LINK_EVENTS_TIME, method=persistent, - trip=ereport.io.fire.link-events-trip@hostbridge/pciexrc ; - -event upset.io.fire.link-events@hostbridge/pciexrc, - engine=serd.io.fire.link-events@hostbridge/pciexrc ; - -event error.io.fire.link-events@hostbridge/pciexrc; - -prop upset.io.fire.link-events@hostbridge/pciexrc (0)-> - error.io.fire.link-events@hostbridge/pciexrc; - -prop error.io.fire.link-events@hostbridge/pciexrc (1)-> - ereport.io.fire.pec.lrs@hostbridge/pciexrc, - ereport.io.fire.pec.ldn@hostbridge/pciexrc; - - -/* - * Fault at the adjacent node which is right below the Fire ASIC - */ -fru hostbridge/pciexrc/pciexbus/pciexdev; -asru hostbridge/pciexrc/pciexbus/pciexdev/pciexfn; -event fault.io.fire.pciex.device@hostbridge/pciexrc/pciexbus/pciexdev/pciexfn, - FITrate=HB_FIT, FRU=hostbridge/pciexrc/pciexbus/pciexdev, - ASRU=hostbridge/pciexrc/pciexbus/pciexdev/pciexfn; - -prop fault.io.fire.asic@hostbridge/pciexrc (0) -> - error.io.fire.pec.adjacentnode@hostbridge/pciexrc; - -prop fault.io.fire.pciex.device@hostbridge/pciexrc/pciexbus/pciexdev/pciexfn -(0) -> - error.io.fire.pec.adjacentnode@hostbridge/pciexrc - { - is_under(hostbridge/pciexrc, - hostbridge/pciexrc/pciexbus/pciexdev/pciexfn) - }; - -prop error.io.fire.pec.adjacentnode@hostbridge/pciexrc (0) -> - ereport.io.fire.link-events-trip@hostbridge/pciexrc; - - -/****************************** - * Fabric Rules Begin Here * - ******************************/ - -/*************** - * fire.fabric rules - * ------------- - * Below rules are so we get a single suspect list in 1 fault with percentage - * of indiction being equal among all the suspect FRUs - ***************/ -prop fault.io.fire.pciex.device@pciexbus/pciexdev/pciexfn (0) -> - error.io.fire.fabric@pciexbus/pciexdev/pciexfn; - -prop fault.io.fire.pci.device@pcibus/pcidev/pcifn (0) -> - error.io.fire.fabric@pcibus/pcidev/pcifn; - -prop error.io.fire.fabric@pciexbus/pciexdev/pciexfn (1) -> - ereport.io.fire.fabric@pciexbus/pciexdev/pciexfn { !MATCH_CE }; - -prop error.io.fire.fabric@pcibus/pcidev/pcifn (1) -> - ereport.io.fire.fabric@pcibus/pcidev/pcifn; - -prop error.io.fire.fabric-sib@hostbridge/pciexrc (0) -> - ereport.io.fire.fabric@pciexbus/pciexdev/pciexfn { - is_under(hostbridge/pciexrc, pciexbus/pciexdev/pciexfn) && !MATCH_CE - }; - -prop error.io.fire.fabric-sib@hostbridge/pciexrc (0) -> - ereport.io.fire.fabric@pcibus/pcidev/pcifn { - is_under(hostbridge/pciexrc, pcibus/pcidev/pcifn) - }; - -prop error.io.fire.fabric@pciexbus/pciexdev/pciexfn (1) -> - error.io.fire.fabric-sib@hostbridge/pciexrc { - is_under(hostbridge/pciexrc, pciexbus/pciexdev/pciexfn) - }; - -prop error.io.fire.fabric@pcibus/pcidev/pcifn (1) -> - error.io.fire.fabric-sib@hostbridge/pciexrc { - is_under(hostbridge/pciexrc, pcibus/pcidev/pcifn) - }; - -event upset.io.fire.fabric@pciexbus/pciexdev/pciexfn{within(1s)}; -event ereport.io.fire.pciex.ce@pciexbus/pciexdev/pciexfn{within(1s)}; - -/* SERD CEs */ -prop upset.io.fire.fabric@pciexbus[b]/pciexdev[d]/pciexfn[f] (0) -> - ereport.io.fire.fabric@pciexbus[b]/pciexdev[d]/pciexfn[f] - { MATCH_CE }; - -event upset.io.fire.fabric@pciexbus/pciexdev/pciexfn, - engine=serd.io.fire.fabric@pciexbus/pciexdev/pciexfn; - -engine serd.io.fire.fabric@pciexbus/pciexdev/pciexfn, - N=CE_EVENTS_COUNT, T=CE_EVENTS_TIME, method=persistent, - trip=ereport.io.fire.pciex.ce@pciexbus/pciexdev/pciexfn; - -prop fault.io.fire.pciex.device@pciexbus/pciexdev/pciexfn (0) -> - ereport.io.fire.pciex.ce@pciexbus/pciexdev/pciexfn; - -/*************** - * Upsets - * ------------- - * Used to hide ereports that are not currently diagnose or should not be - * diagnosed - ***************/ -event upset.io.fire.nodiag@hostbridge/pciexrc; -event error.io.fire.dmc.nodiag@hostbridge/pciexrc; - -prop error.io.fire.dmc.nodiag@hostbridge/pciexrc (1)-> - ereport.io.fire.dmc.tbw_err@hostbridge/pciexrc; - -prop upset.io.fire.nodiag@hostbridge/pciexrc (0)-> - ereport.io.fire.jbc.ce_asyn@hostbridge/pciexrc, /* CPU */ - ereport.io.fire.jbc.jbe@hostbridge/pciexrc, /* CPU */ - ereport.io.fire.jbc.jte@hostbridge/pciexrc, /* CPU */ - ereport.io.fire.jbc.ue_asyn@hostbridge/pciexrc, /* CPU */ - ereport.io.fire.jbc.unsol_intr@hostbridge/pciexrc, /* CPU */ - ereport.io.fire.jbc.unsol_rd@hostbridge/pciexrc, /* CPU */ - ereport.io.fire.pec.lin@hostbridge/pciexrc, - ereport.io.fire.pec.lup@hostbridge/pciexrc, - error.io.fire.dmc.nodiag@hostbridge/pciexrc, - error.io.fire.dmc.secondary@hostbridge/pciexrc, - ereport.io.fire.epkt@hostbridge { !MATCH_UNRECOGNIZED }, - ereport.io.fire.epkt@hostbridge/pciexrc { !MATCH_UNRECOGNIZED }; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/Makefile b/usr/src/cmd/fm/eversholt/files/sparc/sun4u/Makefile deleted file mode 100644 index 630ed0348e..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/Makefile +++ /dev/null @@ -1,33 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2006 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../sun4/Makefile.sun4 - -EFT_PLAT= sun4u -SUN4UEFTFILES= schizo.eft psycho.eft tomatillo.eft xmits.eft oberon.eft -EFT_PLAT_FILES= $(SUN4UEFTFILES) $(SUN4EFTFILES) - -include ../../Makefile.com diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/oberon.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4u/oberon.esc deleted file mode 100644 index 0a18f85a71..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/oberon.esc +++ /dev/null @@ -1,160 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2008 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -/* - * Eversholt rules for Oberon ASICs - */ - -#pragma dictionary "SUN4U" - -#define HB_FIT 1000 - -/* - * Test for primary or secondary ereports - */ -#define IS_PRIMARY (payloadprop("primary")) -#define IS_SECONDARY (! payloadprop("primary")) - -event error.io.oberon.pec.secondary@hostbridge/pciexrc; -event error.io.oberon.pec.fabric_error@hostbridge/pciexrc; - -/* - * Ereports derived from the - * UBC Status Clear Register - * - * dmarduea-channel DMA read uncorrectable error (UE) in leaf A - * dmawtuea DMA write UE in leaf A - * memrdaxa Memory read invalid address error in leaf A - * memwtaxa Memory write invalid address error in leaf A - * dmardueb-channel DMA read uncorrectable error (UE) in leaf B - * dmawtueb DMA write UE in leaf B - * memrdaxb Memory read invalid address error in leaf B - * memwtaxb Memory write invalid address error in leaf B - * piowtue-channel PIO write UE - * piowbeue-channel PIO write byte enable UE - * piorbeue-channel PIO read byte enable UE - */ -event ereport.io.oberon.ubc.dmarduea-channel@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.dmawtuea@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.memrdaxa@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.memwtaxa@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.dmardueb-channel@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.dmawtueb@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.memrdaxb@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.memwtaxb@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.piowtue-channel@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.piowbeue-channel@hostbridge/pciexrc{within(5s)}; -event ereport.io.oberon.ubc.piorbeue-channel@hostbridge/pciexrc{within(5s)}; - -/* - * tlueitmo TLU Egress Issue Timeout - */ -event ereport.io.oberon.pec.tlueitmo@hostbridge/pciexrc{within(5s)}; - -/* - * TLU Uncorrectable and Correctable ereports - * - * ecrc End-to-end CRC error - */ -event ereport.io.oberon.pec.ecrc@hostbridge/pciexrc{within(5s)}; - -/* - * A faulty Oberon may cause; - * - * - DMA write internal RAM UE: dmawtuea, dmawtueb - * - TLU ECRC - * - * Errors marked with * may cause PCI-E abort - */ - -fru hostbridge; -asru hostbridge; -event fault.io.oberon@hostbridge, - FITrate=HB_FIT, FRU=hostbridge, ASRU=hostbridge; -prop fault.io.oberon@hostbridge (0)-> - ereport.io.oberon.ubc.dmawtuea@hostbridge/pciexrc, - ereport.io.oberon.ubc.dmawtueb@hostbridge/pciexrc; -event fault.io.oberon@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge, ASRU=hostbridge; -prop fault.io.oberon@hostbridge/pciexrc (0)-> - ereport.io.oberon.pec.ecrc@hostbridge/pciexrc { IS_PRIMARY }; - -/* - * A faulty PX nexus driver can cause - * - Jbus unmapped error - * - mmu invalid, out of range, protection etc. all except data parity - * - invalid pio r/w - * - unsolicited read or interrupt return - * - msg received to unenabled queue - */ - -#define SW_FIT 5000 /* No real fit rate, SW */ -event fault.io.fire.hb.sw-config@hostbridge/pciexrc, retire=0, response=0, - FITrate=SW_FIT; - -prop fault.io.fire.hb.sw-config@hostbridge/pciexrc (0)-> - ereport.io.oberon.ubc.memrdaxa@hostbridge/pciexrc, - ereport.io.oberon.ubc.memrdaxb@hostbridge/pciexrc, - ereport.io.oberon.ubc.memwtaxa@hostbridge/pciexrc, - ereport.io.oberon.ubc.memwtaxb@hostbridge/pciexrc; - -/* - * Secondary errors of the ereport that the device is at fault. - * Undiagnosed the secondary errors since the payload is invalid. - */ -prop error.io.oberon.pec.secondary@hostbridge/pciexrc (0) -> - ereport.io.oberon.pec.ecrc@hostbridge/pciexrc{ IS_SECONDARY }; - -/* - * For logging purpose only. - * The px nexus driver generates equivalent pciex ereports for the - * common pciex rules to diagnose. - */ -prop error.io.oberon.pec.fabric_error@hostbridge/pciexrc(0) -> - ereport.io.oberon.pec.ecrc@hostbridge/pciexrc; - -event ereport.io.oberon.nodiag@hostbridge; - -/* - * Upset used to hide ereports that are not currently diagnosed. - */ -engine serd.io.oberon.nodiag@hostbridge, - N=1000, T=1s, method=persistent, - trip=ereport.io.oberon.nodiag@hostbridge; - -event upset.io.oberon.nodiag@hostbridge, - engine=serd.io.oberon.nodiag@hostbridge; - -prop upset.io.oberon.nodiag@hostbridge (0)-> - ereport.io.oberon.ubc.dmarduea-channel@hostbridge/pciexrc, - ereport.io.oberon.ubc.dmardueb-channel@hostbridge/pciexrc, - ereport.io.oberon.ubc.piowtue-channel@hostbridge/pciexrc, - ereport.io.oberon.ubc.piowbeue-channel@hostbridge/pciexrc, - ereport.io.oberon.ubc.piorbeue-channel@hostbridge/pciexrc, - ereport.io.oberon.pec.tlueitmo@hostbridge/pciexrc, - error.io.oberon.pec.fabric_error@hostbridge/pciexrc, - ereport.io.oberon.nodiag@hostbridge; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/psycho.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4u/psycho.esc deleted file mode 100644 index da5ece375b..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/psycho.esc +++ /dev/null @@ -1,252 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2008 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -#pragma dictionary "SUN4U" - -#define AGENT_ID_MASK 0x1f -#define AGENT_ID_SHIFT 24 - -#define HB_FIT 1000 -#define HBUS_FIT 1000 -#define PCI_BUS_FIT 500 -#define PCI_DEV_FIT 1000 -#define CPU_FIT 500 - -#define PCI_HB_DEV_PATH hostbridge/pcibus/pcidev[32]/pcifn[0] - -fru hostbridge; -asru hostbridge; - -event fault.io.psycho@hostbridge, - FITrate=HB_FIT, FRU=hostbridge, ASRU=hostbridge; - -event error.io.psy.ecc.thresh@hostbridge; -event ereport.io.psy.ecc.pue@hostbridge{within(5s)}; -event ereport.io.psy.ecc.s-pue@hostbridge{within(5s)}; -event ereport.io.psy.ecc.thresh@hostbridge; - -/* - * A faulty Psycho hostbridge may cause: - * - * - pue: the psycho to detect a PIO uncorrectable error, bad reader. - * - s-pue: the psycho to detect a secondary PIO UE, bad reader. - * - ecc: the SERD engine to gather enough PIO CEs to generate an ereport. - */ -prop fault.io.psycho@hostbridge (0)-> - ereport.io.psy.ecc.pue@hostbridge, - ereport.io.psy.ecc.s-pue@hostbridge, - error.io.psy.ecc.thresh@hostbridge; - -engine serd.io.psycho.ecc@hostbridge, - N=3, T=1day, method=persistent, - trip=ereport.io.psy.ecc.thresh@hostbridge; - -event upset.io.psycho@hostbridge, - engine=serd.io.psycho.ecc@hostbridge; - -event ereport.io.psy.ecc.pce@hostbridge{within(5s)}; -event ereport.io.psy.ecc.s-pce@hostbridge{within(5s)}; - -prop error.io.psy.ecc.thresh@hostbridge (2)-> - ereport.io.psy.ecc.thresh@hostbridge, - ereport.io.psy.ecc.pce@hostbridge; - -/* - * An upset Psycho may cause: - * - * - pce: the psycho to detect a PIO correctable error, bad reader. - */ -prop upset.io.psycho@hostbridge (0)-> - ereport.io.psy.ecc.pce@hostbridge; - -event fault.io.hbus@hostbridge, - FITrate=HBUS_FIT, FRU=hostbridge, ASRU=hostbridge; - -/* - * A faulty host bus may cause: - * - * - pue: a PIO uncorrectable error. - * - s-pue: a secondary PIO UE. - * - ecc: the SERD engine to gather enough PIO CEs to generate an ereport. - */ -prop fault.io.hbus@hostbridge (0)-> - ereport.io.psy.ecc.pue@hostbridge, - ereport.io.psy.ecc.s-pue@hostbridge, - error.io.psy.ecc.thresh@hostbridge; - -fru cpu; - -event fault.io.datapath@cpu, retire=0, - FITrate=CPU_FIT, FRU=cpu; - -event error.io.cpu.ecc.thresh@cpu; - -/* - * A faulty CPU may cause: - * - * - pue: a PIO uncorrectable error, where the captured Agentid matches - * the cpuid. - * - ecc: the SERD engine for the CPU to fire due to PIO CEs from this - * CPU - */ -prop fault.io.datapath@cpu[cpuid] (0)-> - ereport.io.psy.ecc.pue@hostbridge - {((payloadprop("ecc-afsr") >> AGENT_ID_SHIFT) & AGENT_ID_MASK) == cpuid}; - -prop fault.io.datapath@cpu (0)-> - error.io.cpu.ecc.thresh@cpu; - -prop error.io.cpu.ecc.thresh@cpu (1)-> - ereport.io.psy.ecc.thresh@hostbridge<>; - -prop error.io.cpu.ecc.thresh@cpu[cpuid] (1)-> - ereport.io.psy.ecc.pce@hostbridge<> - {((payloadprop("ecc-afsr") >> AGENT_ID_SHIFT) & AGENT_ID_MASK) == cpuid}; - -asru pcibus/pcidev/pcifn; -fru pcibus/pcidev; - -event fault.io.pci.device-interr@hostbridge/pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, FRU=pcibus/pcidev, ASRU=pcibus/pcidev/pcifn; - -event fault.io.pci.device-interr@pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, FRU=pcibus/pcidev, ASRU=pcibus/pcidev/pcifn; - -event error.io.psy.pbm.rl@hostbridge/pcibus/pcidev/pcifn; -event error.io.psy.pbm.rl@pcibus/pcidev/pcifn; -event error.io.psy.pbm.rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.io.psy.pbm.target-rl@pcibus/pcidev/pcifn; -event error.io.psy.pbm.target-rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.perr-pw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.perr-dw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.retry-to-d@hostbridge/pcibus/pcidev/pcifn; -event error.psy.cpu.berr@cpu; - -event ereport.io.psy.sbh@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.psy.pbm.rl@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.psy.pbm.s-rl@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.psy.pbm.s-ma@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.psy.pbm.s-rta@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.psy.pbm.s-mdpe@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.psy.pbm.target-rl@pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.pci.rserr@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.cpu.ultraSPARC-II.berr@cpu{within(5s)}; - -/* - * A faulty PCI device may cause: - * - * - rl: it to retry a transaction beyond the specified limit. - * - sbh: it to generate a streaming byte hole. - * - * For rl, there may be a target-rl ereport on a child device. There may also be - * an associated dto - the retry-to-d error propagates into the pci.esc rules - * to handle this. - */ - -prop fault.io.pci.device-interr@pcibus/pcidev[fromdev]/pcifn (0)-> - error.io.psy.pbm.rl@pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }, - error.io.psy.pbm.target-rl@pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }; - -prop error.io.psy.pbm.rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn (1)-> - error.io.psy.pbm.rl@pcibus/pcidev/pcifn; - -prop error.io.psy.pbm.rl@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.psy.pbm.rl@PCI_HB_DEV_PATH, - ereport.io.psy.pbm.s-rl@PCI_HB_DEV_PATH; - -prop error.io.psy.pbm.target-rl@pcibus/pcidev/pcifn (1)-> - error.io.psy.pbm.target-rl@pcibus/pcidev/pcifn/pcibus<>/pcidev<>/pcifn<>; - -prop error.io.psy.pbm.target-rl@pcibus/pcidev/pcifn (0)-> - ereport.io.psy.pbm.target-rl@pcibus/pcidev/pcifn; - -prop error.io.psy.pbm.rl@hostbridge/pcibus/pcidev/pcifn (0)-> - error.io.pci.retry-to-d@hostbridge/pcibus/pcidev/pcifn; - -prop error.io.psy.pbm.rl@hostbridge/pcibus/pcidev/pcifn (0)-> - error.psy.cpu.berr@cpu; - -prop fault.io.pci.device-interr@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.psy.sbh@PCI_HB_DEV_PATH; - -/* - * Need to add the following psycho specific propagations to complete the PCI - * fault tree. These are to allow propagations to secondary errors and cpu - * bus errors, and to represent the way the chip raises rserr - * on detection of SERR# - */ -prop error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.psy.pbm.s-ma@PCI_HB_DEV_PATH; - -prop error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.psy.pbm.s-rta@PCI_HB_DEV_PATH; - -prop error.io.pci.perr-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.psy.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.perr-dw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.psy.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.psy.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.psy.cpu.berr@cpu; - -prop error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.psy.cpu.berr@cpu; - -prop error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.psy.cpu.berr@cpu; - -prop error.psy.cpu.berr@cpu (0)-> - ereport.cpu.ultraSPARC-II.berr@cpu; - -prop error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.pci.rserr@PCI_HB_DEV_PATH; - -event ereport.io.psy.nodiag@hostbridge; - -/* - * Upset used to hide ereports that can not be currently diagnosed. - */ -engine serd.io.psy.nodiag@hostbridge, - N=1000, T=1hour, method=persistent, - trip=ereport.io.psy.nodiag@hostbridge; - -event upset.io.psy.nodiag@hostbridge, - engine=serd.io.psy.nodiag@hostbridge; - -prop upset.io.psy.nodiag@hostbridge (0)-> - ereport.io.psy.ecc.s-pce@hostbridge, - ereport.io.psy.nodiag@hostbridge; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/schizo.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4u/schizo.esc deleted file mode 100644 index 09957e8654..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/schizo.esc +++ /dev/null @@ -1,441 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2008 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -#pragma dictionary "SUN4U" - -#define AGENT_ID_MASK 0x1f -#define AGENT_ID_SHIFT 24 - -#define HB_FIT 1000 -#define HBUS_FIT 1000 -#define PCI_BUS_FIT 500 -#define PCI_DEV_FIT 1000 -#define CPU_FIT 500 - -#define PCI_HB_DEV_PATH hostbridge/pcibus/pcidev[32]/pcifn[0] - -fru hostbridge; -asru hostbridge; - -event fault.io.schizo@hostbridge, - FITrate=HB_FIT, FRU=hostbridge, ASRU=hostbridge; - -event error.io.sch.saf.dstat@hostbridge; -event error.io.sch.saf.to@hostbridge; -event error.io.sch.saf.bus@hostbridge; -event error.io.sch.ecc.thresh@hostbridge; -event error.io.pci.device-ta@hostbridge/pcibus/pcidev/pcifn; - -event ereport.io.sch.saf.to@hostbridge{within(5s)}; -event ereport.io.sch.saf.bus@hostbridge{within(5s)}; -event ereport.io.sch.saf.bca@hostbridge{within(5s)}; -event ereport.io.sch.saf.bcb@hostbridge{within(5s)}; -event ereport.io.sch.saf.ciq-to@hostbridge{within(5s)}; -event ereport.io.sch.saf.lpq-to@hostbridge{within(5s)}; -event ereport.io.sch.saf.sfpq-to@hostbridge{within(5s)}; -event ereport.io.sch.saf.ufpq-to@hostbridge{within(5s)}; -event ereport.io.sch.saf.ape@hostbridge{within(5s)}; -event ereport.io.sch.ecc.pce@hostbridge{within(5s)}; -event ereport.io.sch.ecc.pue@hostbridge{within(5s)}; -event ereport.io.sch.ecc.s-pce@hostbridge{within(5s)}; -event ereport.io.sch.ecc.s-pue@hostbridge{within(5s)}; -event ereport.io.sch.ecc.thresh@hostbridge{within(5s)}; -event ereport.io.sch.saf.dstat@hostbridge{within(5s)}; - -/* - * A faulty Schizo hostbridge may cause: - * - * - bca: bad safari command from PCI block A. - * - bcb: bad safari command from PCI block B. - * - ciq-to: coherent input queue timeout. - * - lpq-to: local PIO queue timeout. - * - sfpq-to: safari foreign PIO queue timeout. - * - ufpq-to: UPA foreign PIO queue timeout. - * - ape: address parity error. - * - pue: PIO uncorrectable error, bad reader. - * - s-pue: secondary PIO UE, bad reader. - * - ecc: multiple PIO CEs. - * - to: safari bus timeout. - * - bus: safari bus error. - * - dstat: errant dstat on incoming data. - * - * The to, bus and dstat errors can cause a target abort to be sent onto the - * pci bus in response to a dma request. We represent this using a device-ta - * error to propagate into the generic pci.esc rules. - */ -prop fault.io.schizo@hostbridge (0)-> - ereport.io.sch.saf.bca@hostbridge, - ereport.io.sch.saf.bcb@hostbridge, - ereport.io.sch.saf.ciq-to@hostbridge, - ereport.io.sch.saf.lpq-to@hostbridge, - ereport.io.sch.saf.sfpq-to@hostbridge, - ereport.io.sch.saf.ufpq-to@hostbridge, - ereport.io.sch.saf.ape@hostbridge, - ereport.io.sch.ecc.pue@hostbridge, - ereport.io.sch.ecc.s-pue@hostbridge, - error.io.sch.ecc.thresh@hostbridge, - error.io.sch.saf.to@hostbridge, - error.io.sch.saf.bus@hostbridge, - error.io.sch.saf.dstat@hostbridge; - -prop error.io.sch.ecc.thresh@hostbridge (2)-> - ereport.io.sch.ecc.thresh@hostbridge, - ereport.io.sch.ecc.pce@hostbridge; - -prop error.io.sch.saf.to@hostbridge (2)-> - ereport.io.sch.saf.to@hostbridge, - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.sch.saf.bus@hostbridge (2)-> - ereport.io.sch.saf.bus@hostbridge, - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.sch.saf.dstat@hostbridge (1)-> - ereport.io.sch.saf.dstat@hostbridge; - -prop error.io.sch.saf.dstat@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -engine serd.io.schizo.ecc@hostbridge, - N=3, T=1day, method=persistent, - trip=ereport.io.sch.ecc.thresh@hostbridge; - -event upset.io.schizo@hostbridge, - engine=serd.io.schizo.ecc@hostbridge; - -/* - * An upset schizo may cause: - * - * - pce: PIO correctable error. - */ -prop upset.io.schizo@hostbridge (0)-> - ereport.io.sch.ecc.pce@hostbridge; - -fru cpu; - -event fault.io.datapath@cpu, FITrate=CPU_FIT, FRU=cpu, retire=0; - -event error.io.cpu.ecc.thresh@cpu; -event ereport.io.sch.saf.ssm-dis@hostbridge{within(5s)}; -event ereport.io.sch.saf.cpu0-par@hostbridge{within(5s)}; -event ereport.io.sch.saf.cpu0-bidi@hostbridge{within(5s)}; -event ereport.io.sch.saf.cpu1-par@hostbridge{within(5s)}; -event ereport.io.sch.saf.cpu1-bidi@hostbridge{within(5s)}; - -/* - * A faulty xcal CPU[0] may cause: - * - * - cpu0-par: parity error on the unidirectional signals. - * - cpu0-bidi: parity error on the bi-directional signals. - */ -prop fault.io.datapath@cpu[0] (0)-> - ereport.io.sch.saf.cpu0-par@hostbridge, - ereport.io.sch.saf.cpu0-bidi@hostbridge; - -/* - * A faulty xcal CPU[1] may cause: - * - * - cpu1-par: parity error on the unidirectional signals. - * - cpu1-bidi: parity error on the bidirectional signals. - */ -prop fault.io.datapath@cpu[1] (0)-> - ereport.io.sch.saf.cpu1-par@hostbridge, - ereport.io.sch.saf.cpu1-bidi@hostbridge; - -/* - * A faulty CPU may cause: - * - * - to: safari bus timeout. - * - bus: safari bus error. - * - dstat: incorrect dstat sent to hostbridge. - * - ssm-dis: ssm command sent to hostbridge when not enabled. - * - ape: safari address parity error. - * - pue: PIO uncorrectable error. - * - ecc: multiple PIO CEs. - */ -prop fault.io.datapath@cpu (0)-> - error.io.sch.saf.to@hostbridge, - error.io.sch.saf.bus@hostbridge, - error.io.sch.saf.dstat@hostbridge, - ereport.io.sch.saf.ssm-dis@hostbridge, - ereport.io.sch.saf.ape@hostbridge; - -prop fault.io.datapath@cpu[cpuid] (0)-> - ereport.io.sch.ecc.pue@hostbridge - {((payloadprop("ecc-afsr") >> AGENT_ID_SHIFT) & AGENT_ID_MASK) == cpuid}; - -prop fault.io.datapath@cpu (0)-> - error.io.cpu.ecc.thresh@cpu; - -prop error.io.cpu.ecc.thresh@cpu (1)-> - ereport.io.sch.ecc.thresh@hostbridge<>; - -prop error.io.cpu.ecc.thresh@cpu[cpuid] (1)-> - ereport.io.sch.ecc.pce@hostbridge<> - {((payloadprop("ecc-afsr") >> AGENT_ID_SHIFT) & AGENT_ID_MASK) == cpuid}; - -event fault.io.hbus@hostbridge, - FITrate=HBUS_FIT, FRU=hostbridge, ASRU=hostbridge; - -/* - * A faulty host bus may cause: - * - * - ape: address parity error. - * - cpu0-par: parity error on the unidirectional signals. - * - cpu0-bidi: parity error on the bidirectional signals. - * - cpu1-par: parity error on the unidirectional signals. - * - cpu1-bidi: parity error on the bidirectional signals. - * - pue: PIO uncorrectable error. - * - s-pue: secondary PIO UE. - * - ecc: multiple PIO CEs. - */ -prop fault.io.hbus@hostbridge (0)-> - ereport.io.sch.saf.ape@hostbridge, - ereport.io.sch.saf.cpu0-par@hostbridge, - ereport.io.sch.saf.cpu0-bidi@hostbridge, - ereport.io.sch.saf.cpu1-par@hostbridge, - ereport.io.sch.saf.cpu1-bidi@hostbridge, - ereport.io.sch.ecc.pue@hostbridge, - ereport.io.sch.ecc.s-pue@hostbridge, - error.io.sch.ecc.thresh@hostbridge; - -/* - * A bad request from a downstream device/driver may cause - * - * - um: safari unmapped address error. - * - mmu: a iommu translation error. - */ -event error.io.pci.badreq-pw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.badreq-drw-u@hostbridge/pcibus/pcidev/pcifn; - -event ereport.io.pci.rserr@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.mmu@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.saf.um@hostbridge{within(5s)}; - -prop error.io.pci.badreq-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.saf.um@hostbridge; - -prop error.io.pci.badreq-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.mmu@PCI_HB_DEV_PATH; - -prop error.io.pci.badreq-drw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.saf.um@hostbridge; - -prop error.io.pci.badreq-drw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.mmu@PCI_HB_DEV_PATH; - -fru pcibus; -asru pcibus; - -event fault.io.pci.bus@hostbridge/pcibus, - FITrate=PCI_BUS_FIT, FRU=pcibus, ASRU=pcibus; - -event ereport.io.sch.bu@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.s-bu@hostbridge/pcibus/pcidev/pcifn{within(5s)}; - -/* - * A faulty PCI bus may cause: - * - * - bu: PCI bus unusable error. - * - s-bu: secondary PCI bus unusable error. - */ -prop fault.io.pci.bus@hostbridge/pcibus (0)-> - ereport.io.sch.bu@PCI_HB_DEV_PATH, - ereport.io.sch.s-bu@PCI_HB_DEV_PATH; - -fru pcibus/pcidev; -asru pcibus/pcidev/pcifn; - -event fault.io.pci.device-interr@hostbridge/pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, FRU=pcibus/pcidev, ASRU=pcibus/pcidev/pcifn; - -event fault.io.pci.device-interr@pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, FRU=pcibus/pcidev, ASRU=pcibus/pcidev/pcifn; - -event error.io.sch.pbm.rl@hostbridge/pcibus/pcidev/pcifn; -event error.io.sch.pbm.rl@pcibus/pcidev/pcifn; -event error.io.sch.pbm.rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.io.sch.pbm.target-rl@pcibus/pcidev/pcifn; -event error.io.sch.pbm.target-rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.io.sch.pbm.tto@hostbridge/pcibus/pcidev/pcifn; -event error.io.sch.pbm.target-tto@hostbridge/pcibus/pcidev/pcifn; -event error.io.sch.pbm.target-tto@pcibus/pcidev/pcifn; -event error.io.sch.pbm.target-tto@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.sch.cpu.berr@cpu; -event error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.perr-pw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.perr-dw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.retry-to-d@hostbridge/pcibus/pcidev/pcifn; - -event ereport.io.sch.sbh@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.rl@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.tto@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.s-rl@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.s-tto@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.s-ma@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.s-rta@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.s-mdpe@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.target-rl@pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.sch.pbm.target-tto@pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.pci.sserr@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.cpu.ultraSPARC-III.berr@cpu{within(5s)}; -event ereport.cpu.ultraSPARC-IIIplus.berr@cpu{within(5s)}; -event ereport.cpu.ultraSPARC-IV.berr@cpu{within(5s)}; -event ereport.cpu.ultraSPARC-IVplus.berr@cpu{within(5s)}; - -/* - * A faulty PCI device may cause: - * - * - sbh: a streaming byte hole error. - * - rl: it to exceed the number retriesfor a transaction. - * - tto: it to not assert trdy# within the alloted timeout. - * - * For rl and tto, there may be a target- ereport on a child device. For rl, - * there may also be an associated dto - the retry-to-d error propagates into - * the pci.esc rules to handle this. - */ -prop fault.io.pci.device-interr@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.sbh@PCI_HB_DEV_PATH; - -prop fault.io.pci.device-interr@pcibus/pcidev[fromdev]/pcifn (0)-> - error.io.sch.pbm.rl@pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }, - error.io.sch.pbm.target-rl@pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }; - -prop error.io.sch.pbm.rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn (1)-> - error.io.sch.pbm.rl@pcibus/pcidev/pcifn; - -prop error.io.sch.pbm.rl@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.sch.pbm.rl@PCI_HB_DEV_PATH, - ereport.io.sch.pbm.s-rl@PCI_HB_DEV_PATH; - -prop error.io.sch.pbm.target-rl@pcibus/pcidev/pcifn (1)-> - error.io.sch.pbm.target-rl@pcibus/pcidev/pcifn/pcibus<>/pcidev<>/pcifn<>; - -prop error.io.sch.pbm.target-rl@pcibus/pcidev/pcifn (0)-> - ereport.io.sch.pbm.target-rl@pcibus/pcidev/pcifn; - -prop error.io.sch.pbm.rl@hostbridge/pcibus/pcidev/pcifn (0)-> - error.io.pci.retry-to-d@hostbridge/pcibus/pcidev/pcifn; - -prop error.io.sch.pbm.rl@hostbridge/pcibus/pcidev/pcifn (0)-> - error.sch.cpu.berr@cpu; - -prop fault.io.pci.device-interr@hostbridge/pcibus/pcidev[fromdev]/pcifn (0)-> - error.io.sch.pbm.tto@hostbridge/pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }; - -prop error.io.sch.pbm.tto@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.sch.pbm.tto@PCI_HB_DEV_PATH, - ereport.io.sch.pbm.s-tto@PCI_HB_DEV_PATH; - -prop error.io.sch.pbm.tto@hostbridge/pcibus/pcidev/pcifn (1)-> - error.io.sch.pbm.target-tto@hostbridge/pcibus/pcidev/pcifn; - -prop error.io.sch.pbm.target-tto@pcibus/pcidev/pcifn (0)-> - ereport.io.sch.pbm.target-tto@pcibus/pcidev/pcifn; - -prop error.io.sch.pbm.target-tto@pcibus/pcidev/pcifn (1)-> - error.io.sch.pbm.target-tto@pcibus/pcidev/pcifn/pcibus<>/pcidev<>/pcifn<>; - -prop error.io.sch.pbm.tto@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.sch.bu@PCI_HB_DEV_PATH; - -/* - * Need to add the following schizo specific propagations to complete the PCI - * fault tree. These are to allow propagations to secondary errors and cpu - * bus errors, and to represent the way the chip can raise both rserr and sserr - * on detection of SERR# - */ -prop error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.pbm.s-ma@PCI_HB_DEV_PATH; - -prop error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.pbm.s-rta@PCI_HB_DEV_PATH; - -prop error.io.pci.perr-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.perr-dw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.sch.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.sch.cpu.berr@cpu; - -prop error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.sch.cpu.berr@cpu; - -prop error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.sch.cpu.berr@cpu; - -prop error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.pci.rserr@PCI_HB_DEV_PATH; - -prop error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.pci.sserr@PCI_HB_DEV_PATH; - -prop error.sch.cpu.berr@cpu (1)-> - ereport.cpu.ultraSPARC-III.berr@cpu, - ereport.cpu.ultraSPARC-IIIplus.berr@cpu, - ereport.cpu.ultraSPARC-IV.berr@cpu, - ereport.cpu.ultraSPARC-IVplus.berr@cpu; - -event error.io.sch.ecc.drue@hostbridge; -event ereport.io.sch.ecc.drue@hostbridge{within(5s)}; -event ereport.io.sch.nodiag@hostbridge; - -/* - * Upset used to hide ereports that can not be currently diagnosed. - * - * The drue error can cause a target abort to be sent onto the - * pci bus in response to a dma request. We represent this using a device-ta - * error to propagate into the generic pci.esc rules. - */ -engine serd.io.sch.nodiag@hostbridge, - N=1000, T=1hour, method=persistent, - trip=ereport.io.sch.nodiag@hostbridge; - -event upset.io.sch.nodiag@hostbridge, - engine=serd.io.sch.nodiag@hostbridge; - -prop upset.io.sch.nodiag@hostbridge (0)-> - ereport.io.sch.ecc.s-pce@hostbridge, - error.io.sch.ecc.drue@hostbridge, - ereport.io.sch.nodiag@hostbridge; - -prop error.io.sch.ecc.drue@hostbridge (1)-> - ereport.io.sch.ecc.drue@hostbridge; - -prop error.io.sch.ecc.drue@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/tomatillo.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4u/tomatillo.esc deleted file mode 100644 index 3e3a15fe44..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/tomatillo.esc +++ /dev/null @@ -1,430 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2008 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -#pragma dictionary "SUN4U" - -#define HB_FIT 1000 -#define HBUS_FIT 1000 -#define PCI_BUS_FIT 500 -#define PCI_DEV_FIT 1000 -#define CPU_FIT 500 - -#define PCI_HB_DEV_PATH hostbridge/pcibus/pcidev[32]/pcifn[0] - -fru hostbridge; -asru hostbridge; - -event fault.io.tomatillo@hostbridge, - FITrate=HB_FIT, FRU=hostbridge, ASRU=hostbridge; - -event error.io.tom.jbus.um@hostbridge; -event error.io.tom.jbus.to@hostbridge; -event error.io.tom.jbus.bus@hostbridge; -event error.io.tom.jbus.iis@hostbridge; -event error.io.tom.mmu.inval@hostbridge/pcibus; -event error.io.tom.mmu.prot@hostbridge/pcibus; -event error.io.tom.mmu.bva@hostbridge/pcibus; -event error.io.tom.mmu.btt@hostbridge/pcibus; -event error.io.pci.device-ta@hostbridge/pcibus/pcidev/pcifn; - -event ereport.io.tom.jbus.um@hostbridge{within(5s)}; -event ereport.io.tom.jbus.to@hostbridge{within(5s)}; -event ereport.io.tom.jbus.bus@hostbridge{within(5s)}; -event ereport.io.tom.jbus.to-exp@hostbridge{within(5s)}; -event ereport.io.tom.jbus.iis@hostbridge{within(5s)}; -event ereport.io.tom.mmu.btt@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.mmu.bva@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.mmu.prot@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.mmu.inval@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.jbus.srds@hostbridge{within(5s)}; -event ereport.io.tom.jbus.srdsa@hostbridge{within(5s)}; -event ereport.io.tom.jbus.sown@hostbridge{within(5s)}; -event ereport.io.tom.jbus.srdo@hostbridge{within(5s)}; - -/* - * A faulty Tomatillo hostbridge may cause: - * - * - um: jbus unmapped address error. - * - to: jbus timeout. - * - bus: jbus bus error. - * - iis: illegal coherency install state error. - * - inval: iommu invalid entry error. - * - prot: iommu protection error, attempted to write a read-only page. - * - bva: iommu bad virtual address, address out of range. - * - btt: iommu bad tsb size tbw size combination. - * - srds: snoop error due to own RDS hitting cache line in S, O or M. - * - srdsa: snoop error due to own RDSA hitting cache line in S, O or M. - * - sown: snoop error due to own OWN hitting cache line in S or M. - * - srdo: snoop error due to own RDO hitting cache line in O or M. - * - * The um, to, bus, btt, inval, prot and bva errors can cause a target abort to - * be sent onto the pci bus in response to a dma request. We represent this - * using a device-ta error to propagate into the generic pci.esc rules. - */ -prop fault.io.tomatillo@hostbridge (0)-> - error.io.tom.jbus.um@hostbridge, - error.io.tom.jbus.to@hostbridge, - error.io.tom.jbus.bus@hostbridge, - error.io.tom.jbus.iis@hostbridge, - error.io.tom.mmu.inval@hostbridge/pcibus, - error.io.tom.mmu.prot@hostbridge/pcibus, - error.io.tom.mmu.bva@hostbridge/pcibus, - error.io.tom.mmu.btt@hostbridge/pcibus, - ereport.io.tom.jbus.srds@hostbridge, - ereport.io.tom.jbus.srdsa@hostbridge, - ereport.io.tom.jbus.sown@hostbridge, - ereport.io.tom.jbus.srdo@hostbridge; - -prop error.io.tom.jbus.um@hostbridge (1)-> - ereport.io.tom.jbus.um@hostbridge; - -prop error.io.tom.jbus.um@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.tom.jbus.to@hostbridge (1)-> - ereport.io.tom.jbus.to@hostbridge, - ereport.io.tom.jbus.to-exp@hostbridge; - -prop error.io.tom.jbus.to@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.tom.jbus.bus@hostbridge (1)-> - ereport.io.tom.jbus.bus@hostbridge; - -prop error.io.tom.jbus.bus@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.tom.jbus.iis@hostbridge (1)-> - ereport.io.tom.jbus.iis@hostbridge; - -prop error.io.tom.mmu.btt@hostbridge/pcibus (1)-> - ereport.io.tom.mmu.btt@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.btt@hostbridge/pcibus (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH, - error.io.tom.mmu.inval@hostbridge/pcibus; - -prop error.io.tom.mmu.inval@hostbridge/pcibus (1)-> - ereport.io.tom.mmu.inval@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.inval@hostbridge/pcibus (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.prot@hostbridge/pcibus (1)-> - ereport.io.tom.mmu.prot@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.prot@hostbridge/pcibus (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.bva@hostbridge/pcibus (1)-> - ereport.io.tom.mmu.bva@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.bva@hostbridge/pcibus (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -fru cpu; - -event fault.io.datapath@cpu, FITrate=CPU_FIT, FRU=cpu, retire=0; - -event error.io.tom.jbus.ibe@hostbridge; - -event ereport.io.tom.jbus.ibe@hostbridge{within(5s)}; -event ereport.io.tom.jbus.srd@hostbridge{within(5s)}; -event ereport.io.tom.jbus.bc@hostbridge{within(5s)}; - -/* - * A faulty CPU may cause: - * - * - to: jbus timeout error. - * - bus: jbus bus error. - * - ibe: illegal byte enable error. - * - iis: illegal coherency install state error. - * - um: jbus unmapped error. - * - srd: foreign RD hitting cache line in S, O or M. - * - bc: bad jbus command. - * - * The ibe error can cause a target abort to - * be sent onto the pci bus in response to a dma request. We represent this - * using a device-ta error to propagate into the generic pci.esc rules. - */ -prop fault.io.datapath@cpu (0)-> - error.io.tom.jbus.to@hostbridge, - error.io.tom.jbus.bus@hostbridge, - error.io.tom.jbus.ibe@hostbridge, - error.io.tom.jbus.iis@hostbridge, - error.io.tom.jbus.um@hostbridge, - ereport.io.tom.jbus.srd@hostbridge, - ereport.io.tom.jbus.bc@hostbridge; - -prop error.io.tom.jbus.ibe@hostbridge (1)-> - ereport.io.tom.jbus.ibe@hostbridge; - -prop error.io.tom.jbus.ibe@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -event fault.io.hbus@hostbridge, - FITrate=HBUS_FIT, FRU=hostbridge, ASRU=hostbridge; - -event error.io.tom.jbus.drpe@hostbridge; -event ereport.io.tom.jbus.ape@hostbridge{within(5s)}; -event ereport.io.tom.jbus.pwpe@hostbridge{within(5s)}; -event ereport.io.tom.jbus.drpe@hostbridge{within(5s)}; -event ereport.io.tom.jbus.dwpe@hostbridge{within(5s)}; -event ereport.io.tom.jbus.cpe@hostbridge{within(5s)}; - -/* - * A faulty host bus may cause: - * - * - ape: jbus address parity error. - * - pwpe: jbus PIO write parity error. - * - drpe: jbus DMA read parity error. - * - dwpe: jbus DMA write parity error. - * - cpe: jbus control parity error. - * - * The drpe error can cause a target abort to - * be sent onto the pci bus in response to a dma request. We represent this - * using a device-ta error to propagate into the generic pci.esc rules. - */ -prop fault.io.hbus@hostbridge(0)-> - ereport.io.tom.jbus.ape@hostbridge, - ereport.io.tom.jbus.pwpe@hostbridge, - error.io.tom.jbus.drpe@hostbridge, - ereport.io.tom.jbus.dwpe@hostbridge, - ereport.io.tom.jbus.cpe@hostbridge; - -prop error.io.tom.jbus.drpe@hostbridge(1)-> - ereport.io.tom.jbus.drpe@hostbridge; - -prop error.io.tom.jbus.drpe@hostbridge(0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -fru pcibus/pcidev; -asru pcibus/pcidev/pcifn; - -event fault.io.pci.device-interr@hostbridge/pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, FRU=pcibus/pcidev, ASRU=pcibus/pcidev/pcifn; - -event fault.io.pci.device-interr@pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, FRU=pcibus/pcidev, ASRU=pcibus/pcidev/pcifn; - -event error.io.tom.pbm.rl@hostbridge/pcibus/pcidev/pcifn; -event error.io.tom.pbm.rl@pcibus/pcidev/pcifn; -event error.io.tom.pbm.rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.io.tom.pbm.target-rl@pcibus/pcidev/pcifn; -event error.io.tom.pbm.target-rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.io.tom.pbm.tto@hostbridge/pcibus/pcidev/pcifn; -event error.io.tom.pbm.target-tto@hostbridge/pcibus/pcidev/pcifn; -event error.io.tom.pbm.target-tto@pcibus/pcidev/pcifn; -event error.io.tom.pbm.target-tto@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.tom.cpu.berr@cpu; -event error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.perr-pw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.perr-dw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.retry-to-d@hostbridge/pcibus/pcidev/pcifn; - -event ereport.io.tom.pbm.tto@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.pbm.rl@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.pbm.s-tto@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.pbm.s-rl@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.pbm.s-ma@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.pbm.s-rta@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.pbm.s-mdpe@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.pbm.target-tto@pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.pbm.target-rl@pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.pci.rserr@hostbridge/pcibus/pcidev/pcifn{within(5s)}; - -/* - * A faulty PCI device may cause: - * - * - rl: it to exceed the limit on retrying a transaction. - * - tto: it to not assert trdy# within the set timeout. - * - * For rl and tto, there may be a target- ereport on a child device. For rl, - * there may also be an associated dto - the retry-to-d error propagates into - * the pci.esc rules to handle this. - */ -prop fault.io.pci.device-interr@pcibus/pcidev[fromdev]/pcifn (0)-> - error.io.tom.pbm.rl@pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }, - error.io.tom.pbm.target-rl@pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }; - -prop error.io.tom.pbm.rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn (1)-> - error.io.tom.pbm.rl@pcibus/pcidev/pcifn; - -prop error.io.tom.pbm.rl@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.tom.pbm.rl@PCI_HB_DEV_PATH, - ereport.io.tom.pbm.s-rl@PCI_HB_DEV_PATH; - -prop error.io.tom.pbm.target-rl@pcibus/pcidev/pcifn (1)-> - error.io.tom.pbm.target-rl@pcibus/pcidev/pcifn/pcibus<>/pcidev<>/pcifn<>; - -prop error.io.tom.pbm.target-rl@pcibus/pcidev/pcifn (0)-> - ereport.io.tom.pbm.target-rl@pcibus/pcidev/pcifn; - -prop error.io.tom.pbm.rl@hostbridge/pcibus/pcidev/pcifn (0)-> - error.tom.cpu.berr@cpu; - -prop error.io.tom.pbm.rl@hostbridge/pcibus/pcidev/pcifn (0)-> - error.io.pci.retry-to-d@hostbridge/pcibus/pcidev/pcifn; - -prop fault.io.pci.device-interr@hostbridge/pcibus/pcidev[fromdev]/pcifn (0)-> - error.io.tom.pbm.tto@hostbridge/pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32}; - -prop error.io.tom.pbm.tto@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.tom.pbm.tto@PCI_HB_DEV_PATH, - ereport.io.tom.pbm.s-tto@PCI_HB_DEV_PATH; - -prop error.io.tom.pbm.tto@hostbridge/pcibus/pcidev/pcifn (1)-> - error.io.tom.pbm.target-tto@hostbridge/pcibus/pcidev/pcifn; - -prop error.io.tom.pbm.target-tto@pcibus/pcidev/pcifn (0)-> - ereport.io.tom.pbm.target-tto@pcibus/pcidev/pcifn; - -prop error.io.tom.pbm.target-tto@pcibus/pcidev/pcifn (1)-> - error.io.tom.pbm.target-tto@pcibus/pcidev/pcifn/pcibus<>/pcidev<>/pcifn<>; - -/* - * Need to add the following tomatillo specific propagations to complete the - * fault tree. These are to allow propagations to secondary errors and cpu - * bus errors, and to represent the way the chip raises rserr - * on detection of SERR# - */ -prop error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.tom.pbm.s-ma@PCI_HB_DEV_PATH; - -prop error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.tom.pbm.s-rta@PCI_HB_DEV_PATH; - -prop error.io.pci.perr-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.tom.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.perr-dw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.tom.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.tom.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.tom.cpu.berr@cpu; - -prop error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.tom.cpu.berr@cpu; - -prop error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.tom.cpu.berr@cpu; - -prop error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.pci.rserr@PCI_HB_DEV_PATH; - -event ereport.cpu.ultraSPARC-IIIi.berr@cpu{within(5s)}; - -prop error.tom.cpu.berr@cpu (1)-> - ereport.cpu.ultraSPARC-IIIi.berr@cpu; - -/* - * A bad request from a downstream device/driver may cause - * - * - inval: iommu invalid entry error. - * - prot: iommu protection error, attempted to write a read-only page. - * - bva: iommu bad virtual address, address out of range. - * - btt: iommu bad tsb size tbw size combination. - */ -event error.io.pci.badreq-pw-u@hostbridge/pcibus/pcidev/pcifn; - -prop error.io.pci.badreq-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.tom.mmu.inval@PCI_HB_DEV_PATH, - ereport.io.tom.mmu.prot@PCI_HB_DEV_PATH, - ereport.io.tom.mmu.bva@PCI_HB_DEV_PATH, - ereport.io.tom.mmu.btt@PCI_HB_DEV_PATH; - -event error.io.pci.badreq-drw-u@hostbridge/pcibus/pcidev/pcifn; - -prop error.io.pci.badreq-drw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.tom.mmu.inval@PCI_HB_DEV_PATH, - ereport.io.tom.mmu.prot@PCI_HB_DEV_PATH, - ereport.io.tom.mmu.bva@PCI_HB_DEV_PATH, - ereport.io.tom.mmu.btt@PCI_HB_DEV_PATH; - -event error.io.tom.ecc.drue@hostbridge; -event error.io.tom.mmu.ue@hostbridge/pcibus; -event error.io.tom.mmu.to@hostbridge/pcibus; -event ereport.io.tom.jbus.sgr@hostbridge{within(5s)}; -event ereport.io.tom.jbus.spci@hostbridge{within(5s)}; -event ereport.io.tom.jbus.snp@hostbridge{within(5s)}; -event ereport.io.tom.ecc.drue@hostbridge{within(5s)}; -event ereport.io.tom.mmu.ue@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.tom.mmu.to@hostbridge/pcibus/pcidev/pcifn{within(5s)}; - -event ereport.io.tom.nodiag@hostbridge; - -/* - * Upset used to hide ereports that can not be currently diagnosed. - * - * The ue, to and drue errors can cause a target abort to - * be sent onto the pci bus in response to a dma request. We represent this - * using a device-ta error to propagate into the generic pci.esc rules. - */ -engine serd.io.tom.nodiag@hostbridge, - N=1000, T=1hour, method=persistent, - trip=ereport.io.tom.nodiag@hostbridge; - -event upset.io.tom.nodiag@hostbridge, - engine=serd.io.tom.nodiag@hostbridge; - -prop upset.io.tom.nodiag@hostbridge (0)-> - ereport.io.tom.jbus.sgr@hostbridge, - ereport.io.tom.jbus.spci@hostbridge, - ereport.io.tom.jbus.snp@hostbridge, - ereport.io.tom.nodiag@hostbridge; - -prop upset.io.tom.nodiag@hostbridge (0)-> - error.io.tom.ecc.drue@hostbridge, - error.io.tom.mmu.to@hostbridge/pcibus, - error.io.tom.mmu.ue@hostbridge/pcibus; - -prop error.io.tom.mmu.ue@hostbridge/pcibus (1)-> - ereport.io.tom.mmu.ue@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.ue@hostbridge/pcibus (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.to@hostbridge/pcibus (1)-> - ereport.io.tom.mmu.to@PCI_HB_DEV_PATH; - -prop error.io.tom.mmu.to@hostbridge/pcibus (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.tom.ecc.drue@hostbridge (1)-> - ereport.io.tom.ecc.drue@hostbridge; - -prop error.io.tom.ecc.drue@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/xmits.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4u/xmits.esc deleted file mode 100644 index 51217ef94d..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4u/xmits.esc +++ /dev/null @@ -1,449 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2008 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -#pragma dictionary "SUN4U" - -#define AGENT_ID_MASK 0x1f -#define AGENT_ID_SHIFT 24 - -#define HB_FIT 1000 -#define HBUS_FIT 1000 -#define PCI_BUS_FIT 500 -#define PCI_DEV_FIT 1000 -#define CPU_FIT 500 - -#define PCI_HB_DEV_PATH hostbridge/pcibus/pcidev[32]/pcifn[0] - -fru hostbridge; -asru hostbridge; - -event fault.io.xmits@hostbridge, - FITrate=HB_FIT, FRU=hostbridge, ASRU=hostbridge; - -event error.io.xmits.saf.dstat@hostbridge; -event error.io.xmits.saf.to@hostbridge; -event error.io.xmits.saf.bus@hostbridge; -event error.io.xmits.ecc.thresh@hostbridge; -event error.io.pci.device-ta@hostbridge/pcibus/pcidev/pcifn; - -event ereport.io.xmits.saf.ape@hostbridge{within(5s)}; -event ereport.io.xmits.saf.to@hostbridge{within(5s)}; -event ereport.io.xmits.saf.bus@hostbridge{within(5s)}; -event ereport.io.xmits.saf.bca@hostbridge{within(5s)}; -event ereport.io.xmits.saf.bcb@hostbridge{within(5s)}; -event ereport.io.xmits.saf.ciq-to@hostbridge{within(5s)}; -event ereport.io.xmits.saf.lpq-to@hostbridge{within(5s)}; -event ereport.io.xmits.saf.sfpq-to@hostbridge{within(5s)}; -event ereport.io.xmits.ecc.pce@hostbridge{within(5s)}; -event ereport.io.xmits.ecc.pue@hostbridge{within(5s)}; -event ereport.io.xmits.ecc.s-pce@hostbridge{within(5s)}; -event ereport.io.xmits.ecc.s-pue@hostbridge{within(5s)}; -event ereport.io.xmits.saf.para@hostbridge{within(5s)}; -event ereport.io.xmits.saf.parb@hostbridge{within(5s)}; -event ereport.io.xmits.saf.pars@hostbridge{within(5s)}; -event ereport.io.xmits.saf.plla@hostbridge{within(5s)}; -event ereport.io.xmits.saf.pllb@hostbridge{within(5s)}; -event ereport.io.xmits.saf.plls@hostbridge{within(5s)}; -event ereport.io.xmits.ecc.thresh@hostbridge{within(5s)}; -event ereport.io.xmits.saf.dstat@hostbridge{within(5s)}; -event ereport.io.xmits.pbmx.stdst@PCI_HB_DEV_PATH{within(5s)}; -event ereport.io.xmits.pbmx.cndst@PCI_HB_DEV_PATH{within(5s)}; -event ereport.io.xmits.pbmx.tato@PCI_HB_DEV_PATH{within(5s)}; -event ereport.io.xmits.pbmx.stmmu@PCI_HB_DEV_PATH{within(5s)}; -event ereport.io.xmits.pbmx.cnmmu@PCI_HB_DEV_PATH{within(5s)}; - -/* - * A faulty Xmits hostbridge may cause: - * - * - para: a parity error on the internal memories of PCI block A. - * - parb: a parity error on the internal memories of PCI block B. - * - pars: a parity error on the internal memories of the Safari block. - * - plla: a PLL lock error on the PCIA Leaf PLL. - * - pllb: a PLL lock error on the PCIB Leaf PLL. - * - plls: a PLL lock error on the Safari block PLL. - * - stdst a streaming DMA split completion encounters a DSTAT error - * - cndst a consistant DMA split completion encounters a DSTAT error - * - bca: bad safari command from PCI block A. - * - bcb: bad safari command from PCI block B. - * - ciq-to: coherent input queue timeout. - * - lpq-to: local PIO queue timeout. - * - sfpq-to: safari foreign PIO queue timeout. - * - ape: address parity error. - * - pue: PIO uncorrectable error, bad reader. - * - s-pue: secondary PIO UE, bad reader. - * - ecc: multiple PIO CEs. - * - to: safari bus timeout. - * - bus: safari bus error. - * - dstat: errant dstat on incoming data. - * - * The to, bus and dstat errors can cause a target abort to be sent onto the - * pci bus in response to a dma request. We represent this using a device-ta - * error to propagate into the generic pci.esc rules. - */ -prop fault.io.xmits@hostbridge (0)-> - ereport.io.xmits.saf.para@hostbridge, - ereport.io.xmits.saf.parb@hostbridge, - ereport.io.xmits.saf.pars@hostbridge, - ereport.io.xmits.saf.plla@hostbridge, - ereport.io.xmits.saf.pllb@hostbridge, - ereport.io.xmits.saf.plls@hostbridge, - ereport.io.xmits.saf.bca@hostbridge, - ereport.io.xmits.saf.bcb@hostbridge, - ereport.io.xmits.saf.ciq-to@hostbridge, - ereport.io.xmits.saf.lpq-to@hostbridge, - ereport.io.xmits.saf.sfpq-to@hostbridge, - ereport.io.xmits.saf.ape@hostbridge, - ereport.io.xmits.ecc.pue@hostbridge, - ereport.io.xmits.ecc.s-pue@hostbridge, - ereport.io.xmits.pbmx.stdst@PCI_HB_DEV_PATH, - ereport.io.xmits.pbmx.cndst@PCI_HB_DEV_PATH, - error.io.xmits.ecc.thresh@hostbridge, - error.io.xmits.saf.to@hostbridge, - error.io.xmits.saf.bus@hostbridge, - error.io.xmits.saf.dstat@hostbridge; - -prop error.io.xmits.ecc.thresh@hostbridge (2)-> - ereport.io.xmits.ecc.thresh@hostbridge, - ereport.io.xmits.ecc.pce@hostbridge; - -prop error.io.xmits.saf.to@hostbridge (2)-> - ereport.io.xmits.saf.to@hostbridge, - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.xmits.saf.bus@hostbridge (2)-> - ereport.io.xmits.saf.bus@hostbridge, - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -prop error.io.xmits.saf.dstat@hostbridge (1)-> - ereport.io.xmits.saf.dstat@hostbridge; - -prop error.io.xmits.saf.dstat@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; - -engine serd.io.xmits.ecc@hostbridge, - N=3, T=1day, method=persistent, - trip=ereport.io.xmits.ecc.thresh@hostbridge; - -event upset.io.xmits@hostbridge, - engine=serd.io.xmits.ecc@hostbridge; - -/* - * An upset xmits may cause: - * - * - pce: PIO correctable error. - */ -prop upset.io.xmits@hostbridge (0)-> - ereport.io.xmits.ecc.pce@hostbridge; - -fru cpu; - -event fault.io.datapath@cpu, FITrate=CPU_FIT, FRU=cpu, retire=0; - -event error.io.cpu.ecc.thresh@cpu; -event ereport.io.xmits.saf.ssm-dis@hostbridge{within(5s)}; - -/* - * A faulty CPU may cause: - * - * - to: safari bus timeout. - * - bus: safari bus error. - * - dstat: incorrect dstat sent to hostbridge. - * - ssm-dis: ssm command sent to hostbridge when not enabled. - * - ape: safari address parity error. - * - pue: PIO uncorrectable error. - * - ecc: multiple PIO CEs. - */ -prop fault.io.datapath@cpu (0)-> - error.io.xmits.saf.to@hostbridge, - error.io.xmits.saf.bus@hostbridge, - error.io.xmits.saf.dstat@hostbridge, - ereport.io.xmits.saf.ssm-dis@hostbridge, - ereport.io.xmits.saf.ape@hostbridge; - -prop fault.io.datapath@cpu[cpuid] (0)-> - ereport.io.xmits.ecc.pue@hostbridge - {((payloadprop("ecc-afsr") >> AGENT_ID_SHIFT) & AGENT_ID_MASK) == cpuid}; - -prop fault.io.datapath@cpu (0)-> - error.io.cpu.ecc.thresh@cpu; - -prop error.io.cpu.ecc.thresh@cpu (1)-> - ereport.io.xmits.ecc.thresh@hostbridge<>; - -prop error.io.cpu.ecc.thresh@cpu[cpuid] (1)-> - ereport.io.xmits.ecc.pce@hostbridge<> - {((payloadprop("ecc-afsr") >> AGENT_ID_SHIFT) & AGENT_ID_MASK) == cpuid}; - -event fault.io.hbus@hostbridge, - FITrate=HBUS_FIT, FRU=hostbridge, ASRU=hostbridge; - -/* - * A faulty host bus may cause: - * - * - ape: address parity error. - * - pue: PIO uncorrectable error. - * - s-pue: secondary PIO UE. - * - ecc: multiple PIO CEs. - */ -prop fault.io.hbus@hostbridge (0)-> - ereport.io.xmits.saf.ape@hostbridge, - ereport.io.xmits.ecc.pue@hostbridge, - ereport.io.xmits.ecc.s-pue@hostbridge, - error.io.xmits.ecc.thresh@hostbridge; - -/* - * A defective PCI driver may cause: - * - * - um: safari unmapped address error. - * - mmu: a iommu translation error. - */ -event error.io.pci.badreq-pw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.badreq-drw-u@hostbridge/pcibus/pcidev/pcifn; - -event ereport.io.xmits.mmu@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.saf.um@hostbridge{within(5s)}; -event ereport.io.pci.rserr@hostbridge/pcibus/pcidev/pcifn{within(5s)}; - -prop error.io.pci.badreq-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.saf.um@hostbridge; - -prop error.io.pci.badreq-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.mmu@PCI_HB_DEV_PATH; - -prop error.io.pci.badreq-drw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.saf.um@hostbridge; - -prop error.io.pci.badreq-drw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.mmu@PCI_HB_DEV_PATH; - -event defect.io.pci.driver@hostbridge; - -/* - * A defective PCI nexus driver may cause: - * - * - stmmu: A streaming DMA split completion transaction - * encounters an MMU error. - * - cnmmu: A consistant DMA split completion transaction - * encounters an MMU error. - */ -prop defect.io.pci.driver@hostbridge (0)-> - ereport.io.xmits.pbmx.stmmu@PCI_HB_DEV_PATH, - ereport.io.xmits.pbmx.cnmmu@PCI_HB_DEV_PATH; - -fru pcibus; -asru pcibus; - -event fault.io.pci.bus@hostbridge/pcibus, - FITrate=PCI_BUS_FIT, FRU=pcibus, ASRU=pcibus; - -event ereport.io.xmits.bu@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.s-bu@hostbridge/pcibus/pcidev/pcifn{within(5s)}; - -/* - * A faulty PCI bus may cause: - * - * - bu: PCI bus unusable error. - * - s-bu: secondary PCI bus unusable error. - * - tato: DMA split completion target timeout error - */ -prop fault.io.pci.bus@hostbridge/pcibus (0)-> - ereport.io.xmits.bu@PCI_HB_DEV_PATH, - ereport.io.xmits.s-bu@PCI_HB_DEV_PATH, - ereport.io.xmits.pbmx.tato@PCI_HB_DEV_PATH; - -fru pcibus/pcidev; -asru pcibus/pcidev/pcifn; - -event fault.io.pci.device-interr@hostbridge/pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, FRU=pcibus/pcidev, ASRU=pcibus/pcidev/pcifn; - -event fault.io.pci.device-interr@pcibus/pcidev/pcifn, - FITrate=PCI_DEV_FIT, FRU=pcibus/pcidev, ASRU=pcibus/pcidev/pcifn; - -event error.io.xmits.pbm.rl@hostbridge/pcibus/pcidev/pcifn; -event error.io.xmits.pbm.rl@pcibus/pcidev/pcifn; -event error.io.xmits.pbm.rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.io.xmits.pbm.target-rl@pcibus/pcidev/pcifn; -event error.io.xmits.pbm.target-rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.io.xmits.pbm.tto@hostbridge/pcibus/pcidev/pcifn; -event error.io.xmits.pbm.target-tto@hostbridge/pcibus/pcidev/pcifn; -event error.io.xmits.pbm.target-tto@pcibus/pcidev/pcifn; -event error.io.xmits.pbm.target-tto@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn; -event error.xmits.cpu.berr@cpu; -event error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.perr-pw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.perr-dw-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn; -event error.io.pci.retry-to-d@hostbridge/pcibus/pcidev/pcifn; - -event ereport.io.xmits.sbh@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.rl@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.tto@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.s-rl@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.s-tto@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.s-ma@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.s-rta@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.s-mdpe@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.target-rl@pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.xmits.pbm.target-tto@pcibus/pcidev/pcifn{within(5s)}; -event ereport.io.pci.sserr@hostbridge/pcibus/pcidev/pcifn{within(5s)}; -event ereport.cpu.ultraSPARC-III.berr@cpu{within(5s)}; -event ereport.cpu.ultraSPARC-IIIplus.berr@cpu{within(5s)}; -event ereport.cpu.ultraSPARC-IV.berr@cpu{within(5s)}; -event ereport.cpu.ultraSPARC-IVplus.berr@cpu{within(5s)}; - -/* - * A faulty PCI device may cause: - * - * - sbh: a streaming byte hole error. - * - rl: it to exceed the number retriesfor a transaction. - * - tto: it to not assert trdy# within the alloted timeout. - * - * For rl and tto, there may be a target- ereport on a child device. For rl, - * there may also be an associated dto - the retry-to-d error propagates into - * the pci.esc rules to handle this. - */ -prop fault.io.pci.device-interr@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.sbh@PCI_HB_DEV_PATH; - -prop fault.io.pci.device-interr@pcibus/pcidev[fromdev]/pcifn (0)-> - error.io.xmits.pbm.rl@pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }, - error.io.xmits.pbm.target-rl@pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }; - -prop error.io.xmits.pbm.rl@pcibus/pcidev/pcifn/pcibus/pcidev/pcifn (1)-> - error.io.xmits.pbm.rl@pcibus/pcidev/pcifn; - -prop error.io.xmits.pbm.rl@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.xmits.pbm.rl@PCI_HB_DEV_PATH, - ereport.io.xmits.pbm.s-rl@PCI_HB_DEV_PATH; - -prop error.io.xmits.pbm.target-rl@pcibus/pcidev/pcifn (1)-> - error.io.xmits.pbm.target-rl@pcibus/pcidev/pcifn/pcibus<>/pcidev<>/pcifn<>; - -prop error.io.xmits.pbm.target-rl@pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.pbm.target-rl@pcibus/pcidev/pcifn; - -prop error.io.xmits.pbm.rl@hostbridge/pcibus/pcidev/pcifn (0)-> - error.io.pci.retry-to-d@hostbridge/pcibus/pcidev/pcifn; - -prop error.io.xmits.pbm.rl@hostbridge/pcibus/pcidev/pcifn (0)-> - error.xmits.cpu.berr@cpu; - -prop fault.io.pci.device-interr@hostbridge/pcibus/pcidev[fromdev]/pcifn (0)-> - error.io.xmits.pbm.tto@hostbridge/pcibus/pcidev/pcifn { - fromdev == todev && fromdev != 32 }; - -prop error.io.xmits.pbm.tto@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.xmits.pbm.tto@PCI_HB_DEV_PATH, - ereport.io.xmits.pbm.s-tto@PCI_HB_DEV_PATH; - -prop error.io.xmits.pbm.tto@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.xmits.bu@PCI_HB_DEV_PATH; - -prop error.io.xmits.pbm.tto@hostbridge/pcibus/pcidev/pcifn (1)-> - error.io.xmits.pbm.target-tto@hostbridge/pcibus/pcidev/pcifn; - -prop error.io.xmits.pbm.target-tto@pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.pbm.target-tto@pcibus/pcidev/pcifn; - -prop error.io.xmits.pbm.target-tto@pcibus/pcidev/pcifn (1)-> - error.io.xmits.pbm.target-tto@pcibus/pcidev/pcifn/pcibus<>/pcidev<>/pcifn<>; - -/* - * Need to add the following xmits specific propagations to complete the PCI - * fault tree. These are to allow propagations to secondary errors and cpu - * bus errors, and to represent the way the chip can raise both rserr and sserr - * on detection of SERR# - */ -prop error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.pbm.s-ma@PCI_HB_DEV_PATH; - -prop error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.pbm.s-rta@PCI_HB_DEV_PATH; - -prop error.io.pci.perr-dw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.perr-pw-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.xmits.pbm.s-mdpe@PCI_HB_DEV_PATH; - -prop error.io.pci.ta-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.xmits.cpu.berr@cpu; - -prop error.io.pci.dpdata-dr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.xmits.cpu.berr@cpu; - -prop error.io.pci.ma-u@hostbridge/pcibus/pcidev/pcifn (0)-> - error.xmits.cpu.berr@cpu; - -prop error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn (1)-> - ereport.io.pci.rserr@PCI_HB_DEV_PATH; - -prop error.io.pci.serr-u@hostbridge/pcibus/pcidev/pcifn (0)-> - ereport.io.pci.sserr@PCI_HB_DEV_PATH; - -prop error.xmits.cpu.berr@cpu (1)-> - ereport.cpu.ultraSPARC-III.berr@cpu, - ereport.cpu.ultraSPARC-IIIplus.berr@cpu, - ereport.cpu.ultraSPARC-IV.berr@cpu, - ereport.cpu.ultraSPARC-IVplus.berr@cpu; - -event error.io.xmits.ecc.drue@hostbridge; -event ereport.io.xmits.ecc.drue@hostbridge{within(5s)}; -event ereport.io.xmits.nodiag@hostbridge; - -/* - * Upset used to hide ereports that can not be currently diagnosed. - * - * The drue error can cause a target abort to be sent onto the - * pci bus in response to a dma request. We represent this using a device-ta - * error to propagate into the generic pci.esc rules. - */ -engine serd.io.xmits.nodiag@hostbridge, - N=1000, T=1hour, method=persistent, - trip=ereport.io.xmits.nodiag@hostbridge; - -event upset.io.xmits.nodiag@hostbridge, - engine=serd.io.xmits.nodiag@hostbridge; - -prop upset.io.xmits.nodiag@hostbridge (0)-> - ereport.io.xmits.ecc.s-pce@hostbridge, - error.io.xmits.ecc.drue@hostbridge, - ereport.io.xmits.nodiag@hostbridge; - -prop error.io.xmits.ecc.drue@hostbridge (1)-> - ereport.io.xmits.ecc.drue@hostbridge; - -prop error.io.xmits.ecc.drue@hostbridge (0)-> - error.io.pci.device-ta@PCI_HB_DEV_PATH; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/Makefile b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/Makefile deleted file mode 100644 index f884926bd5..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/Makefile +++ /dev/null @@ -1,34 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2009 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -# - -include ../sun4/Makefile.sun4 - -EFT_PLAT= sun4v -SUN4VEFTFILES= n2piu.eft vfncx.eft n2niu_xaui.eft n2niu_xfp.eft zambezi.eft \ -gcpu.eft gmem.eft sp.eft -EFT_PLAT_FILES= $(SUN4VEFTFILES) $(SUN4EFTFILES) - -include ../../Makefile.com diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/gcpu.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/gcpu.esc deleted file mode 100644 index 696567d677..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/gcpu.esc +++ /dev/null @@ -1,515 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ - -/* - * Copyright 2010 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -/* - * eversholt rules for generic-sparc sparc cpu errors. - * - * Most propagations are generated by preprocessor macros. The event - * declarations are deliberately not part of the propagation macros - * so that we know we have full coverage - propagations defined without - * events, or events not used in propagations, will produce compiler - * whinges. - */ - -#define DIAGNOSE_ERPT (payloadprop_defined("diagnose") && \ - payloadprop("diagnose") != 0x0) - -#define SET_SERDT (!payloadprop_defined("serd_t") || \ - setserdt(payloadprop("serd_t"))) - -#define SET_SERDN (!payloadprop_defined("serd_n") || \ - setserdn(payloadprop("serd_n"))) - -#define SET_RATIO \ - ((payloadprop_defined("filter_ratio") && \ - payloadprop("filter_ratio") != 0x0) ? \ - (setserdincrement(payloadprop("filter_ratio"))) : 1) - -/* - * The ereport and fault events are declared at multiple levels: - * some set of @chip, @core, and @strand resources since this is - * a generic DE and must be flexible and handle present and future - * sun4v platforms. For example, one processor may have an L2 - * cache per chip, another may have an L2 per core. - * - * For UE errors, faults are produced immediately. - * - * For CE errors, the errors are put through a SERD engine. If - * the SERD engine trips, the fault is produced. SERD engine - * names are of the format: - * serd.cpu.generic-sparc. - * Ex: serd.cpu.generic-sparc.chipitlb - * SERD N/T values are set to default values, but can be - * overridden via the ereport or the eft.conf file. The - * order or precedence of the SERD N/T values is: - * - the 'serd_override' tunable via eft.conf - * - the 'serd_n' and 'serd_t' payload members in the - * incoming ereport - * - the built-in default values - * - * The increment rate of the SERD engines can also be - * controlled via the ereport payload using the 'filter_ratio' - * payload member. N in incremented by the value of - * 'filter_ratio' if the payload member is present, 1 otherwise. - */ -/* - * Ereport event for cpu errors - */ -#define ERPT_EVENT(level, leafclass) \ - event ereport.cpu.generic-sparc.leafclass@level { within(1s) } - -/* - * Ereports for uncorrectable cpu errors - */ -ERPT_EVENT(chip, itlb-uc); -ERPT_EVENT(core, itlb-uc); -ERPT_EVENT(strand, itlb-uc); -ERPT_EVENT(chip, dtlb-uc); -ERPT_EVENT(core, dtlb-uc); -ERPT_EVENT(strand, dtlb-uc); -ERPT_EVENT(chip, icache-uc); -ERPT_EVENT(core, icache-uc); -ERPT_EVENT(chip, dcache-uc); -ERPT_EVENT(core, dcache-uc); -ERPT_EVENT(chip, ireg-uc); -ERPT_EVENT(core, ireg-uc); -ERPT_EVENT(strand, ireg-uc); -ERPT_EVENT(chip, freg-uc); -ERPT_EVENT(core, freg-uc); -ERPT_EVENT(strand, freg-uc); -ERPT_EVENT(chip, mreg-uc); -ERPT_EVENT(core, mreg-uc); -ERPT_EVENT(strand, mreg-uc); -ERPT_EVENT(chip, l2data-uc); -ERPT_EVENT(core, l2data-uc); -ERPT_EVENT(chip, l2tagctl-uc); -ERPT_EVENT(core, l2tagctl-uc); -ERPT_EVENT(chip, l3data-uc); -ERPT_EVENT(core, l3data-uc); -ERPT_EVENT(chip, l3tagctl-uc); -ERPT_EVENT(core, l3tagctl-uc); -ERPT_EVENT(chip, int-mem-ue); -ERPT_EVENT(core, int-mem-ue); -ERPT_EVENT(strand, int-mem-ue); -ERPT_EVENT(chip, gchip-uc); -ERPT_EVENT(core, gcore-uc); -ERPT_EVENT(strand, gstrand-uc); - -/* - * Propagations for CPU UE errors - * A fault is produced immediately for a CPU UE errors. - */ -#define FLT_CPU_UE(level, erptleaf, fltleaf) \ - event fault.cpu.generic-sparc.fltleaf@level; \ - \ - prop fault.cpu.generic-sparc.fltleaf@level \ - { DIAGNOSE_ERPT } (0)-> \ - ereport.cpu.generic-sparc.erptleaf@level; \ - \ - event upset.cpu.generic-sparc.fltleaf@level; \ - \ - prop upset.cpu.generic-sparc.fltleaf@level \ - { !DIAGNOSE_ERPT } (0)-> \ - ereport.cpu.generic-sparc.erptleaf@level - - -FLT_CPU_UE(chip, itlb-uc, chip-uc); -FLT_CPU_UE(core, itlb-uc, core-uc); -FLT_CPU_UE(strand, itlb-uc, strand-uc); -FLT_CPU_UE(chip, dtlb-uc, chip-uc); -FLT_CPU_UE(core, dtlb-uc, core-uc); -FLT_CPU_UE(strand, dtlb-uc, strand-uc); -FLT_CPU_UE(chip, icache-uc, chip-uc); -FLT_CPU_UE(core, icache-uc, core-uc); -FLT_CPU_UE(chip, dcache-uc, chip-uc); -FLT_CPU_UE(core, dcache-uc, core-uc); -FLT_CPU_UE(chip, ireg-uc, chip-uc); -FLT_CPU_UE(core, ireg-uc, core-uc); -FLT_CPU_UE(strand, ireg-uc, strand-uc); -FLT_CPU_UE(chip, mreg-uc, chip-uc); -FLT_CPU_UE(core, mreg-uc, core-uc); -FLT_CPU_UE(strand, mreg-uc, strand-uc); -FLT_CPU_UE(chip, freg-uc, chip-uc); -FLT_CPU_UE(core, freg-uc, core-uc); -FLT_CPU_UE(strand, freg-uc, strand-uc); -FLT_CPU_UE(chip, l2data-uc, chip-uc); -FLT_CPU_UE(core, l2data-uc, core-uc); -FLT_CPU_UE(chip, l2tagctl-uc, chip-uc); -FLT_CPU_UE(core, l2tagctl-uc, core-uc); -FLT_CPU_UE(chip, l3data-uc, chip-uc); -FLT_CPU_UE(core, l3data-uc, core-uc); -FLT_CPU_UE(chip, l3tagctl-uc, chip-uc); -FLT_CPU_UE(core, l3tagctl-uc, core-uc); -FLT_CPU_UE(chip, gchip-uc, chip-uc); -FLT_CPU_UE(core, gcore-uc, core-uc); -FLT_CPU_UE(strand, gstrand-uc, strand-uc); - - - -#define FLT_CPU_UE_UNRETIRED(level, erptleaf, fltleaf) \ - event fault.cpu.generic-sparc.fltleaf@level, \ - retire=0; \ - \ - prop fault.cpu.generic-sparc.fltleaf@level \ - { DIAGNOSE_ERPT } (0)-> \ - ereport.cpu.generic-sparc.erptleaf@level; \ - \ - event upset.cpu.generic-sparc.fltleaf@level; \ - \ - prop upset.cpu.generic-sparc.fltleaf@level \ - { !DIAGNOSE_ERPT } (0)-> \ - ereport.cpu.generic-sparc.erptleaf@level - -FLT_CPU_UE_UNRETIRED(chip, int-mem-ue, chip-uc-nr); -FLT_CPU_UE_UNRETIRED(core, int-mem-ue, core-uc-nr); -FLT_CPU_UE_UNRETIRED(strand, int-mem-ue, strand-uc-nr); - -/* - * Ereport events for corectable errors. - */ -ERPT_EVENT(chip, itlb); -ERPT_EVENT(core, itlb); -ERPT_EVENT(strand, itlb); -ERPT_EVENT(chip, dtlb); -ERPT_EVENT(core, dtlb); -ERPT_EVENT(strand, dtlb); -ERPT_EVENT(chip, icache); -ERPT_EVENT(core, icache); -ERPT_EVENT(chip, dcache); -ERPT_EVENT(core, dcache); -ERPT_EVENT(chip, ireg); -ERPT_EVENT(core, ireg); -ERPT_EVENT(strand, ireg); -ERPT_EVENT(chip, freg); -ERPT_EVENT(core, freg); -ERPT_EVENT(strand, freg); -ERPT_EVENT(chip, mreg); -ERPT_EVENT(core, mreg); -ERPT_EVENT(strand, mreg); -ERPT_EVENT(chip, l2data); -ERPT_EVENT(core, l2data); -ERPT_EVENT(chip, l2tagctl); -ERPT_EVENT(core, l2tagctl); -ERPT_EVENT(chip, l3data); -ERPT_EVENT(core, l3data); -ERPT_EVENT(chip, l3tagctl); -ERPT_EVENT(core, l3tagctl); -ERPT_EVENT(chip, int-mem); -ERPT_EVENT(core, int-mem); -ERPT_EVENT(strand, int-mem); -ERPT_EVENT(chip, gchip); -ERPT_EVENT(core, gcore); -ERPT_EVENT(strand, gstrand); - -/* - * Propagations for CE errors - * Errors are serded and fault is generated when the SERD engine trips - * The serd name & the N & T values are set at the running time. - */ -engine serd.cpu.generic-sparc.core@core, N=8, T=1week; -engine serd.cpu.generic-sparc.strand@strand, N=8, T=1week; - - -#define FLT_CPU_CE(erptleaf, level, fltleaf, n, t) \ - \ - /* Simple fault event */ \ - event fault.cpu.generic-sparc.fltleaf@level, \ - engine=serd.cpu.generic-sparc.fltleaf@level; \ - \ - /* When the correctable engine trips, diagnose a fault */ \ - prop fault.cpu.generic-sparc.fltleaf@level \ - { DIAGNOSE_ERPT && setserdsuffix("erptleaf") && \ - setserdn(n) && setserdt(t) && SET_SERDN && \ - SET_SERDT && SET_RATIO } (0) -> \ - ereport.cpu.generic-sparc.erptleaf@level; \ - \ - event upset.cpu.generic-sparc.fltleaf@level; \ - \ - prop upset.cpu.generic-sparc.fltleaf@level \ - { !DIAGNOSE_ERPT } (0) -> \ - ereport.cpu.generic-sparc.erptleaf@level - -FLT_CPU_CE(itlb, core, core, 8, 1week); -FLT_CPU_CE(itlb, strand, strand, 8, 1week); -FLT_CPU_CE(dtlb, core, core, 8, 1week); -FLT_CPU_CE(dtlb, strand, strand, 8, 1week); -FLT_CPU_CE(icache, core, core, 8, 1week); -FLT_CPU_CE(dcache, core, core, 8, 1week); -FLT_CPU_CE(ireg, core, core, 8, 1week); -FLT_CPU_CE(ireg, strand, strand, 8, 1week); -FLT_CPU_CE(freg, core, core, 8, 1week); -FLT_CPU_CE(freg, strand, strand, 8, 1week); -FLT_CPU_CE(mreg, core, core, 8, 1week); -FLT_CPU_CE(mreg, strand, strand, 8, 1week); -FLT_CPU_CE(l2data, core, core, 8, 1week); -FLT_CPU_CE(l2tagctl, core, core, 8, 1week); -FLT_CPU_CE(l3data, core, core, 8, 1week); -FLT_CPU_CE(l3tagctl, core, core, 8, 1week); -FLT_CPU_CE(gcore, core, core, 8, 1week); -FLT_CPU_CE(gstrand, strand, strand, 8, 1week); - -engine serd.cpu.generic-sparc.chip-nr@chip, N=8, T=1week; -engine serd.cpu.generic-sparc.core-nr@core, N=8, T=1week; -engine serd.cpu.generic-sparc.strand-nr@strand, N=8, T=1week; - -#define FLT_CPU_CE_UNRETIRED(erptleaf, level, fltleaf, n, t) \ - \ - /* Simple fault event */ \ - event fault.cpu.generic-sparc.fltleaf@level, \ - retire=0, \ - engine=serd.cpu.generic-sparc.fltleaf@level; \ - \ - /* When the correctable engine trips, diagnose a fault */ \ - prop fault.cpu.generic-sparc.fltleaf@level \ - { DIAGNOSE_ERPT && setserdsuffix("erptleaf") && setserdn(n) && \ - setserdt(t) && SET_SERDN && SET_SERDT && SET_RATIO } (0) -> \ - ereport.cpu.generic-sparc.erptleaf@level; \ - \ - event upset.fault.cpu.generic-sparc.fltleaf@level; \ - \ - prop upset.fault.cpu.generic-sparc.fltleaf@level \ - { !DIAGNOSE_ERPT } (0)-> \ - ereport.cpu.generic-sparc.erptleaf@level - -FLT_CPU_CE_UNRETIRED(itlb, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(dtlb, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(icache, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(dcache, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(ireg, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(freg, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(mreg, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(l2data, chip, chip-nr, 8, 2h); -FLT_CPU_CE_UNRETIRED(l2tagctl, chip, chip-nr, 8, 2h); -FLT_CPU_CE_UNRETIRED(l3data, chip, chip-nr, 8, 2h); -FLT_CPU_CE_UNRETIRED(l3tagctl, chip, chip-nr, 8, 2h); -FLT_CPU_CE_UNRETIRED(gchip, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(int-mem, chip, chip-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(int-mem, core, core-nr, 8, 1week); -FLT_CPU_CE_UNRETIRED(int-mem, strand, strand-nr, 8, 1week); - -/* - * c2c-link-uc, c2c-prot-uc, c2c-failover errors - * The detector and sender are faulted immediately. - * If ereport does not have a sender, all chips are faulted - */ - -#define CONTAINS_SENDER (payloadprop_contains("sender", asru(chip))) -#define HAS_SENDER (payloadprop_defined("sender")) -#define HAS_C2C_FAULT(c) has_fault(c, "fault.cpu.generic-sparc.c2c") -#define CONTAINS_DET (payloadprop_contains("detector", asru(chip))) - -event ereport.cpu.generic-sparc.c2c-link-uc@chip { within(1s) }; -event ereport.cpu.generic-sparc.c2c-prot-uc@chip { within(1s) }; -event ereport.cpu.generic-sparc.c2c-failover@chip { within(1s) }; - -event fault.cpu.generic-sparc.c2c-uc@chip, retire=0; -event fault.cpu.generic-sparc.c2c-failover@chip, retire=0; -event upset.cpu.generic-sparc.c2c-uc@chip; -event upset.cpu.generic-sparc.c2c-failover@chip; - -prop fault.cpu.generic-sparc.c2c-uc@chip - { DIAGNOSE_ERPT && CONTAINS_SENDER } (0) -> - ereport.cpu.generic-sparc.c2c-link-uc@chip; - -prop fault.cpu.generic-sparc.c2c-uc@chip - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.c2c-link-uc@chip; - -prop fault.cpu.generic-sparc.c2c-uc@chip - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.c2c-link-uc@chip; - -prop fault.cpu.generic-sparc.c2c-uc@chip - { DIAGNOSE_ERPT && CONTAINS_SENDER } (0) -> - ereport.cpu.generic-sparc.c2c-prot-uc@chip; - -prop fault.cpu.generic-sparc.c2c-uc@chip - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.c2c-prot-uc@chip; - -prop fault.cpu.generic-sparc.c2c-uc@chip - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.c2c-prot-uc@chip; - -prop upset.cpu.generic-sparc.c2c-uc@chip - { !DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.c2c-prot-uc@chip, - ereport.cpu.generic-sparc.c2c-link-uc@chip; - -prop fault.cpu.generic-sparc.c2c-failover@chip - { DIAGNOSE_ERPT && CONTAINS_SENDER } (0) -> - ereport.cpu.generic-sparc.c2c-failover@chip; - -prop fault.cpu.generic-sparc.c2c-failover@chip - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.c2c-failover@chip; - -prop fault.cpu.generic-sparc.c2c-failover@chip - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.c2c-failover@chip; - -prop upset.cpu.generic-sparc.c2c-failover@chip - { !DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.c2c-failover@chip; - -/* - * c2c-link, c2c-prot. Errors are serded. When the serd trips, - * the detector & sender will be faulted. - * If ereport does not have a sender, all chips will be faulted - * If ereport sender or detector was faulted, discard ereport - */ -event ereport.cpu.generic-sparc.c2c-link@chip { within(1s) }; -event ereport.cpu.generic-sparc.c2c-prot@chip { within(1s) }; - -engine serd.cpu.generic-sparc.c2c@chip, N=120, T=30min; - -event fault.cpu.generic-sparc.c2c@chip, retire=0, - engine=serd.cpu.generic-sparc.c2c@chip; - -event upset.cpu.generic-sparc.c2c-link@chip; -event upset.cpu.generic-sparc.c2c_discard@chip; - -prop fault.cpu.generic-sparc.c2c@chip - { DIAGNOSE_ERPT && CONTAINS_SENDER - && !HAS_C2C_FAULT(asru(chip)) && !HAS_C2C_FAULT(payloadprop("detector")) - && setserdsuffix("link") && SET_SERDN - && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.c2c-link@chip; - -prop fault.cpu.generic-sparc.c2c@chip - { DIAGNOSE_ERPT && !HAS_C2C_FAULT(asru(chip)) - && !HAS_C2C_FAULT(payloadprop("sender")) - && setserdsuffix("link") && SET_SERDN - && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.c2c-link@chip; - -prop fault.cpu.generic-sparc.c2c@chip - { DIAGNOSE_ERPT && !HAS_SENDER && setserdsuffix("link") && - SET_SERDN && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.c2c-link@chip; - -prop fault.cpu.generic-sparc.c2c@chip - { DIAGNOSE_ERPT && CONTAINS_SENDER - && !HAS_C2C_FAULT(asru(chip)) && !HAS_C2C_FAULT(payloadprop("detector")) - && setserdsuffix("prot") && SET_SERDN - && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.c2c-prot@chip; - -prop fault.cpu.generic-sparc.c2c@chip - { DIAGNOSE_ERPT && !HAS_C2C_FAULT(asru(chip)) - && !HAS_C2C_FAULT(payloadprop("sender")) - && setserdsuffix("prot") && SET_SERDN - && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.c2c-prot@chip; - -prop fault.cpu.generic-sparc.c2c@chip - { DIAGNOSE_ERPT && !HAS_SENDER && setserdsuffix("prot") && - SET_SERDN && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.c2c-prot@chip; - -prop upset.cpu.generic-sparc.c2c-link@chip - { !DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.c2c-prot@chip, - ereport.cpu.generic-sparc.c2c-link@chip; - -prop upset.cpu.generic-sparc.c2c_discard@chip (0) -> - ereport.cpu.generic-sparc.c2c-link@chip, - ereport.cpu.generic-sparc.c2c-prot@chip; - -/* - * addr-oob is a firmware error - there is no associated FRU/ASRU - * and firmware is not represented in topology. Rather than ignore - * the error, the DE generates a defect with no FRU or ASRU. It - * is generated @chassis so no location (label) is picked up out - * of the topology. The associated knowledge article can instruct - * users what steps to take to address the error. - */ -fru NULL; -asru NULL; - -event ereport.cpu.generic-sparc.addr-oob@chassis; -event defect.fw.generic-sparc.addr-oob@chassis, - ASRU=NULL, - FRU=NULL; -event upset.fw.generic-sparc.addr-oob@chassis; - -prop defect.fw.generic-sparc.addr-oob@chassis - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.addr-oob@chassis; - -prop upset.fw.generic-sparc.addr-oob@chassis - { !DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.addr-oob@chassis; - -event ereport.cpu.generic-sparc.inconsistent@chassis; -event defect.fw.generic-sparc.erpt-gen@chassis, - ASRU=NULL, - FRU=NULL; -event upset.fw.generic-sparc.erpt-gen@chassis; - -prop defect.fw.generic-sparc.erpt-gen@chassis - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.inconsistent@chassis; - -prop upset.fw.generic-sparc.erpt-gen@chassis - { !DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.inconsistent@chassis; -/* - * bootbus-prot, bootbus-to and bootbus-par errors. Fault the detector. - */ -event ereport.cpu.generic-sparc.bootbus-to@chip; -event ereport.cpu.generic-sparc.bootbus-par@chip; -event ereport.cpu.generic-sparc.bootbus-prot@chip; -event upset.cpu.generic-sparc.bootbus@chip; - -event fault.cpu.generic-sparc.bootbus@chip, retire=0; - -prop fault.cpu.generic-sparc.bootbus@chip - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.bootbus-to@chip; - -prop fault.cpu.generic-sparc.bootbus@chip - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.bootbus-par@chip; - -prop fault.cpu.generic-sparc.bootbus@chip - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.bootbus-prot@chip; - -prop upset.cpu.generic-sparc.bootbus@chip - { !DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.bootbus-to@chip, - ereport.cpu.generic-sparc.bootbus-par@chip, - ereport.cpu.generic-sparc.bootbus-prot@chip; - -/* - * ignore the pio-read error. - */ -event ereport.cpu.generic-sparc.pio-read@chip; -event upset.cpu.generic-sparc.discard@chip; - -prop upset.cpu.generic-sparc.discard@chip (0) -> - ereport.cpu.generic-sparc.pio-read@chip; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/gmem.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/gmem.esc deleted file mode 100644 index 8c322272da..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/gmem.esc +++ /dev/null @@ -1,478 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ - -/* - * Copyright 2010 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#define DIAGNOSE_ERPT (payloadprop_defined("diagnose") && \ - payloadprop("diagnose") != 0x0) - -#define DIMMPATH dimm - -#define CONTAINS_DIMM (payloadprop_contains("resource", asru(DIMMPATH))) - -#define SET_ADDR (!payloadprop_defined("phys-addr") || \ - setpayloadprop("physaddr", payloadprop("phys-addr"))) - -#define SET_OFFSET (!payloadprop_defined("offset") || \ - setpayloadprop("offset",\ - payloadprop("offset"))) - -#define SET_SERDT (!payloadprop_defined("serd_t") || \ - setserdt(payloadprop("serd_t"))) - -#define SET_SERDN (!payloadprop_defined("serd_n") || \ - setserdn(payloadprop("serd_n"))) - -#define SET_RATIO \ - ((payloadprop_defined("filter_ratio") && \ - payloadprop("filter_ratio") != 0x0) ? \ - (setserdincrement(payloadprop("filter_ratio"))) : 1) - -/* - * fault.memory.generic-sparc.bank & fault.memory.generic-sparc.page - * are generated for memory ue error. - */ -#define MEMUE_ERPT(level) \ - event ereport.cpu.generic-sparc.mem-uc@level { within(1s)} - -MEMUE_ERPT(chip); -MEMUE_ERPT(core); -MEMUE_ERPT(strand); - -#define FLT_MEM_UE_BANK(level) \ - event fault.memory.bank@DIMMPATH; \ - \ - prop fault.memory.bank@DIMMPATH \ - { DIAGNOSE_ERPT && CONTAINS_DIMM } (0)-> \ - ereport.cpu.generic-sparc.mem-uc@level<>; \ - \ - event upset.memory.bank@DIMMPATH; \ - \ - prop upset.memory.bank@DIMMPATH \ - { !DIAGNOSE_ERPT } (0)-> \ - ereport.cpu.generic-sparc.mem-uc@level<> - -FLT_MEM_UE_BANK(chip); -FLT_MEM_UE_BANK(core); -FLT_MEM_UE_BANK(strand); - -#define FLT_MEM_UE_PAGE(level) \ - event fault.memory.page@DIMMPATH, \ - message=0; \ - \ - prop fault.memory.page@DIMMPATH \ - { DIAGNOSE_ERPT && CONTAINS_DIMM && SET_ADDR && SET_OFFSET } (0)-> \ - ereport.cpu.generic-sparc.mem-uc@level<>; \ - \ - event upset.memory.page@DIMMPATH; \ - \ - prop upset.memory.page@DIMMPATH \ - { !DIAGNOSE_ERPT } (0)-> \ - ereport.cpu.generic-sparc.mem-uc@level<> - -FLT_MEM_UE_PAGE(chip); -FLT_MEM_UE_PAGE(core); -FLT_MEM_UE_PAGE(strand); - - -#define CHIP chip -#define MEM_BUFF memory-buffer -#define MEM_CTRL memory-controller - -#define CONTAINS_CHIP (payloadprop_contains("sender", asru(CHIP))) -#define CONTAINS_MEMBUFF (payloadprop_contains("sender", asru(MEM_BUFF))) -#define CONTAINS_MEMCTRL (payloadprop_contains("sender", asru(MEM_CTRL))) - -engine serd.memory.generic-sparc.membuf-crc@CHIP, N=120, T=30min; -engine serd.memory.generic-sparc.membuf-crc@MEM_BUFF, N=120, T=30min; -engine serd.memory.generic-sparc.membuf-crc@MEM_CTRL, N=120, T=30min; - - -event fault.memory.memlink@CHIP, - engine=serd.memory.generic-sparc.membuf-crc@CHIP; -event fault.memory.memlink@MEM_BUFF, - engine=serd.memory.generic-sparc.membuf-crc@MEM_BUFF; -event fault.memory.memlink@MEM_CTRL, - engine=serd.memory.generic-sparc.membuf-crc@MEM_CTRL; - -/* - * 1. if ereport has both sender & detector: membuf-crc errors will fault - * both detector & sender. - * - if detector is chip or memory-controller, the sender is memory-buffer. - * - if detector is memory-buffer, the sender is chip or memory-controller - * 2. if ereport does not have sender: - * - if detector is chip, sender is memory-buffer - * - if detector is memory-controller, sender is memory-buffer - * - if detector is memory-buffer: - * + if topology is chip/memory-buffer, sender is chip - * + if topology is memory-controller/memory-buffer, sender is - * memory-controller. - */ - -#define HAS_SENDER (payloadprop_defined("sender")) - -event ereport.cpu.generic-sparc.membuf-crc@CHIP { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc@MEM_BUFF { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc@MEM_CTRL { within(1s) }; - -/* - * detector is chip and ereport has a sender - */ -prop fault.memory.memlink@CHIP - { DIAGNOSE_ERPT && SET_SERDN && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.membuf-crc@CHIP; - -prop fault.memory.memlink@MEM_BUFF - { DIAGNOSE_ERPT && CONTAINS_MEMBUFF && SET_SERDN && - SET_SERDT && SET_RATIO } (0)-> - ereport.cpu.generic-sparc.membuf-crc@CHIP<>; - -/* - * detector is chip and ereport does not have sender - */ -engine serd.memory.generic-sparc.membuf-crc@CHIP/MEM_BUFF, N=120, T=30min; -event fault.memory.memlink@CHIP/MEM_BUFF, - engine=serd.memory.generic-sparc.membuf-crc@CHIP/MEM_BUFF; - -prop fault.memory.memlink@CHIP/MEM_BUFF - { DIAGNOSE_ERPT && !HAS_SENDER && - SET_SERDN && SET_SERDT && SET_RATIO } (0)-> - ereport.cpu.generic-sparc.membuf-crc@CHIP; - -event upset.memory.memlink@CHIP; - -prop upset.memory.memlink@CHIP - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc@CHIP; - -/* - * detector is memory-buffer and ereport has sender - */ -prop fault.memory.memlink@MEM_BUFF - { DIAGNOSE_ERPT && SET_SERDN && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.membuf-crc@MEM_BUFF; - -prop fault.memory.memlink@CHIP - { DIAGNOSE_ERPT && CONTAINS_CHIP && SET_SERDN && - SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.membuf-crc@MEM_BUFF<>; - -prop fault.memory.memlink@MEM_CTRL - { DIAGNOSE_ERPT && CONTAINS_MEMCTRL && SET_SERDN && - SET_SERDT && SET_RATIO } (0)-> - ereport.cpu.generic-sparc.membuf-crc@MEM_BUFF<>; - -/* - * detector is memory-buffer and ereport does not have sender - */ -event ereport.cpu.generic-sparc.membuf-crc@CHIP/MEM_BUFF { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc@MEM_CTRL/MEM_BUFF { within(1s) }; - -prop fault.memory.memlink@CHIP - { DIAGNOSE_ERPT && !HAS_SENDER && - SET_SERDN && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.membuf-crc@CHIP/MEM_BUFF<>; - -prop fault.memory.memlink@MEM_CTRL - { DIAGNOSE_ERPT && !HAS_SENDER && - SET_SERDN && SET_SERDT && SET_RATIO } (0) -> - ereport.cpu.generic-sparc.membuf-crc@MEM_CTRL/MEM_BUFF<>; - -event upset.memory.memlink@MEM_BUFF; - -prop upset.memory.memlink@MEM_BUFF - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc@MEM_BUFF; - -/* - * detector is memory-controller and ereport has a sender - */ -prop fault.memory.memlink@MEM_CTRL - { DIAGNOSE_ERPT && SET_SERDN && SET_SERDT && SET_RATIO } (0)-> - ereport.cpu.generic-sparc.membuf-crc@MEM_CTRL; - -prop fault.memory.memlink@MEM_BUFF - { DIAGNOSE_ERPT && CONTAINS_MEMBUFF && SET_SERDN && - SET_SERDT && SET_RATIO } (0)-> - ereport.cpu.generic-sparc.membuf-crc@MEM_CTRL<>; - -/* - * detector is memory-controller and ereport does not have a sender - */ -engine serd.cpu.generic-sparc.membuf-crc@MEM_CTRL/MEM_BUFF, N=120, T=30min; -event fault.memory.memlink@MEM_CTRL/MEM_BUFF, - engine=serd.cpu.generic-sparc.membuf-crc@MEM_CTRL/MEM_BUFF; - -prop fault.memory.memlink@MEM_CTRL/MEM_BUFF - { DIAGNOSE_ERPT && !HAS_SENDER && - SET_SERDN && SET_SERDT && SET_RATIO } (0)-> - ereport.cpu.generic-sparc.membuf-crc@MEM_CTRL; - -event upset.memory.memlink@MEM_CTRL; - -prop upset.memory.memlink@MEM_CTRL - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc@MEM_CTRL; - -/* - * membuf-crc-uc, membuf-other-uc will fault the detector FRU and sender FRU - * if detector is CHIP or MEM_CTRL, the sender is MEM_BUFF. - * if detector is MEM_BUFF, the sender is CHIP or MEM_CTRL - */ -event ereport.cpu.generic-sparc.membuf-crc-uc@CHIP { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc-uc@MEM_BUFF { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc-uc@MEM_CTRL { within(1s) }; - -event ereport.cpu.generic-sparc.membuf-other-uc@CHIP { within(1s) }; -event ereport.cpu.generic-sparc.membuf-other-uc@MEM_BUFF { within(1s) }; -event ereport.cpu.generic-sparc.membuf-other-uc@MEM_CTRL { within(1s) }; - -event fault.memory.memlink-uc@CHIP; -event fault.memory.memlink-uc@MEM_BUFF; -event fault.memory.memlink-uc@MEM_CTRL; - -/* - * chip is detector and ereport has a sender - */ -prop fault.memory.memlink-uc@CHIP - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@CHIP, - ereport.cpu.generic-sparc.membuf-other-uc@CHIP; - -prop fault.memory.memlink-uc@MEM_BUFF - { DIAGNOSE_ERPT && CONTAINS_MEMBUFF } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@CHIP<>, - ereport.cpu.generic-sparc.membuf-other-uc@CHIP<>; - -/* - * chip is detector and ereport does not have a sender - */ -event fault.memory.memlink-uc@CHIP/MEM_BUFF; - -prop fault.memory.memlink-uc@CHIP/MEM_BUFF - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@CHIP, - ereport.cpu.generic-sparc.membuf-other-uc@CHIP; - -event upset.memory.memlink-uc@CHIP; - -prop upset.memory.memlink-uc@CHIP - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc-uc@CHIP, - ereport.cpu.generic-sparc.membuf-other-uc@CHIP; - -/* - * memory-buffer is detector and ereport has a sender - */ -prop fault.memory.memlink-uc@MEM_BUFF - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_BUFF, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_BUFF; - -prop fault.memory.memlink-uc@CHIP - { DIAGNOSE_ERPT && CONTAINS_CHIP } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_BUFF<>, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_BUFF<>; - -prop fault.memory.memlink-uc@MEM_CTRL - { DIAGNOSE_ERPT && CONTAINS_MEMCTRL } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_BUFF<>, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_BUFF<>; - -/* - * memory-buffer is detector and ereport does not have sender - */ -event ereport.cpu.generic-sparc.membuf-crc-uc@CHIP/MEM_BUFF { within(1s) }; -event ereport.cpu.generic-sparc.membuf-other-uc@CHIP/MEM_BUFF { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc-uc@MEM_CTRL/MEM_BUFF { within(1s) }; -event ereport.cpu.generic-sparc.membuf-other-uc@MEM_CTRL/MEM_BUFF - { within(1s) }; - -prop fault.memory.memlink-uc@CHIP - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@CHIP/MEM_BUFF<>, - ereport.cpu.generic-sparc.membuf-other-uc@CHIP/MEM_BUFF<>; - -prop fault.memory.memlink-uc@MEM_CTRL - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_CTRL/MEM_BUFF<>, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_CTRL/MEM_BUFF<>; - -event upset.memory.memlink-uc@MEM_BUFF; - -prop upset.memory.memlink-uc@MEM_BUFF - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_BUFF, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_BUFF; - -/* - * memory-controller is detector and ereport has a sender - */ -prop fault.memory.memlink-uc@MEM_CTRL - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_CTRL, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_CTRL; - -prop fault.memory.memlink-uc@MEM_BUFF - { DIAGNOSE_ERPT && CONTAINS_MEMBUFF } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_CTRL<>, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_CTRL<>; - -/* - * memory-controller is detector and ereport does not have sender - */ -event fault.memory.memlink-uc@MEM_CTRL/MEM_BUFF; - -prop fault.memory.memlink-uc@MEM_CTRL/MEM_BUFF - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_CTRL, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_CTRL; - -event upset.memory.memlink-uc@MEM_CTRL; - -prop upset.memory.memlink-uc@MEM_CTRL - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc-uc@MEM_CTRL, - ereport.cpu.generic-sparc.membuf-other-uc@MEM_CTRL; - -/* - * membuf-crc-failover will fault the detector FRU and sender FRU - * if detector is chip or memory-controller, the sender is memory-buffer. - * if detector is memory-buffer, the sender is chip or memory-controller - */ -event ereport.cpu.generic-sparc.membuf-crc-failover@CHIP { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc-failover@MEM_BUFF - { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc-failover@MEM_CTRL - { within(1s) }; - -event fault.memory.memlink-failover@CHIP; -event fault.memory.memlink-failover@MEM_BUFF; -event fault.memory.memlink-failover@MEM_CTRL; - -/* - * chip is detector and ereport has a sender - */ -prop fault.memory.memlink-failover@CHIP - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@CHIP; - -prop fault.memory.memlink-failover@MEM_BUFF - { DIAGNOSE_ERPT && CONTAINS_MEMBUFF } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@CHIP<>; - -/* - * chip is detector and ereport does not have sender - */ -event fault.memory.memlink-failover@CHIP/MEM_BUFF; - -prop fault.memory.memlink-failover@CHIP/MEM_BUFF - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@CHIP; - -event upset.memory.memlink-failover@CHIP; - -prop upset.memory.memlink-failover@CHIP - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc-failover@CHIP; -/* - * memory-buffer is detector and ereport has a sender - */ -prop fault.memory.memlink-failover@MEM_BUFF - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_BUFF; - -prop fault.memory.memlink-failover@CHIP - { DIAGNOSE_ERPT && CONTAINS_CHIP } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_BUFF<>; - -prop fault.memory.memlink-failover@MEM_CTRL - { DIAGNOSE_ERPT && CONTAINS_MEMCTRL } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_BUFF<>; - -/* - * memory-buffer is detector and ereport does not have sender - */ -event ereport.cpu.generic-sparc.membuf-crc-failover@CHIP/MEM_BUFF - { within(1s) }; -event ereport.cpu.generic-sparc.membuf-crc-failover@MEM_CTRL/MEM_BUFF - { within(1s) }; - -prop fault.memory.memlink-failover@CHIP - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@CHIP/MEM_BUFF<>; - -prop fault.memory.memlink-failover@MEM_CTRL - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_CTRL/MEM_BUFF<>; - -event upset.memory.memlink-failover@MEM_BUFF; - -prop upset.memory.memlink-failover@MEM_BUFF - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_BUFF; -/* - * memory-controller is detector and ereport has a sender - */ -prop fault.memory.memlink-failover@MEM_CTRL - { DIAGNOSE_ERPT } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_CTRL; - -prop fault.memory.memlink-failover@MEM_BUFF - { DIAGNOSE_ERPT && CONTAINS_MEMBUFF } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_CTRL<>; - -/* - * memory-controller is detector and ereport does not have sender - */ -event fault.memory.memlink-failover@MEM_CTRL/MEM_BUFF; - -prop fault.memory.memlink-failover@MEM_CTRL/MEM_BUFF - { DIAGNOSE_ERPT && !HAS_SENDER } (0) -> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_CTRL; - -event upset.memory.memlink-failover@MEM_CTRL; - -prop upset.memory.memlink-failover@MEM_CTRL - { !DIAGNOSE_ERPT } (0)-> - ereport.cpu.generic-sparc.membuf-crc-failover@MEM_CTRL; -/* - * ignore the membuf-other errors - */ -event ereport.cpu.generic-sparc.membuf-other@CHIP; -event ereport.cpu.generic-sparc.membuf-other@MEM_BUFF; -event ereport.cpu.generic-sparc.membuf-other@MEM_CTRL; - -event upset.memory.discard@CHIP; -event upset.memory.discard@MEM_BUFF; -event upset.memory.discard@MEM_CTRL; - -prop upset.memory.discard@CHIP (1)-> - ereport.cpu.generic-sparc.membuf-other@CHIP; - -prop upset.memory.discard@MEM_BUFF (1)-> - ereport.cpu.generic-sparc.membuf-other@MEM_BUFF; - -prop upset.memory.discard@MEM_CTRL (1)-> - ereport.cpu.generic-sparc.membuf-other@MEM_CTRL; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2niu_xaui.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2niu_xaui.esc deleted file mode 100644 index 22583ce334..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2niu_xaui.esc +++ /dev/null @@ -1,50 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2007 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -#pragma dictionary "NXGE" -/* - * Eversholt rules for a XAUI card connected to the NIU of Niagara2 CPU - */ - -#define XAUI_FIT 100 - -asru niufn; -fru xaui; - -event fault.io.n2.niu-xaui@niufn/xaui, - FITrate=XAUI_FIT, ASRU=niufn, FRU=xaui; - -event error.io.device.nxge.xaui-err@niufn; -event ereport.io.device.nxge.xaui-err@niufn {within(10s)}; -event ereport.io.service.lost@niufn {within(10s)}; - -prop fault.io.n2.niu-xaui@niufn/xaui (1) -> - error.io.device.nxge.xaui-err@niufn; - -prop error.io.device.nxge.xaui-err@niufn (2) -> - ereport.io.device.nxge.xaui-err@niufn, - ereport.io.service.lost@niufn; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2niu_xfp.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2niu_xfp.esc deleted file mode 100644 index 31c5517bf8..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2niu_xfp.esc +++ /dev/null @@ -1,53 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2007 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -#pragma dictionary "NXGE" -/* - * Eversholt rules for the XFP optical module inserted in the XAUI card, - * which is connected to the NIU of the Niagara2 CPU - */ - -#define XFP_FIT 100 - -asru niufn; -fru xaui/xfp; - -event fault.io.n2.niu-xfp@niufn/xaui/xfp, - FITrate=XFP_FIT, ASRU=niufn, FRU=xaui/xfp; - -event error.io.device.nxge.xfp-err@niufn; -event ereport.io.device.nxge.xfp-err@niufn {within(10s)}; -event ereport.io.service.lost@niufn {within(10s)}; - - -prop fault.io.n2.niu-xfp@niufn/xaui/xfp (1) -> - error.io.device.nxge.xfp-err@niufn; - -prop error.io.device.nxge.xfp-err@niufn (2) -> - ereport.io.device.nxge.xfp-err@niufn, - ereport.io.service.lost@niufn; - diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2piu.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2piu.esc deleted file mode 100644 index 70a319b7f5..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/n2piu.esc +++ /dev/null @@ -1,288 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2009 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma dictionary "SUN4V" - -/* - * Eversholt rules for the N2 PIU extention to Fire nexus driver - */ -#define HB_FIT 400 -#define NONFATAL_COUNT 10 -#define NONFATAL_TIME 1hour -#define PCIEX_DEV_FIT 1000 -#define LINK_EVENTS_COUNT 10 -#define LINK_EVENTS_TIME 1h - -/* - * Test for primary or secondary ereports - */ -#define IS_PRIMARY (payloadprop("primary")) -#define IS_SECONDARY (! payloadprop("primary")) - -/* - * payload: mmu-tfsr - * - * Extract the request id, the BDF value, in the MMU TFSR register - * - * PRM 2.0, pg 243 - * Request ID: bits 15:0 - * - * Example: - * 0x7766554433221100 - * ^^^^ - */ -#define MMU_REQ_ID_BIT_MODULO (1 << 16) -#define MMU_MATCH_BDF(mmu_tfsr, b, d, f) \ - ( IS_PRIMARY && \ - (((mmu_tfsr) % MMU_REQ_ID_BIT_MODULO) == ((b << 8) | (d << 3) | f)) \ - ) - -/* - * Faults, upsets and defects - */ -/* N2 Asic */ -fru hostbridge/pciexrc; -asru hostbridge/pciexrc; -event fault.io.fire.asic@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge/pciexrc, ASRU=hostbridge/pciexrc; -event fault.io.n2.soc@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge/pciexrc, ASRU=hostbridge/pciexrc; -event fault.io.n2.crossbar@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge/pciexrc, ASRU=hostbridge/pciexrc; -event fault.io.n2.dmu@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge/pciexrc, ASRU=hostbridge/pciexrc; -event fault.io.n2.ncu@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge/pciexrc, ASRU=hostbridge/pciexrc; -event fault.io.n2.siu@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge/pciexrc, ASRU=hostbridge/pciexrc; -event fault.io.n2.niu@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge/pciexrc, ASRU=hostbridge/pciexrc; - -/* No diagnosis */ -event upset.io.fire.nodiag@hostbridge; - -/* - * Additional "DMC" errors to fire. - * N2 asic parity error - */ -event ereport.io.n2.dmu.iotsbdesc_dpe@hostbridge/pciexrc{within(5s)}; - -/* - * Additional "PEC" errors to fire. - */ -event ereport.io.n2.peu.err_sds_los@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.peu.lwc@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.peu.nfp@hostbridge/pciexrc{within(5s)}; - -/* - * Unique SOC errors to N2 - */ -/* fault.io.n2.soc */ -event ereport.io.n2.soc.ncumondotable@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.ncuctagce@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.ncuinttable@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.ncudataparity@hostbridge/pciexrc{within(5s)}; - -/* fault.io.n2.crossbar */ -event ereport.io.n2.soc.ncupcxdata@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.ncudmucredit@hostbridge/pciexrc{within(5s)}; - -/* fault.io.n2.dmu */ -event ereport.io.n2.soc.siidmuctague@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.siidmuctagce@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.siidmuaparity@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.siidmudparity@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.dmuinternal@hostbridge/pciexrc; - -/* fault.io.n2.ncu */ -event ereport.io.n2.soc.ncupcxue@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.dmuncucredit@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.ncumondofifo@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.ncucpxue@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.ncudmuue@hostbridge/pciexrc{within(5s)}; - -/* fault.io.n2.siu */ -event ereport.io.n2.soc.ncuctague@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.sioctague@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.dmusiicredit@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.dmudataparity@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.sioctagce@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.dmuctagce@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.dmuctague@hostbridge/pciexrc{within(5s)}; - -/* fault.io.n2.niu */ -event ereport.io.n2.soc.siiniuctagce@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.siiniuctague@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.siiniuaparity@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.siiniudparity@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.niuctague@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.niuctagce@hostbridge/pciexrc{within(5s)}; -event ereport.io.n2.soc.niudataparity@hostbridge/pciexrc{within(5s)}; - -/* fault.io.niu/niufn */ -event ereport.io.device.inval_state@niu/niufn{within(5s)}; -event ereport.io.device.no_response@niu/niufn{within(5s)}; -event ereport.io.device.stall@niu/niufn{within(5s)}; -event ereport.io.device.badint_limit@niu/niufn{within(5s)}; -event ereport.io.device.intern_corr@niu/niufn{within(5s)}; -event ereport.io.device.intern_uncorr@niu/niufn{within(5s)}; -event ereport.io.device.nf-device@niu/niufn; - -/* - * Fault at the adjacent node which is right below the Fire ASIC - */ -event error.io.fire.pec.adjacentnode@hostbridge/pciexrc; - -prop error.io.fire.pec.adjacentnode@hostbridge/pciexrc (0) -> - ereport.io.n2.peu.nfp@hostbridge/pciexrc; - -/* - * DMU N2 asic parity error - */ -prop fault.io.fire.asic@hostbridge/pciexrc (0)-> - ereport.io.n2.dmu.iotsbdesc_dpe@hostbridge/pciexrc; - -/* - * Surprise remove or serdes los, similar to fire ldn event, - * don't diag. - */ -prop upset.io.fire.nodiag@hostbridge (0)-> - ereport.io.n2.peu.err_sds_los@hostbridge/pciexrc, - ereport.io.n2.peu.lwc@hostbridge/pciexrc; - -/* SOC Errors */ -/* fault.io.n2.soc */ -prop fault.io.n2.soc@hostbridge/pciexrc (1)-> - ereport.io.n2.soc.ncumondotable@hostbridge/pciexrc, - ereport.io.n2.soc.ncuctagce@hostbridge/pciexrc, - ereport.io.n2.soc.ncuinttable@hostbridge/pciexrc, - ereport.io.n2.soc.ncudataparity@hostbridge/pciexrc; - -/* fault.io.n2.crossbar */ -prop fault.io.n2.crossbar@hostbridge/pciexrc (1)-> - ereport.io.n2.soc.ncudmucredit@hostbridge/pciexrc, - ereport.io.n2.soc.ncupcxdata@hostbridge/pciexrc; - -/* fault.io.n2.dmu */ -prop fault.io.n2.dmu@hostbridge/pciexrc (1)-> - ereport.io.n2.soc.siidmuctague@hostbridge/pciexrc, - ereport.io.n2.soc.siidmuctagce@hostbridge/pciexrc, - ereport.io.n2.soc.siidmuaparity@hostbridge/pciexrc, - ereport.io.n2.soc.siidmudparity@hostbridge/pciexrc, - ereport.io.n2.soc.dmuinternal@hostbridge/pciexrc; - -/* fault.io.n2.ncu */ -prop fault.io.n2.ncu@hostbridge/pciexrc (1)-> - ereport.io.n2.soc.ncupcxue@hostbridge/pciexrc, - ereport.io.n2.soc.dmuncucredit@hostbridge/pciexrc, - ereport.io.n2.soc.ncumondofifo@hostbridge/pciexrc, - ereport.io.n2.soc.ncucpxue@hostbridge/pciexrc, - ereport.io.n2.soc.ncudmuue@hostbridge/pciexrc; - -/* fault.io.n2.siu */ -prop fault.io.n2.siu@hostbridge/pciexrc (1)-> - ereport.io.n2.soc.ncuctague@hostbridge/pciexrc, - ereport.io.n2.soc.sioctague@hostbridge/pciexrc, - ereport.io.n2.soc.dmusiicredit@hostbridge/pciexrc, - ereport.io.n2.soc.dmudataparity@hostbridge/pciexrc, - ereport.io.n2.soc.sioctagce@hostbridge/pciexrc, - ereport.io.n2.soc.dmuctagce@hostbridge/pciexrc, - ereport.io.n2.soc.dmuctague@hostbridge/pciexrc; - -/* fault.io.n2.niu */ -prop fault.io.n2.niu@hostbridge/pciexrc (0)-> - ereport.io.n2.soc.siiniuctague@hostbridge/pciexrc, - ereport.io.n2.soc.siiniuaparity@hostbridge/pciexrc, - ereport.io.n2.soc.siiniudparity@hostbridge/pciexrc, - ereport.io.n2.soc.siiniuctagce@hostbridge/pciexrc, - ereport.io.n2.soc.niuctague@hostbridge/pciexrc, - ereport.io.n2.soc.niuctagce@hostbridge/pciexrc, - ereport.io.n2.soc.niudataparity@hostbridge/pciexrc; - -/* n2 niu/niufn */ -event error.io.device.f-device@niu/niufn; -event error.io.device.nf-device@niu/niufn; -event error.io.service.restored@niu/niufn; -event ereport.io.service.lost@niu/niufn{within(5s)}; -event ereport.io.service.restored@niu/niufn{within(30s)}; -event ereport.io.service.degraded@niu/niufn{within(5s)}; -event ereport.io.service.unaffected@niu/niufn{within(5s)}; - -/* fault error propogation */ -prop fault.io.n2.niu@hostbridge/pciexrc (0)-> - error.io.device.f-device@niu/niufn, - error.io.device.nf-device@niu/niufn; - -/* fault.io.niu/niufn */ -prop error.io.service.restored@niu/niufn (1)-> - ereport.io.service.lost@niu/niufn, - ereport.io.service.degraded@niu/niufn; - -prop error.io.service.restored@niu/niufn (1)-> - ereport.io.service.restored@niu/niufn; - -prop error.io.device.f-device@niu/niufn (1)-> - ereport.io.device.inval_state@niu/niufn, - ereport.io.device.no_response@niu/niufn, - ereport.io.device.stall@niu/niufn, - ereport.io.device.badint_limit@niu/niufn, - ereport.io.device.intern_corr@niu/niufn, - ereport.io.device.intern_uncorr@niu/niufn; - -prop error.io.device.f-device@niu/niufn (1)-> - ereport.io.service.lost@niu/niufn, - ereport.io.service.degraded@niu/niufn; - -engine serd.io.device.nonfatal@niu/niufn, - N=NONFATAL_COUNT, T=NONFATAL_TIME, method=persistent, - trip=ereport.io.device.nf-device@niu/niufn; - -event upset.io.device.nonfatal@niu/niufn, - engine=serd.io.device.nonfatal@niu/niufn; - -prop error.io.device.nf-device@niu/niufn (1)-> - ereport.io.device.nf-device@niu/niufn; - -prop error.io.device.nf-device@niu/niufn (0)-> - ereport.io.device.inval_state@niu/niufn, - ereport.io.device.no_response@niu/niufn, - ereport.io.device.stall@niu/niufn, - ereport.io.device.badint_limit@niu/niufn, - ereport.io.device.intern_corr@niu/niufn, - ereport.io.device.intern_uncorr@niu/niufn, - ereport.io.service.unaffected@niu/niufn, - error.io.service.restored@niu/niufn; - -prop upset.io.device.nonfatal@niu/niufn (1)-> - ereport.io.device.inval_state@niu/niufn, - ereport.io.device.no_response@niu/niufn, - ereport.io.device.stall@niu/niufn, - ereport.io.device.badint_limit@niu/niufn, - ereport.io.device.intern_corr@niu/niufn, - ereport.io.device.intern_uncorr@niu/niufn; - -prop upset.io.device.nonfatal@niu/niufn (1)-> - ereport.io.service.unaffected@niu/niufn, - error.io.service.restored@niu/niufn; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/sp.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/sp.esc deleted file mode 100644 index c1f272b244..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/sp.esc +++ /dev/null @@ -1,37 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2009 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma dictionary "SUN4V" - -/* - * Eversholt rule for a faulted Service Processor - */ - -event fault.sp.failed@sp; - -event ereport.chassis.sp.unavailable@chassis; - -prop fault.sp.failed@sp -> - ereport.chassis.sp.unavailable@chassis; diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/vfncx.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/vfncx.esc deleted file mode 100644 index 732bbfdfa5..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/vfncx.esc +++ /dev/null @@ -1,58 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ -/* - * Copyright 2007 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -#pragma dictionary "SUN4V" - -/* - * Eversholt rules for the VF PIU extention to Fire nexus driver - */ -#define HB_FIT 400 - -/* - * Faults, upsets and defects - */ -/* VF Asic */ -fru hostbridge/pciexrc; -asru hostbridge/pciexrc; -event fault.io.vf.ncx@hostbridge/pciexrc, - FITrate=HB_FIT, FRU=hostbridge/pciexrc, ASRU=hostbridge/pciexrc; - -/* fault.io.vf.ncx */ -event ereport.io.vf.ncx.to-fdr@hostbridge/pciexrc{within(0s)}; -event ereport.io.vf.ncx.to-fsr@hostbridge/pciexrc{within(0s)}; -event ereport.io.vf.ncx.fre@hostbridge/pciexrc{within(0s)}; -event ereport.io.vf.ncx.fse@hostbridge/pciexrc{within(0s)}; -event ereport.io.vf.ncx.fde@hostbridge/pciexrc{within(0s)}; - -/* fault.io.vf.ncx */ -prop fault.io.vf.ncx@hostbridge/pciexrc (1)-> - ereport.io.vf.ncx.to-fdr@hostbridge/pciexrc, - ereport.io.vf.ncx.to-fsr@hostbridge/pciexrc, - ereport.io.vf.ncx.fre@hostbridge/pciexrc, - ereport.io.vf.ncx.fse@hostbridge/pciexrc, - ereport.io.vf.ncx.fde@hostbridge/pciexrc; - diff --git a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/zambezi.esc b/usr/src/cmd/fm/eversholt/files/sparc/sun4v/zambezi.esc deleted file mode 100644 index 4d3303a3ec..0000000000 --- a/usr/src/cmd/fm/eversholt/files/sparc/sun4v/zambezi.esc +++ /dev/null @@ -1,839 +0,0 @@ -/* - * CDDL HEADER START - * - * The contents of this file are subject to the terms of the - * Common Development and Distribution License (the "License"). - * You may not use this file except in compliance with the License. - * - * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE - * or http://www.opensolaris.org/os/licensing. - * See the License for the specific language governing permissions - * and limitations under the License. - * - * When distributing Covered Code, include this CDDL HEADER in each - * file and include the License file at usr/src/OPENSOLARIS.LICENSE. - * If applicable, add the following below this CDDL HEADER, with the - * fields enclosed by brackets "[]" replaced with your own identifying - * information: Portions Copyright [yyyy] [name of copyright owner] - * - * CDDL HEADER END - */ - -/* - * Copyright 2007 Sun Microsystems, Inc. All rights reserved. - * Use is subject to license terms. - */ - -#pragma ident "%Z%%M% %I% %E% SMI" - -#pragma dictionary "SUN4V" - -/* - * Define FITrates for different types of errors. For the ultrSPARC-T2plus - * interconnect, they are all defined to provide relative likelihood as - * actual FITrates are unavailable. We define them here in case more - * accurate values become available in future. - */ -#define CPU_CHIP_FIT 400 -#define FPGA_FIT 400 -#define FIRMWARE_HYPERVISOR_FIT 400 -#define FIRMWARE_VBSC_FIT 400 -#define INTERCONNECT_OPU_FIT 400 -#define INTERCONNECT_LFU_F_FIT 400 -#define INTERCONNECT_LFU_U_FIT 400 -#define INTERCONNECT_LFU_C_FIT 400 -#define INTERCONNECT_GPD_FIT 400 -#define INTERCONNECT_ASU_FIT 400 - -/* - * Define propogation delays for the ereports. - * - * For immediate processing, we specify a very short delay, which seems to - * work better than 0. For ereports that are to be ignored, we delay longer, - * 1 second. - */ -#define IGNORE_DELAY 1s -#define IMMEDIATE_DELAY 5ms -#define SERD_DELAY 1ms -#define RETRAIN_DELAY 5s - - -/* - * Test for primary or secondary ereports - */ -#define IS_PRIMARY (payloadprop("primary")) -#define IS_SECONDARY (! payloadprop("primary")) - - -/* - * Tests to determine what CHIP is associated with an ereport - */ -#define MATCH_CPUID(n) (payloadprop("cpu-nodeid") == n) - - -/* - * SERD values used by the LFU subsystem - */ -#define LFU_CRC_SERD_N 22 -#define LFU_CRC_SERD_T 30 min - - -/* - * ASRU and FRU definitions used by this diagnosis engine. - */ -asru motherboard; -asru interconnect; -asru chip; -fru motherboard; -fru cpuboard; - - -/* - * Define the errors that propogate to a CHIP fault. - */ -event error.cpu.ultraSPARC-T2plus.opu.protocol@chip; -event error.cpu.ultraSPARC-T2plus.lfu-c.chip@chip; -event error.cpu.ultraSPARC-T2plus.lfu-f.chip@chip; -event error.cpu.ultraSPARC-T2plus.lfu-u.chip@chip; -event error.cpu.ultraSPARC-T2plus.gpd-u.chip@chip; -event error.cpu.ultraSPARC-T2plus.gpd-c.chip@chip; -event error.cpu.ultraSPARC-T2plus.asu.protocol@chip; - -event fault.cpu.ultraSPARC-T2plus.chip@chip - FITrate=CPU_CHIP_FIT, ASRU=chip, FRU=cpuboard; - -prop fault.cpu.ultraSPARC-T2plus.chip@chip -> - error.cpu.ultraSPARC-T2plus.opu.protocol@chip, - error.cpu.ultraSPARC-T2plus.lfu-c.chip@chip, - error.cpu.ultraSPARC-T2plus.lfu-f.chip@chip, - error.cpu.ultraSPARC-T2plus.lfu-u.chip@chip, - error.cpu.ultraSPARC-T2plus.gpd-u.chip@chip, - error.cpu.ultraSPARC-T2plus.gpd-c.chip@chip, - error.cpu.ultraSPARC-T2plus.asu.protocol@chip; - - -/* - * OPU Subsystem - */ -event ereport.asic.zambezi.opu.ods-ctrl-parity@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ods-data-coherent-read@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ods-data-coherent-writeback@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ods-data-destid@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ods-data-parity@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.oqs-request-bad-nc-type@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.oqs-request-bad-read-type@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.oqs-request-bad-writeback-type@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.oqs-request-duplicate@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ors-response-bad-nc-type@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ors-response-bad-read-type@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ors-response-bad-writeback-type@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ors-response-duplicate@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ors-response-inconsistent@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ors-response-unexpected@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ors-timeout-read@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.opu.ors-timeout-writeback@interconnect - {within (IMMEDIATE_DELAY)}; - - -/* - * Declare the intermediate errors that will be generated by the ereports - * in this subsystem. These errors will, in turn, propogate to the - * appropriate fault. - */ -event error.asic.ultraSPARC-T2plus.interconnect.opu-u@interconnect; -event error.asic.ultraSPARC-T2plus.interconnect.opu-c@interconnect; - - -/* - * This fault is diagnosed for uncorrectible OPU errors - */ -event fault.asic.ultraSPARC-T2plus.interconnect.opu-u@interconnect - FITrate=INTERCONNECT_OPU_FIT, ASRU=interconnect, FRU=motherboard; - -prop error.asic.ultraSPARC-T2plus.interconnect.opu-u@interconnect -> - ereport.asic.zambezi.opu.ods-ctrl-parity@interconnect; - -prop fault.asic.ultraSPARC-T2plus.interconnect.opu-u@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.opu-u@interconnect; - - -/* - * This fault is diagnosed for correctible OPU errors. - */ -event fault.asic.ultraSPARC-T2plus.interconnect.opu-c@interconnect - FITrate=INTERCONNECT_OPU_FIT, ASRU=interconnect, FRU=motherboard; - -prop error.asic.ultraSPARC-T2plus.interconnect.opu-c@interconnect -> - ereport.asic.zambezi.opu.ods-data-parity@interconnect; - -prop fault.asic.ultraSPARC-T2plus.interconnect.opu-c@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.opu-c@interconnect; - - -/* - * All of the following ereports are associated with a CHIP. Propogate - * them to the appropriate error for diagnosis to a CHIP fault, above. - */ -prop error.cpu.ultraSPARC-T2plus.opu.protocol@chip[chip_num] (0) -> - ereport.asic.zambezi.opu.ods-data-destid@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ods-data-coherent-read@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ods-data-coherent-writeback@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.oqs-request-bad-read-type@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.oqs-request-bad-writeback-type@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.oqs-request-bad-nc-type@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.oqs-request-duplicate@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ors-response-unexpected@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ors-response-duplicate@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ors-response-inconsistent@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ors-response-bad-read-type@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ors-response-bad-writeback-type@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ors-response-bad-nc-type@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ors-timeout-read@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.opu.ors-timeout-writeback@interconnect - {MATCH_CPUID(chip_num)}; - - - -/* - * LFU Subsystem - */ -event ereport.asic.zambezi.lfu.crc-error@interconnect - {within (SERD_DELAY)}; -event ereport.asic.zambezi.lfu.data-invalid-or-unmapped@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.electric-idle@interconnect - {within (RETRAIN_DELAY)}; -event ereport.asic.zambezi.lfu.irq-overflow@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.irq-parity@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.irq-underflow@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.lane-failure-slf@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.lane-failure-mlf@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.link-down-retrain@interconnect - {within (RETRAIN_DELAY)}; -event ereport.asic.zambezi.lfu.link-down-retrain-failed@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.link-down-second-replay@interconnect - {within (SERD_DELAY)}; -event ereport.asic.zambezi.lfu.link-training-l05@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.link-training-config@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.link-training-state@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.link-training-testing@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.replay-lcf-rcvd-error@interconnect - {within (RETRAIN_DELAY)}; -event ereport.asic.zambezi.lfu.replay-lcf-sent-error@interconnect - {within (RETRAIN_DELAY)}; -event ereport.asic.zambezi.lfu.replay-parity@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.reply-invalid-or-unmapped@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.reply-tid-release-set@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.retrain-error-disabled@interconnect - {within (RETRAIN_DELAY)}; -event ereport.asic.zambezi.lfu.retrain-error-resume-timeout@interconnect - {within (RETRAIN_DELAY)}; -event ereport.asic.zambezi.lfu.retrain-error-second-crc@interconnect - {within (RETRAIN_DELAY)}; -event ereport.asic.zambezi.lfu.retrain-failed-disabled@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.retrain-failed-resume-timeout@interconnect - {within (IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.lfu.retrain-failed-second-crc@interconnect - {within (IMMEDIATE_DELAY)}; - -/* - * Declare the intermediate errors that will be generated by the ereports - * in this subsystem. These errors will, in turn, propogate to the - * appropriate fault. - */ -event error.asic.ultraSPARC-T2plus.interconnect.lfu-c@interconnect; -event error.asic.ultraSPARC-T2plus.interconnect.lfu-f@interconnect; -event error.asic.ultraSPARC-T2plus.interconnect.lfu-u@interconnect; -event error.asic.ultraSPARC-T2plus.interconnect.lfu.ignore@interconnect; - - -/* - * Declare the upsets that may be diagnosed for the LFU subsystem - */ -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.ignore@interconnect; - - -/* - * Declare the faults that may be generated for the LFU subsystem. - */ -event fault.asic.ultraSPARC-T2plus.interconnect.lfu-c@interconnect - FITrate=INTERCONNECT_LFU_C_FIT, ASRU=interconnect, FRU=motherboard; - -event fault.asic.ultraSPARC-T2plus.interconnect.lfu-f@interconnect - FITrate=INTERCONNECT_LFU_F_FIT, ASRU=interconnect, FRU=motherboard; - -event fault.asic.ultraSPARC-T2plus.interconnect.lfu-u@interconnect - FITrate=INTERCONNECT_LFU_U_FIT, ASRU=interconnect, FRU=motherboard; - -/* - * Define how the intermediate errors propogate to faults for the LFU - * subsystem. - */ -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.ignore@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.lfu.ignore@interconnect; - -prop fault.asic.ultraSPARC-T2plus.interconnect.lfu-c@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.lfu-c@interconnect; - -prop fault.asic.ultraSPARC-T2plus.interconnect.lfu-f@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.lfu-f@interconnect; - -prop fault.asic.ultraSPARC-T2plus.interconnect.lfu-u@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.lfu-u@interconnect; - - -/* - * We want to count CRC errors on each connection between an interconnect - * and a CHIP. Each interconnect is connected to each CHIP, so we need 16 - * SERD engines (4 interconnects, and 4 CHIPs). - * - * The topology does not include interconnect/chip, so we cannot do this - * automatically. Instead, we explicitly declare 4 sets of serd engine - * propogations, one for each CHIP, and let eversholt expand to all available - * interconnects. - */ -event ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip0@interconnect; -event ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip1@interconnect; -event ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip2@interconnect; -event ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip3@interconnect; - -prop error.asic.ultraSPARC-T2plus.interconnect.lfu-c@interconnect -> - ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip0@interconnect, - ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip1@interconnect, - ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip2@interconnect, - ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip3@interconnect; - -/* - * CHIP0 SERD rules - * - * These rules create a SERD engine for the connection between each - * interconnect and CHIP 0. - */ -engine serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip0@interconnect, - N=LFU_CRC_SERD_N, T=LFU_CRC_SERD_T, method=persistent, - trip=ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip0@interconnect; - -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.crc.chip0@interconnect, - engine=serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip0@interconnect; - -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.replay.chip0@interconnect, - engine=serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip0@interconnect; - -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.crc.chip0@interconnect -> - ereport.asic.zambezi.lfu.crc-error@interconnect - {MATCH_CPUID(0)}; - -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.replay.chip0@interconnect -> - ereport.asic.zambezi.lfu.link-down-second-replay@interconnect - {MATCH_CPUID(0)}; - - -/* - * CHIP1 SERD rules - * - * These rules create a SERD engine for the connection between each - * interconnect and CHIP 1. - */ -engine serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip1@interconnect, - N=LFU_CRC_SERD_N, T=LFU_CRC_SERD_T, method=persistent, - trip=ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip1@interconnect; - -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.crc.chip1@interconnect, - engine=serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip1@interconnect; - -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.replay.chip1@interconnect, - engine=serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip1@interconnect; - -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.crc.chip1@interconnect -> - ereport.asic.zambezi.lfu.crc-error@interconnect - {MATCH_CPUID(1)}; - -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.replay.chip1@interconnect -> - ereport.asic.zambezi.lfu.link-down-second-replay@interconnect - {MATCH_CPUID(1)}; - - -/* - * CHIP2 SERD rules - * - * These rules create a SERD engine for the connection between each - * interconnect and CHIP 2. - */ -engine serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip2@interconnect, - N=LFU_CRC_SERD_N, T=LFU_CRC_SERD_T, method=persistent, - trip=ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip2@interconnect; - -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.crc.chip2@interconnect, - engine=serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip2@interconnect; - -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.replay.chip2@interconnect, - engine=serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip2@interconnect; - -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.crc.chip2@interconnect -> - ereport.asic.zambezi.lfu.crc-error@interconnect - {MATCH_CPUID(2)}; - -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.replay.chip2@interconnect -> - ereport.asic.zambezi.lfu.link-down-second-replay@interconnect - {MATCH_CPUID(2)}; - - -/* - * CHIP3 SERD rules - * - * These rules create a SERD engine for the connection between each - * interconnect and CHIP 3. - */ -engine serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip3@interconnect, - N=LFU_CRC_SERD_N, T=LFU_CRC_SERD_T, method=persistent, - trip=ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip3@interconnect; - -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.crc.chip3@interconnect, - engine=serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip3@interconnect; - -event upset.asic.ultraSPARC-T2plus.interconnect.lfu.replay.chip3@interconnect, - engine=serd.asic.ultraSPARC-T2plus.interconnect.lfu.chip3@interconnect; - -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.crc.chip3@interconnect -> - ereport.asic.zambezi.lfu.crc-error@interconnect - {MATCH_CPUID(3)}; - -prop upset.asic.ultraSPARC-T2plus.interconnect.lfu.replay.chip3@interconnect -> - ereport.asic.zambezi.lfu.link-down-second-replay@interconnect - {MATCH_CPUID(3)}; - - -/* - * LFU propogations that generate - * error.asic.ultraSPARC-T2plus.interconnect.lfu-f@interconnect - */ -prop error.asic.ultraSPARC-T2plus.interconnect.lfu-f@interconnect -> - ereport.asic.zambezi.lfu.lane-failure-slf@interconnect; - - -/* - * LFU propogations that generate - * error.cpu.ultraSPARC-T2plus.lfu-f.chip@chip - */ -prop error.cpu.ultraSPARC-T2plus.lfu-f.chip@chip[chip_num] (0) -> - ereport.asic.zambezi.lfu.lane-failure-slf@interconnect - {MATCH_CPUID(chip_num)}; - - -/* - * LFU propogations that generate - * error.cpu.ultrSPARC-T2plus.lfu-u.chip - */ -prop error.cpu.ultraSPARC-T2plus.lfu-u.chip@chip[chip_num] (0) -> - ereport.asic.zambezi.lfu.lane-failure-mlf@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.link-training-state@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.link-training-testing@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.link-training-config@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.link-training-l05@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.link-down-retrain-failed@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.retrain-failed-second-crc@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.retrain-failed-resume-timeout@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.retrain-failed-disabled@interconnect - {MATCH_CPUID(chip_num)}; - -/* - * LFU propogations that generate - * error.asic.ultraSPARC-T2plus.interconnect.lfu-u@interconnect - */ -prop error.asic.ultraSPARC-T2plus.interconnect.lfu-u@interconnect -> - ereport.asic.zambezi.lfu.lane-failure-mlf@interconnect, - ereport.asic.zambezi.lfu.link-training-state@interconnect, - ereport.asic.zambezi.lfu.link-training-testing@interconnect, - ereport.asic.zambezi.lfu.link-training-config@interconnect, - ereport.asic.zambezi.lfu.link-training-l05@interconnect, - ereport.asic.zambezi.lfu.link-down-retrain-failed@interconnect, - ereport.asic.zambezi.lfu.retrain-failed-second-crc@interconnect, - ereport.asic.zambezi.lfu.retrain-failed-resume-timeout@interconnect, - ereport.asic.zambezi.lfu.retrain-failed-disabled@interconnect, - ereport.asic.zambezi.lfu.replay-parity@interconnect, - ereport.asic.zambezi.lfu.irq-parity@interconnect, - ereport.asic.zambezi.lfu.irq-underflow@interconnect; - -/* - * LFU propogations that generate - * error.asic.ultraSPARC-T2plus.interconnect.lfu.ignore@interconnect - */ -prop error.asic.ultraSPARC-T2plus.interconnect.lfu.ignore@interconnect -> - ereport.asic.zambezi.lfu.link-down-retrain@interconnect, - ereport.asic.zambezi.lfu.electric-idle@interconnect, - ereport.asic.zambezi.lfu.retrain-error-resume-timeout@interconnect, - ereport.asic.zambezi.lfu.retrain-error-second-crc@interconnect, - ereport.asic.zambezi.lfu.retrain-error-disabled@interconnect, - ereport.asic.zambezi.lfu.replay-lcf-rcvd-error@interconnect, - ereport.asic.zambezi.lfu.replay-lcf-sent-error@interconnect; - - -/* - * LFU propogations that generate - * error.cpu.ultraSPARC-T2plus.lfu-c.chip@chip - */ -prop error.cpu.ultraSPARC-T2plus.lfu-c.chip@chip[chip_num] (0) -> - ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip0@interconnect - {chip_num == 0}, - ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip1@interconnect - {chip_num == 1}, - ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip2@interconnect - {chip_num == 2}, - ereport.asic.ultraSPARC-T2plus.interconnect.lfu.crc-trip3@interconnect - {chip_num == 3}, - ereport.asic.zambezi.lfu.data-invalid-or-unmapped@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.reply-invalid-or-unmapped@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.reply-tid-release-set@interconnect - {MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.lfu.irq-overflow@interconnect - {MATCH_CPUID(chip_num)}; - - -/* - * GPD Subsystem - */ -event ereport.asic.zambezi.gpd.jtag-access-violation@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.jtag-mapped-timeout@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-access-violation@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-invalid-read-request@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-invalid-write-request@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-mapped-timeout@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-unexpected-data-rcvd@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-unexpected-request-rcvd@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-write-data-bytemask-error@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-write-data-c2c-set@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-write-data-chunk-error@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-write-data-error-bit-set@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-write-data-timeout@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-write-request-tid-invalid@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-write-request-timeout@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.link-write-tid-invalid@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.lpc-access-violation@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.lpc-invalid-abort@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.lpc-invalid-cycle-type@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.lpc-invalid-start@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.lpc-mapped-timeout@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.gpd.lpc-rw-interleave-error@interconnect - {within(IMMEDIATE_DELAY)}; - -/* - * Declare the intermediate errors that will be generated by the ereports - * in this subsystem. These errors will, in turn, propogate to the - * appropriate fault. - */ -event error.asic.fpga@motherboard; -event error.asic.ultraSPARC-T2plus.interconnect.gpd@interconnect; -event error.asic.ultraSPARC-T2plus.interconnect.gpd.ignore@interconnect; -event error.asic.ultraSPARC-T2plus.interconnect.gpd-c@interconnect; -event error.asic.ultraSPARC-T2plus.interconnect.gpd-u@interconnect; - - -/* - * Declare the upsets that may be diagnosed for this subsystem - */ -event upset.asic.ultraSPARC-T2plus.interconnect.gpd.ignore@interconnect; - - -/* - * Declare the faults that may be generated for this subsystem. - */ -event fault.asic.fpga@motherboard - FITrate=FPGA_FIT, ASRU=motherboard, FRU=motherboard; - -event fault.asic.ultraSPARC-T2plus.interconnect.gpd-c@interconnect - FITrate=INTERCONNECT_GPD_FIT, ASRU=interconnect, FRU=motherboard; - -event fault.asic.ultraSPARC-T2plus.interconnect.gpd-u@interconnect - FITrate=INTERCONNECT_GPD_FIT, ASRU=interconnect, FRU=motherboard; - - -/* - * Define how the intermediate errors propogate to faults for this subsystem. - */ -prop fault.asic.fpga@motherboard -> - error.asic.fpga@motherboard; - -prop upset.asic.ultraSPARC-T2plus.interconnect.gpd.ignore@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.gpd.ignore@interconnect; - -prop fault.asic.ultraSPARC-T2plus.interconnect.gpd-u@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.gpd-u@interconnect; - -prop fault.asic.ultraSPARC-T2plus.interconnect.gpd-c@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.gpd@interconnect, - error.asic.ultraSPARC-T2plus.interconnect.gpd-c@interconnect; - -/* - * GPD suspect list - * fault.asic.ultraSPARC-T2plus.interconnect.gpd-u - * fault.cpu.ultraSPARC-T2plus.chip - * - * Events in this list are diagnosed only if they are primary errors. - * The necessary information is unavailable for secondary errors, so - * they are logged but not diagnosed. - */ -prop error.cpu.ultraSPARC-T2plus.gpd-u.chip@chip[chip_num] (0) -> - ereport.asic.zambezi.gpd.link-write-request-timeout@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-write-data-timeout@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-write-request-tid-invalid@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-unexpected-data-rcvd@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-unexpected-request-rcvd@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}; - -prop error.cpu.ultraSPARC-T2plus.gpd-c.chip@chip[chip_num] (0) -> - ereport.asic.zambezi.gpd.link-write-tid-invalid@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-write-data-chunk-error@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-write-data-c2c-set@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-write-data-error-bit-set@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-invalid-write-request@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-write-data-bytemask-error@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-mapped-timeout@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-access-violation@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.gpd.link-invalid-read-request@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}; - -prop error.asic.ultraSPARC-T2plus.interconnect.gpd-u@interconnect -> - ereport.asic.zambezi.gpd.link-write-request-timeout@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-write-data-timeout@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-write-request-tid-invalid@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-unexpected-data-rcvd@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-unexpected-request-rcvd@interconnect - {IS_PRIMARY}; - -prop error.asic.ultraSPARC-T2plus.interconnect.gpd.ignore@interconnect -> - ereport.asic.zambezi.gpd.link-write-request-timeout@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-write-data-timeout@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-write-request-tid-invalid@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-unexpected-data-rcvd@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-unexpected-request-rcvd@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-write-tid-invalid@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-write-data-chunk-error@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-write-data-c2c-set@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-write-data-error-bit-set@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-invalid-write-request@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-write-data-bytemask-error@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-mapped-timeout@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-access-violation@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.gpd.link-invalid-read-request@interconnect - {IS_SECONDARY}; - -prop error.asic.ultraSPARC-T2plus.interconnect.gpd-c@interconnect -> - ereport.asic.zambezi.gpd.link-write-tid-invalid@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-write-data-chunk-error@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-write-data-c2c-set@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-write-data-error-bit-set@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-invalid-write-request@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-write-data-bytemask-error@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-mapped-timeout@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-access-violation@interconnect - {IS_PRIMARY}, - ereport.asic.zambezi.gpd.link-invalid-read-request@interconnect - {IS_PRIMARY}; - -prop error.asic.ultraSPARC-T2plus.interconnect.gpd@interconnect -> - ereport.asic.zambezi.gpd.jtag-access-violation@interconnect, - ereport.asic.zambezi.gpd.jtag-mapped-timeout@interconnect, - ereport.asic.zambezi.gpd.lpc-mapped-timeout@interconnect, - ereport.asic.zambezi.gpd.lpc-access-violation@interconnect, - ereport.asic.zambezi.gpd.lpc-rw-interleave-error@interconnect, - ereport.asic.zambezi.gpd.lpc-invalid-abort@interconnect, - ereport.asic.zambezi.gpd.lpc-invalid-start@interconnect, - ereport.asic.zambezi.gpd.lpc-invalid-cycle-type@interconnect; - -prop error.asic.fpga@motherboard (0) -> - ereport.asic.zambezi.gpd.lpc-invalid-abort@interconnect, - ereport.asic.zambezi.gpd.lpc-invalid-start@interconnect, - ereport.asic.zambezi.gpd.lpc-invalid-cycle-type@interconnect; - - -/* - * ASU Subsystem - */ -event ereport.asic.zambezi.asu.cam-parity-error@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.asu.invalid-nc-destid@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.asu.invalid-tid-cacheable@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.asu.invalid-tid-non-cacheable@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.asu.invalid-wb-destid@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.asu.malformed-wb@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.asu.pending-ram-parity-error@interconnect - {within(IMMEDIATE_DELAY)}; -event ereport.asic.zambezi.asu.pending-tid-ram-parity-error@interconnect - {within(IMMEDIATE_DELAY)}; - -/* - * Declare the intermediate errors that will be generated by the ereports - * in this subsystem. These errors will, in turn, propogate to the - * appropriate fault. - */ -event error.asic.ultraSPARC-T2plus.interconnect.asu.ignore@interconnect; -event error.asic.ultraSPARC-T2plus.interconnect.asu@interconnect; - - -/* - * Declare the upsets that may be diagnosed for this subsystem - */ -event upset.asic.ultraSPARC-T2plus.interconnect.asu.ignore@interconnect; - - -/* - * Declare the faults that may be generated for this subsystem. - */ -event fault.asic.ultraSPARC-T2plus.interconnect.asu@interconnect - FITrate=INTERCONNECT_ASU_FIT, ASRU=interconnect, FRU=motherboard; - - -/* - * Define how the intermediate errors propogate to faults for this subsystem. - */ -prop upset.asic.ultraSPARC-T2plus.interconnect.asu.ignore@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.asu.ignore@interconnect; - -prop fault.asic.ultraSPARC-T2plus.interconnect.asu@interconnect -> - error.asic.ultraSPARC-T2plus.interconnect.asu@interconnect; - - -prop error.cpu.ultraSPARC-T2plus.asu.protocol@chip[chip_num] (0) -> - ereport.asic.zambezi.asu.invalid-nc-destid@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.asu.invalid-tid-non-cacheable@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.asu.invalid-wb-destid@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.asu.malformed-wb@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}, - ereport.asic.zambezi.asu.invalid-tid-cacheable@interconnect - {IS_PRIMARY && MATCH_CPUID(chip_num)}; - -prop error.asic.ultraSPARC-T2plus.interconnect.asu.ignore@interconnect -> - ereport.asic.zambezi.asu.invalid-nc-destid@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.asu.invalid-tid-non-cacheable@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.asu.invalid-wb-destid@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.asu.malformed-wb@interconnect - {IS_SECONDARY}, - ereport.asic.zambezi.asu.invalid-tid-cacheable@interconnect - {IS_SECONDARY}; - -prop error.asic.ultraSPARC-T2plus.interconnect.asu@interconnect -> - ereport.asic.zambezi.asu.pending-ram-parity-error@interconnect, - ereport.asic.zambezi.asu.pending-tid-ram-parity-error@interconnect, - ereport.asic.zambezi.asu.cam-parity-error@interconnect; diff --git a/usr/src/cmd/fm/eversholt/native/sparc/Makefile b/usr/src/cmd/fm/eversholt/native/sparc/Makefile deleted file mode 100644 index 9af309e868..0000000000 --- a/usr/src/cmd/fm/eversholt/native/sparc/Makefile +++ /dev/null @@ -1,28 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2004 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# - -include ../../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/fmadm/sparc/Makefile b/usr/src/cmd/fm/fmadm/sparc/Makefile deleted file mode 100644 index 7bca6cefe5..0000000000 --- a/usr/src/cmd/fm/fmadm/sparc/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2004 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/fmd/sparc/Makefile b/usr/src/cmd/fm/fmd/sparc/Makefile deleted file mode 100644 index a2e4d5c324..0000000000 --- a/usr/src/cmd/fm/fmd/sparc/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2004 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../Makefile.cmd -include ../Makefile.fmd diff --git a/usr/src/cmd/fm/fmdump/sparc/Makefile b/usr/src/cmd/fm/fmdump/sparc/Makefile deleted file mode 100644 index 7bca6cefe5..0000000000 --- a/usr/src/cmd/fm/fmdump/sparc/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2004 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/fminject/sparc/Makefile b/usr/src/cmd/fm/fminject/sparc/Makefile deleted file mode 100644 index 7bca6cefe5..0000000000 --- a/usr/src/cmd/fm/fminject/sparc/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2004 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/fmstat/sparc/Makefile b/usr/src/cmd/fm/fmstat/sparc/Makefile deleted file mode 100644 index 7bca6cefe5..0000000000 --- a/usr/src/cmd/fm/fmstat/sparc/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2004 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/fmtopo/sparc/Makefile b/usr/src/cmd/fm/fmtopo/sparc/Makefile deleted file mode 100644 index 719d6803ef..0000000000 --- a/usr/src/cmd/fm/fmtopo/sparc/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License, Version 1.0 only -# (the "License"). You may not use this file except in compliance -# with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2006 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/ipmitopo/sparc/Makefile b/usr/src/cmd/fm/ipmitopo/sparc/Makefile deleted file mode 100644 index 16356f9dd8..0000000000 --- a/usr/src/cmd/fm/ipmitopo/sparc/Makefile +++ /dev/null @@ -1,28 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -include ../../../Makefile.cmd -include ../Makefile.com diff --git a/usr/src/cmd/fm/modules/Makefile b/usr/src/cmd/fm/modules/Makefile index dbdcfd3d13..bf4ddeb680 100644 --- a/usr/src/cmd/fm/modules/Makefile +++ b/usr/src/cmd/fm/modules/Makefile @@ -23,22 +23,6 @@ # Use is subject to license terms. # -sparc_SUBDIRS = sun4u \ - sun4v \ - SUNW,SPARC-Enterprise \ - SUNW,Netra-CP3060 \ - SUNW,Netra-CP3260 \ - SUNW,Sun-Blade-T6300 \ - SUNW,Sun-Blade-T6320 \ - SUNW,Netra-T5220 \ - SUNW,Sun-Fire-T200 \ - SUNW,Netra-T5440 \ - SUNW,T5140 \ - SUNW,USBRDT-5240 \ - SUNW,SPARC-Enterprise-T5120 - -i386_SUBDIRS = - -SUBDIRS = common $($(MACH)_SUBDIRS) +SUBDIRS = common include ../Makefile.subdirs diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/Makefile b/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/Makefile deleted file mode 100644 index 79eaa7bff8..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -SUBDIRS = etm - -include ../../Makefile.subdirs diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/etm/Makefile b/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/etm/Makefile deleted file mode 100644 index e4edf33b64..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/etm/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -PLATFORMS = SUNW,Netra-CP3060 - -include ../../sun4v/etm/Makefile.etm diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/etm/etm.conf b/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/etm/etm.conf deleted file mode 100644 index f90226df2c..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-CP3060/etm/etm.conf +++ /dev/null @@ -1,55 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# - -# transport these FMA events from the domain to the SP -subscribe fault.cpu.* -subscribe fault.memory.* -subscribe fault.io.fire.* -subscribe fault.io.pci.* -subscribe fault.io.pciex.* -subscribe list.repaired - -# -# etm agent properties: -# -# On supported systems, ETM can transport SP Alert event messages from the -# SP to Solaris. SP Alert messages are generated by the Service Processor -# and indicate various conditions monitored by the SP. The following -# properties define how those messages are handled by Solaris. -# -# etm_alert_console - bool - log messages to system console (default=false) -# etm_alert_syslogd - bool - log messages to messages file through -# syslogd (default=true) -# etm_alert_facility - string - syslog(3C) log facility to use -# (default=LOG_DAEMON) -# -# The "etm_alert_facility" property may only be configured to use -# LOG_DAEMON (which is the default) or one of LOG_LOCAL[0-7]. For -# information about the use of local log facilities, refer to syslog(3C), -# syslogd(8), and syslog.conf(5). -# -# Example settings: -# setprop etm_alert_console true -# setprop etm_alert_facility LOG_LOCAL0 -# diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/Makefile b/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/Makefile deleted file mode 100644 index 79eaa7bff8..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -SUBDIRS = etm - -include ../../Makefile.subdirs diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/etm/Makefile b/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/etm/Makefile deleted file mode 100644 index 3cec42ef09..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/etm/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -PLATFORMS = SUNW,Netra-CP3260 - -include ../../sun4v/etm/Makefile.etm diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/etm/etm.conf b/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/etm/etm.conf deleted file mode 100644 index 301291548c..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-CP3260/etm/etm.conf +++ /dev/null @@ -1,56 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# - -# transport these FMA events from the domain to the SP -subscribe fault.cpu.* -subscribe fault.memory.* -subscribe fault.io.fire.* -subscribe fault.io.pci.* -subscribe fault.io.pciex.* -subscribe fault.io.n2.* -subscribe list.repaired - -# -# etm agent properties: -# -# On supported systems, ETM can transport SP Alert event messages from the -# SP to Solaris. SP Alert messages are generated by the Service Processor -# and indicate various conditions monitored by the SP. The following -# properties define how those messages are handled by Solaris. -# -# etm_alert_console - bool - log messages to system console (default=false) -# etm_alert_syslogd - bool - log messages to messages file through -# syslogd (default=true) -# etm_alert_facility - string - syslog(3C) log facility to use -# (default=LOG_DAEMON) -# -# The "etm_alert_facility" property may only be configured to use -# LOG_DAEMON (which is the default) or one of LOG_LOCAL[0-7]. For -# information about the use of local log facilities, refer to syslog(3C), -# syslogd(8), and syslog.conf(5). -# -# Example settings: -# setprop etm_alert_console true -# setprop etm_alert_facility LOG_LOCAL0 -# diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-T5220/Makefile b/usr/src/cmd/fm/modules/SUNW,Netra-T5220/Makefile deleted file mode 100644 index 79eaa7bff8..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-T5220/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -SUBDIRS = etm - -include ../../Makefile.subdirs diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-T5220/etm/Makefile b/usr/src/cmd/fm/modules/SUNW,Netra-T5220/etm/Makefile deleted file mode 100644 index 2e291b1875..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-T5220/etm/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -PLATFORMS = SUNW,Netra-T5220 - -include ../../sun4v/etm/Makefile.etm diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-T5220/etm/etm.conf b/usr/src/cmd/fm/modules/SUNW,Netra-T5220/etm/etm.conf deleted file mode 100644 index 301291548c..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-T5220/etm/etm.conf +++ /dev/null @@ -1,56 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# - -# transport these FMA events from the domain to the SP -subscribe fault.cpu.* -subscribe fault.memory.* -subscribe fault.io.fire.* -subscribe fault.io.pci.* -subscribe fault.io.pciex.* -subscribe fault.io.n2.* -subscribe list.repaired - -# -# etm agent properties: -# -# On supported systems, ETM can transport SP Alert event messages from the -# SP to Solaris. SP Alert messages are generated by the Service Processor -# and indicate various conditions monitored by the SP. The following -# properties define how those messages are handled by Solaris. -# -# etm_alert_console - bool - log messages to system console (default=false) -# etm_alert_syslogd - bool - log messages to messages file through -# syslogd (default=true) -# etm_alert_facility - string - syslog(3C) log facility to use -# (default=LOG_DAEMON) -# -# The "etm_alert_facility" property may only be configured to use -# LOG_DAEMON (which is the default) or one of LOG_LOCAL[0-7]. For -# information about the use of local log facilities, refer to syslog(3C), -# syslogd(8), and syslog.conf(5). -# -# Example settings: -# setprop etm_alert_console true -# setprop etm_alert_facility LOG_LOCAL0 -# diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-T5440/Makefile b/usr/src/cmd/fm/modules/SUNW,Netra-T5440/Makefile deleted file mode 100644 index 79eaa7bff8..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-T5440/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -SUBDIRS = etm - -include ../../Makefile.subdirs diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-T5440/etm/Makefile b/usr/src/cmd/fm/modules/SUNW,Netra-T5440/etm/Makefile deleted file mode 100644 index 82a04dec99..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-T5440/etm/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -PLATFORMS = SUNW,Netra-T5440 - -include ../../sun4v/etm/Makefile.etm diff --git a/usr/src/cmd/fm/modules/SUNW,Netra-T5440/etm/etm.conf b/usr/src/cmd/fm/modules/SUNW,Netra-T5440/etm/etm.conf deleted file mode 100644 index 463952123c..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,Netra-T5440/etm/etm.conf +++ /dev/null @@ -1,58 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# - -# transport these FMA events from the domain to the SP -subscribe fault.cpu.* -subscribe fault.memory.* -subscribe fault.io.fire.* -subscribe fault.io.pci.* -subscribe fault.io.pciex.* -subscribe fault.io.n2.* -subscribe fault.io.vf.* -subscribe fault.asic.ultraSPARC-T2plus.* -subscribe list.repaired - -# -# etm agent properties: -# -# On supported systems, ETM can transport SP Alert event messages from the -# SP to Solaris. SP Alert messages are generated by the Service Processor -# and indicate various conditions monitored by the SP. The following -# properties define how those messages are handled by Solaris. -# -# etm_alert_console - bool - log messages to system console (default=false) -# etm_alert_syslogd - bool - log messages to messages file through -# syslogd (default=true) -# etm_alert_facility - string - syslog(3C) log facility to use -# (default=LOG_DAEMON) -# -# The "etm_alert_facility" property may only be configured to use -# LOG_DAEMON (which is the default) or one of LOG_LOCAL[0-7]. For -# information about the use of local log facilities, refer to syslog(3C), -# syslogd(8), and syslog.conf(5). -# -# Example settings: -# setprop etm_alert_console true -# setprop etm_alert_facility LOG_LOCAL0 -# diff --git a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/Makefile b/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/Makefile deleted file mode 100644 index 79eaa7bff8..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -SUBDIRS = etm - -include ../../Makefile.subdirs diff --git a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/etm/Makefile b/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/etm/Makefile deleted file mode 100644 index 41a63cd804..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/etm/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -PLATFORMS = SUNW,SPARC-Enterprise-T5120 - -include ../../sun4v/etm/Makefile.etm diff --git a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/etm/etm.conf b/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/etm/etm.conf deleted file mode 100644 index 301291548c..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise-T5120/etm/etm.conf +++ /dev/null @@ -1,56 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# - -# transport these FMA events from the domain to the SP -subscribe fault.cpu.* -subscribe fault.memory.* -subscribe fault.io.fire.* -subscribe fault.io.pci.* -subscribe fault.io.pciex.* -subscribe fault.io.n2.* -subscribe list.repaired - -# -# etm agent properties: -# -# On supported systems, ETM can transport SP Alert event messages from the -# SP to Solaris. SP Alert messages are generated by the Service Processor -# and indicate various conditions monitored by the SP. The following -# properties define how those messages are handled by Solaris. -# -# etm_alert_console - bool - log messages to system console (default=false) -# etm_alert_syslogd - bool - log messages to messages file through -# syslogd (default=true) -# etm_alert_facility - string - syslog(3C) log facility to use -# (default=LOG_DAEMON) -# -# The "etm_alert_facility" property may only be configured to use -# LOG_DAEMON (which is the default) or one of LOG_LOCAL[0-7]. For -# information about the use of local log facilities, refer to syslog(3C), -# syslogd(8), and syslog.conf(5). -# -# Example settings: -# setprop etm_alert_console true -# setprop etm_alert_facility LOG_LOCAL0 -# diff --git a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/Makefile b/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/Makefile deleted file mode 100644 index ecea0e4fb9..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/Makefile +++ /dev/null @@ -1,29 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2006 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" - -SUBDIRS = event-transport cpumem-retire - -include ../../Makefile.subdirs diff --git a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/cpumem-retire/Makefile b/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/cpumem-retire/Makefile deleted file mode 100644 index 5ca1dfcbbb..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/cpumem-retire/Makefile +++ /dev/null @@ -1,57 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2008 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# - -PLATFORMS = SUNW,SPARC-Enterprise -CLASS = plat -MODULE = cpumem-retire - -CPUMEM_RETIRE_COMMON = ../../common/$(MODULE) - -INCDIRS += . -INCDIRS += $(CPUMEM_RETIRE_COMMON) - -SRCS = \ - cma_main.c \ - cma_cpu.c \ - cma_cpu_arch.c \ - cma_page.c \ - cma_page_arch.c - -include ../../Makefile.plugin - -CMA_VERSION = "1.1" - - -LIBDIRS = $(ROOT)/usr/platform/$(PLATFORMS)/lib -CPPFLAGS += $(INCDIRS:%=-I%) -DCMA_VERSION='$(CMA_VERSION)' -Dopl -LDFLAGS += -R/usr/lib/fm -LDLIBS += -L$(ROOTLIB)/fm -lfmd_agent - -%.o: $(CPUMEM_RETIRE_COMMON)/%.c - $(COMPILE.c) -o $@ $< - $(CTFCONVERT_O) - -%.ln: $(CPUMEM_RETIRE_COMMON)/%.c - $(LINT.c) -c $< diff --git a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/cpumem-retire/cpumem-retire.conf b/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/cpumem-retire/cpumem-retire.conf deleted file mode 100644 index 96cef6e863..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/cpumem-retire/cpumem-retire.conf +++ /dev/null @@ -1,39 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2006 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#pragma ident "%Z%%M% %I% %E% SMI" - -# -# cpumem-retire -# -setprop cpu_tries 10 -setprop cpu_delay 1sec -# -setprop page_ret_mindelay 1sec -setprop page_ret_maxdelay 5min -# -setprop cpu_offline_enable true -setprop cpu_forced_offline true -setprop cpu_blacklist_enable false -setprop page_retire_enable true diff --git a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/Makefile b/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/Makefile deleted file mode 100644 index c9a3f21f3f..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/Makefile +++ /dev/null @@ -1,36 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2006 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# - -PLATFORMS = SUNW,SPARC-Enterprise - -$(PLATFORMS)_SRCS = ex_dscp.c - -LIBDIRS = $(ROOT)/usr/platform/$(PLATFORMS)/lib -LIBFLAGS = \$$ORIGIN/../../../../lib -XPORTLIBS = -lsocket -lnsl -ldscp - -include ../../common/event-transport/Makefile.etm - -CERRWARN += -_gcc=-Wno-parentheses diff --git a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/event-transport.conf b/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/event-transport.conf deleted file mode 100644 index 739e04eb72..0000000000 --- a/usr/src/cmd/fm/modules/SUNW,SPARC-Enterprise/event-transport/event-transport.conf +++ /dev/null @@ -1,88 +0,0 @@ -# -# CDDL HEADER START -# -# The contents of this file are subject to the terms of the -# Common Development and Distribution License (the "License"). -# You may not use this file except in compliance with the License. -# -# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE -# or http://www.opensolaris.org/os/licensing. -# See the License for the specific language governing permissions -# and limitations under the License. -# -# When distributing Covered Code, include this CDDL HEADER in each -# file and include the License file at usr/src/OPENSOLARIS.LICENSE. -# If applicable, add the following below this CDDL HEADER, with the -# fields enclosed by brackets "[]" replaced with your own identifying -# information: Portions Copyright [yyyy] [name of copyright owner] -# -# CDDL HEADER END -# -# -# Copyright 2006 Sun Microsystems, Inc. All rights reserved. -# Use is subject to license terms. -# -#ident "%Z%%M% %I% %E% SMI" -# -# fmd configuration file for the event-transport.so plugin module. -# -# The following configuration options are valid: -# -# setprop reconnect_timeout