Messages in this thread | | | Date | Thu, 2 Feb 2006 20:38:10 +0100 | From | Jesper Juhl <> | Subject | Re: discriminate single bit error hardware failure from slab corruption. |
| |
On 2/2/06, Dave Jones <davej@redhat.com> 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. > May I suggest that the text be Single bit error detected. Possibly bad RAM. Please run memtest86 and/or memtest86+.
both programs are good memory testers, but they are different and sometimes one finds problems not detected by the other.
-- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - 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/
| |