Hi Marco, On 3/14/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:
Hello everybody. Sorry for posting to this list, but I'm pretty lost.
Don't worry, this is the proper mailing list for bug reports. On 3/14/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:
I don't think this is related to buggy hardware because it is happening on 3 different boxes with the same hardware config.
No, looks like someone is feeding a bad pointer to slab. The debug check is relatively new and in previous kernels the problem would might have gone unnoticed causing silent corruption of the slab. On 3/14/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:
ksymoops 2.4.10 on i686 2.6.20. Options used
From Documentation/oops-tracing.txt:
"NOTE: ksymoops is useless on 2.6. Please use the Oops in its original format (from dmesg, etc). Ignore any references in this or other docs to "decoding the Oops" or "running it through ksymoops". If you post an Oops from 2.6 that has been run through ksymoops, people will just tell you to repost it." So, can you please repost the original oops? Also, please enable CONFIG_DEBUG_SLAB and try to reproduce. Thanks. - 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/
