From owner-freebsd-questions@FreeBSD.ORG Sun Aug 15 15:49:49 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABA0216A4CE for ; Sun, 15 Aug 2004 15:49:49 +0000 (GMT) Received: from web50806.mail.yahoo.com (web50806.mail.yahoo.com [206.190.38.115]) by mx1.FreeBSD.org (Postfix) with SMTP id 370FD43D2D for ; Sun, 15 Aug 2004 15:49:49 +0000 (GMT) (envelope-from plaur_27@yahoo.de) Message-ID: <20040815154948.28008.qmail@web50806.mail.yahoo.com> Received: from [217.81.146.97] by web50806.mail.yahoo.com via HTTP; Sun, 15 Aug 2004 17:49:48 CEST Date: Sun, 15 Aug 2004 17:49:48 +0200 (CEST) From: =?iso-8859-1?q?Laurentiu=20Pancescu?= To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: dealing with deffective RAM X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Aug 2004 15:49:49 -0000 Hello! Both Memtest86 and Memtest86+ find some failures in RAM (one finds 11 faults, the other 14 - most 32-bit, but some are only 8-bit wide). How can I deal with this in FreeBSD? Buying new RAM modules is probably the best choice, but I have no guarantee that the new modules will be perfectly ok, so it might be wasted money. Under Linux, I used the badram patch (http://rick.vanrein.org/linux/badram/). Is there similar functionality in the FreeBSD kernel, or is there such a patch? I failed to find anything on Google, and boot(8) didn't help much, either. In case such a patch doesn't exist, do you have any ideas about how such a thing might be implemented? Eventually, could you point me to the right place in the kernel source? I use Linux since 1997, but I'm pretty much a FreeBSD newbie, so please be merciful... :) Best regards, Laurentiu P.S. I assume the physical pages (4k/4M) where the faults reside could just be not mapped at all in the virtual memory manager, so it should be doable, right? ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de