From owner-freebsd-hackers Thu Apr 6 8:41:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 4754837C153 for ; Thu, 6 Apr 2000 08:41:18 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for hackers@freebsd.org id 12dEPD-000KjV-00; Thu, 6 Apr 2000 16:41:15 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id QAA30067 for hackers@freebsd.org; Thu, 6 Apr 2000 16:41:15 +0100 (BST) (envelope-from jcm) Date: Thu, 6 Apr 2000 16:41:15 +0100 From: J McKitrick To: hackers@freebsd.org Subject: bad memory patch? Message-ID: <20000406164114.B29984@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message