On Fri, 6 Jun 2008 09:25:36 +0200 Ingo Molnar [off-list ref] wrote:

* Ingo Molnar [off-list ref] wrote:

quoted

* Andrew Morton [off-list ref] wrote:

quoted

On Thu, 5 Jun 2008 17:52:17 +1000 Stephen Rothwell [off-list ref] wrote:

quoted

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git

Instantly oopses on two x86_64 boxes with this config:
http://userweb.kernel.org/~akpm/config-akpm2.txt

oops: http://userweb.kernel.org/~akpm/p6056454.jpg

At a guess I'd say the sched_domains code is calling into slab before 
slab is initalised.  Something like that.

did SLUB change in linux-next? There is no such problem in -tip.

i just successfully booted your config on 4 separate 64-bit test-systems 
with latest -tip. (two dual-core boxes, a quad and a 16way box) Latest 
-tip includes sched-next and x86-next as well.

What's the point in testing a radically differenet kernel from the one
which is known to be crashing?