lkml.org 
[lkml]   [2007]   [Nov]   [14]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateWed, 14 Nov 2007 20:05:01 +0100
FromIngo Molnar <>
SubjectRe: [bug] SLOB crash, 2.6.24-rc2
* Matt Mackall <mpm@selenic.com> wrote:

> > > [   61.245190] rc.sysinit used greatest stack depth: 1680 bytes left
> > > [   61.386859] list_add corruption. prev->next should be next (407d973c), but was 418cf818. (prev=41877098).
> > > [   61.396328] ------------[ cut here ]------------
> > > [   61.400910] kernel BUG at lib/list_debug.c:33!
> > > [   61.405330] invalid opcode: 0000 [#1] DEBUG_PAGEALLOC
> > > 
> > > looks like memory corruption of some sort and it's reproducible. Picking 
> > > CONFIG_SLUB makes the crash go away. Booting v2.6.23 with the same 
> > > .config works fine.
> > 
> > Hmmm, the changes in SLOB since v2.6.23 are all trivial. I'll try to 
> > reproduce it with your config, but it doesn't seem promising.
> 
> Couldn't reproduce it here, let me know if you get anywhere with your 
> bisect.

the bug went away - and the only thing i did was a networking config 
tweak. So maybe something in networking corrupts memory? I'm not sure i 
can restore the old state. (i had lots of problems with net interface 
renaming not working in .24)

	Ingo
-
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/

\
 
 \ /
  Last update: 2007-11-14 20:09    [from the cache]
©2003-2008