From: Ingo Molnar <mingo@elte.hu>
Date: Wed, 14 Nov 2007 20:05:01 +0100

quoted text
> the bug went away - and the only thing i did was a networking config 
> tweak. So maybe something in networking corrupts memory?

This wouldn't surprise me at all.

I think we can make some headway on this bug, the next time
you trigger it, if the list debugging was a little less terse.

For example, a backtrace and perhaps even feeding the bad list
pointers in question to the SLAB/SLUB debug helpers that can
identify a kmem cache from a given pointer would help.

Thanks.
-
unsubscribe notice
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/