Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264835AbTGBImH (ORCPT ); Wed, 2 Jul 2003 04:42:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264839AbTGBImH (ORCPT ); Wed, 2 Jul 2003 04:42:07 -0400 Received: from web11803.mail.yahoo.com ([216.136.172.157]:57479 "HELO web11803.mail.yahoo.com") by vger.kernel.org with SMTP id S264835AbTGBImG (ORCPT ); Wed, 2 Jul 2003 04:42:06 -0400 Message-ID: <20030702085630.55048.qmail@web11803.mail.yahoo.com> Date: Wed, 2 Jul 2003 10:56:30 +0200 (CEST) From: =?iso-8859-1?q?Etienne=20Lorrain?= Subject: Re: [PATCH] BadRAM for 2.5.73-mm2 To: linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1031 Lines: 21 Nowdays the biggest problem seems to be slightly incompatible timings in between motherboard and physical RAM that hurts the most, not so much non-working bits in RAM devices. Is there someone who has a patch so that, in case of a kernel OOPS (or maybe SIGSEGV / SIGILL outside kernel) is checking at least the code page where IP register points to check if a bit has flipped? Could be done by checking the page on the Hard Disk or by a CRC method. Having a bad BIOS parameter so that _one_ bit changes randomly every hours is not an easy thing to detect - a message on the screen would be nice... Etienne. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran?ais ! Yahoo! Mail : http://fr.mail.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/