Messages in this thread | | | Date | Sat, 31 Jul 2010 12:06:22 +0200 | Subject | Re: Regression 2.6.33->2.6.34: OOPS at boot, kmalloc corruption? | From | Torsten Kaiser <> |
| |
On Tue, Jul 20, 2010 at 10:19 PM, Christoph Lameter <cl@linux-foundation.org> wrote: > 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.
I finally had the opportunity to reboot this system again.
CONFIG_SLUB_DEBUG=y was set, so I tried adding slub_debug to the commandline.
With slub_debug added the system boots normal, I could not see any errors in the syslog. When I remove slub_debug it crashed againb before reaching userspace.
After the KMS fixes from Alex Deucher vanilla kernel 2.6.35-rc6 works for me. So I would thing my problems with earlier 2.6.35-rcs where just these KMS errors and this kmalloc problem has already been fixed in mainline.
So I have switched this system to 2.6.35-rc6 and will stay with this kernel.
Thanks, Torsten
| |