On Thu, 30 Oct 2008 12:06:53 +0100
Pavel Machek <pavel@suse.cz> wrote:

quoted text
> > 
> > >From 4f829eef5a31b68a0cbaf83a75ac8b0a1ed05afb Mon Sep 17 00:00:00
> > >2001
> > From: Arjan van de Ven <arjan@linux.intel.com>
> > Date: Wed, 29 Oct 2008 09:13:23 -0700
> > Subject: [PATCH] corruption checker: print the DMI board name
> > 
> > when the memory corruptor checker hits (as it has done now based on
> > kerneloops.org data), it would be extremely useful to know the DMI
> > board name so we can add a blacklist for such a machine... without
> > having to ask the user for lots of extra info.
> 
> I'm not sure if blacklisting whole brand for one case of bit
> corruption is fair -- perhaps the memory was overheating?

this is where kerneloops.org comes in; we can separate the "happens a
lot" from "happens on blue moons"

quoted text
> 
>   
> > Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
> 
> But ACK -- we certainly want to see the data.
--
unsubscribe notice
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/