[fm-discuss] Fmadm faulty not working

[Matty]

Howdy,

While doing some testing on a Sun Enterprise 4500, I started to get 100s of messages similar to the following:

Feb  9 17:16:32 rx SUNW,UltraSPARC-II: WARNING: [AFT0] Sticky Softerror
encountered on Memory Module Board 2 J3800
Feb  9 17:16:32 rx unix: NOTICE: Scheduling removal of page 0x00000001.e
e41e258
Feb  9 17:16:32 rx SUNW,UltraSPARC-II: WARNING: [AFT0] Sticky Softerror
encountered on Memory Module Board 2 J3800
Feb  9 17:16:32 rx last message repeated 1 time
Feb  9 17:16:32 rx unix: NOTICE: Page 0x00000001.ee41e000 removed from s
ervice
Feb  9 17:16:32 rx SUNW,UltraSPARC-II: WARNING: [AFT0] Sticky Softerror
encountered on Memory Module Board 2 J3800
Feb  9 17:16:32 rx unix: NOTICE: Scheduling removal of page 0x00000001.e
e41a258
Feb  9 17:16:32 rx SUNW,UltraSPARC-II: WARNING: [AFT0] Sticky Softerror
encountered on Memory Module Board 2 J3800
Feb  9 17:16:32 rx last message repeated 19 times
Feb  9 17:16:32 rx unix: NOTICE: Page 0x00000001.ee41a000 removed from s
ervice

When I run fmdump to view the error log, I see lots of entries:

# fmdump -e -v
TIME                 CLASS                                 ENA
Feb 09 11:51:13.3956 ereport.fm.fmd.rtld_open              0x094b2d882a304001
Feb 09 11:51:13.4155 ereport.fm.fmd.mod_init               0x094b406e52300401
Feb 09 12:50:34.4480 ereport.io.psy.ecc.drce               0x3d1d21bfdd602001
Feb 09 12:50:40.4402 ereport.io.psy.ecc.s-drce             0x3d33744e05501001
Feb 09 12:50:40.4402 ereport.io.psy.ecc.drce               0x3d33744e05501001
Feb 09 12:55:31.9174 ereport.io.psy.ecc.drce               0x41714aa7af302001
Feb 09 12:55:37.9102 ereport.io.psy.ecc.s-drce             0x41879dce19d00401
Feb 09 12:55:37.9102 ereport.io.psy.ecc.drce               0x41879dce19d00401
 < .....>

But when I run fmadm faulty to view the faulty DIMM, nothing shows up:

# fmadm faulty
   STATE RESOURCE / UUID
-------- ---------------------------------------------------------------------

Shouldn't the faulty DIMM(s) show up in the fmadm faulty output?

Thanks for any insight,
- Ryan
-- 
UNIX Administrator
http://prefetch.net
--
This message posted from opensolaris.org