From owner-freebsd-current Thu Apr 6 12:26:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BDAC437B926; Thu, 6 Apr 2000 12:26:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA76532; Thu, 6 Apr 2000 12:26:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 6 Apr 2000 12:26:22 -0700 (PDT) From: Kris Kennaway To: J McKitrick Cc: current@freebsd.org Subject: Re: bad memory patch? In-Reply-To: <20000406163815.A29984@dogma.freebsd-uk.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, 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? It's not possible to find bad RAM deterministically from software..if you have bad RAM, you need to replace it, end of story. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message