Re: discriminate single bit error hardware failure from slab corruption.

On 2/2/06, Dave Jones <[email protected]> wrote:
> In the 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. Please run memtest86.
>
> Signed-off-by: Dave Jones <[email protected]>

Looks good to me.

                          Pekka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • discriminate single bit error hardware failure from slab corruption.
    • From: Dave Jones <[email protected]>

• Prev by Date: Re: GPL V3 and Linux - Dead Copyright Holders
• Next by Date: Wanted: hotfixes for -mm kernels
• Previous by thread: Re: discriminate single bit error hardware failure from slab corruption.
• Next by thread: Re: discriminate single bit error hardware failure from slab corruption.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]