Date: Thu, 6 Apr 2000 10:13:25 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: J McKitrick <jcm@freebsd-uk.eu.org> Cc: hackers@FreeBSD.ORG Subject: Re: bad memory patch? Message-ID: <20000406101325.C10876@orion.ac.hmc.edu> In-Reply-To: <20000406164114.B29984@dogma.freebsd-uk.eu.org>; from jcm@freebsd-uk.eu.org on Thu, Apr 06, 2000 at 04:41:15PM %2B0100 References: <20000406164114.B29984@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 06, 2000 at 04:41:15PM +0100, J McKitrick wrote: > I saw this link recently... > > http://home.zonnet.nl/vanrein/badram/ > > Apparently, you make a floppy with the supplied image, boot with it to > find the bad RAM addresses, and then those addresses are passed on as a > kernel parameter once the patch is applied. Bad addresses will be excluded > from addressable/virtual memory from then on. > > Sounds like sometheing we could use, eh? Not really. If you run it and it says the RAM is bad you know it's bad. If you run it and it says the RAM is good, then you whine and batch and moan for weeks, if not months, that FreeBSD is busted and your machine is perfectly functional until you finaly replace the RAM and the problem goes away. This is not what we want to see. The problem is that testing can't prove correctness because it can't try EVERY possiable access combination. -- Brooks P.S. The "you" in the above doens't refer to the poster, it refers to the poor sucker with a problem who tries to use this so called tool. -- Any statement of the form "X is the one, true Y" is FALSE. 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?20000406101325.C10876>