All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McLean <pmclean@cs.ubishops.ca>
To: Dave Jones <davej@redhat.com>, Andreas Schwab <schwab@suse.de>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: single bit flip detector.
Date: Wed, 02 Aug 2006 11:24:13 -0400	[thread overview]
Message-ID: <44D0C39D.7040408@cs.ubishops.ca> (raw)
In-Reply-To: <20060802001626.GA14689@redhat.com>

Dave Jones wrote:
> On Tue, Aug 01, 2006 at 07:51:09PM -0400, Dave Jones wrote:
>  > I'm going for the record of 'most times a patch gets submitted in one day'.
>  > And to think we were complaining that patches don't get enough review ? :)
>  > If every change had this much polish, we'd be awesome.
> 
> Sigh. Spaces before printk. Whatever next.
> I am now officially bored of seeing this patch.
> 
> 		Dave
> 
> 
> In case where we detect a single bit has been flipped, we spew
> the usual slab corruption message, which users instantly think
> is a kernel bug.  In a lot of cases, single bit errors are
> down to bad memory, or other hardware failure.
> 
> This patch adds an extra line to the slab debug messages
> in those cases, in the hope that users will try memtest before
> they report a bug.
> 
> 000: 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
> Single bit error detected. Possibly bad RAM. Run memtest86.
> 
> Signed-off-by: Dave Jones <davej@redhat.com>
> 
> +		if (errors && !(errors & (errors-1))) {
> +			printk(KERN_ERR "Single bit error detected. Probably bad RAM.\n");
> +#ifdef CONFIG_X86

#if defined(CONFIG_X86) || defined(CONFIG_X86_64)

memtest86+ runs fine on x86_64 machines as well.

> +			printk(KERN_ERR "Run memtest86+ or a similar memory test tool.\n");
> +#else
> +			printk(KERN_ERR "Run a memory test tool.\n");

  parent reply	other threads:[~2006-08-02 15:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 18:44 single bit flip detector Dave Jones
2006-08-01 20:15 ` Bill Davidsen
2006-08-01 22:14 ` Alan Cox
2006-08-01 22:30   ` Dave Jones
2006-08-01 22:36     ` Dave Jones
2006-08-01 23:00       ` Alexey Dobriyan
2006-08-01 23:16         ` Dave Jones
2006-08-01 23:27           ` Dave Jones
2006-08-01 23:28           ` Andreas Schwab
2006-08-01 23:51             ` Dave Jones
2006-08-02  0:16               ` Dave Jones
2006-08-02  6:20                 ` Rolf Eike Beer
2006-08-02  7:08                 ` Jan Engelhardt
2006-08-06 11:05                   ` Geert Uytterhoeven
2006-08-02 15:24                 ` Patrick McLean [this message]
2006-08-02 16:12                   ` Randy.Dunlap
2006-08-04 21:19                 ` Andrew Morton
2006-08-04 22:06                   ` Dave Jones
2006-08-04 22:25                     ` Andrew Morton
2006-08-04 22:28                       ` Dave Jones
2006-08-02  7:08         ` Jan Engelhardt

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=44D0C39D.7040408@cs.ubishops.ca \
    --to=pmclean@cs.ubishops.ca \
    --cc=adobriyan@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@suse.de \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.