Date: Mon, 13 Mar 2000 10:30:20 -0500 From: Robert Sexton <robert@kudra.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Detecting ECC errors Message-ID: <20000313103020.B1783@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 bet a call for bad simms would dredge up a few. I have a machine on my desk that double bits about twice a week right now. Any takers? :-) -- Robert Sexton - robert@kudra.com, Cincinnati OH, USA Build a man a fire, and he's warm for the rest of the night. Set a man on fire, and he's warm for the rest of his life - Terry Pratchett, "Jingo" 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?20000313103020.B1783>