Re: single bit flip detector.

From: Dave Jones
Date: Tue Aug 01 2006 - 20:14:27 EST

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.


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@xxxxxxxxxx>

diff --git a/mm/slab.c b/mm/slab.c
index 21ba060..39f1183 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -1638,10 +1638,28 @@ static void poison_obj(struct kmem_cache
static void dump_line(char *data, int offset, int limit)
int i;
+ unsigned char total = 0, bad_count = 0, errors;
printk(KERN_ERR "%03x:", offset);
- for (i = 0; i < limit; i++)
+ for (i = 0; i < limit; i++) {
+ if (data[offset + i] != POISON_FREE) {
+ total += data[offset + i];
+ bad_count++;
+ }
printk(" %02x", (unsigned char)data[offset + i]);
+ }
+ if (bad_count == 1) {
+ errors = total ^ POISON_FREE;
+ if (errors && !(errors & (errors-1))) {
+ printk(KERN_ERR "Single bit error detected. Probably bad RAM.\n");
+#ifdef CONFIG_X86
+ printk(KERN_ERR "Run memtest86+ or a similar memory test tool.\n");
+ printk(KERN_ERR "Run a memory test tool.\n");
+ }
+ }

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at