Date: Tue, 14 Mar 2000 12:12:42 -0500 From: Robert Sexton <robert@kudra.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Detecting ECC errors Message-ID: <20000314121241.A6090@tabby.kudra.com> In-Reply-To: <38CC07F7.B55F708B@gorean.org>; from Doug Barton on Sun, Mar 12, 2000 at 01:11:19PM -0800 References: <200003121934.LAA08972@mass.cdrom.com> <38CC07F7.B55F708B@gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 12, 2000 at 01:11:19PM -0800, Doug Barton wrote: > CC'ing -hackers in case we can scare up some interest . . . > > Mike Smith wrote: > > > > > Hi. I took a look over the archives and noticed this ancient > > > thread. (1998) However, I checked the handbook and LINT for options on > > > how FreeBSD logs ECC errors, but I could not find anything. Has this > > > finally been implemented? Or is there currently no way for the OS to > > > detect the # of corrections / detections of errors by DIMM slot? > > > > You're correct; there isn't. It's a relatively simple task that's been > > waiting for a junior hacker to come along and take it up. It's also > > devillishly difficult to _test_ such code... I just spent some time reading the datasheets for the HX chipset (Intels Pentium) and 440BX chipsets, and playing with pciconf. These chipsets will report the ram configuration in terms banks and amounts, and are capable of telling you where the problem is. In the case of the BX, you can get a specific address, while the HX can only tell you which simm is causing the error. All of the hooks are there for true memory error reporting and scrubbing, at least for the two intel chipsets I've seen. -- Robert Sexton - robert@kudra.com, Cincinnati OH, USA "They believe in `peace, justice, morality, culture, sport, family life, and the obliteration of all other life forms" - Douglas Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000314121241.A6090>