LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Pavel Machek <pavel@suse.cz>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] corruption checker: print the DMI board name
Date: Thu, 30 Oct 2008 06:28:30 -0700	[thread overview]
Message-ID: <20081030062830.31023884@infradead.org> (raw)
In-Reply-To: <20081030110653.GA7291@atrey.karlin.mff.cuni.cz>

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

> > 
> > >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"

> 
>   
> > Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
> 
> But ACK -- we certainly want to see the data.

      reply	other threads:[~2008-10-30 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 16:17 Arjan van de Ven
2008-10-29 16:27 ` [PATCH] corruption checker: print the DMI board name on corruption Arjan van de Ven
2008-10-29 16:36   ` Ingo Molnar
2008-10-30 11:06 ` [PATCH] corruption checker: print the DMI board name Pavel Machek
2008-10-30 13:28   ` Arjan van de Ven [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081030062830.31023884@infradead.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@suse.cz \
    --subject='Re: [PATCH] corruption checker: print the DMI board name' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).