Re: Regression 2.6.33->2.6.34: OOPS at boot, kmalloc corruption?

From: Christoph Lameter
Date: Tue Jul 20 2010 - 16:23:48 EST

Next message: Stefan Sitter: "Scrambled console with cirrusfb.c on old Compaq Armada 4120 (and not well-documented boot option as a workaround)"
Previous message: H. Peter Anvin: "Re: [PATCH 00/10] x86, xsave: some code cleanups and reworks"
In reply to: Pekka Enberg: "Re: Regression 2.6.33->2.6.34: OOPS at boot, kmalloc corruption?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 20 Jul 2010, Pekka Enberg wrote:

> It's slab corruption that can be cause by many things. Can you please
> try to reproduce with CONFIG_SLUB_DEBUG_ON=y?

Or simply reboot and add a parameter slub_debug to the other parameters.

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

Next message: Stefan Sitter: "Scrambled console with cirrusfb.c on old Compaq Armada 4120 (and not well-documented boot option as a workaround)"
Previous message: H. Peter Anvin: "Re: [PATCH 00/10] x86, xsave: some code cleanups and reworks"
In reply to: Pekka Enberg: "Re: Regression 2.6.33->2.6.34: OOPS at boot, kmalloc corruption?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]