Re: 2.6.18-mm2 boot failure on x86-64 II

2006-10-05 Thread Andrew Morton
On Thu, 05 Oct 2006 17:02:54 -0700 Badari Pulavarty <[EMAIL PROTECTED]> wrote: > > Code: 0f 0b 48 8b 3d 15 ab 1e 00 be d0 00 00 00 e8 c0 f5 ff ff 48 > > RIP [] init_list+0x1d/0xfd > > RSP > > <0>Kernel panic - not syncing: Attempted to kill the idle task! > > > > > > I am going to revert the p

Re: 2.6.18-mm2 boot failure on x86-64 II

2006-10-05 Thread Badari Pulavarty
keith mannthey wrote: On Fri, 2006-10-06 at 01:35 +0200, Andi Kleen wrote: As of yet I haven't been able to recreate the hang. I am running similar HW to Steve. I ran into this with -mm3 Memory: 24150368k/26738688k available (1933k kernel code, 490260k reserved, 978k data, 308k in

Re: 2.6.18-mm2 boot failure on x86-64 II

2006-10-05 Thread keith mannthey
On Fri, 2006-10-06 at 01:35 +0200, Andi Kleen wrote: > > As of yet I haven't been able to recreate the hang. I am running > > similar HW to Steve. I ran into this with -mm3 Memory: 24150368k/26738688k available (1933k kernel code, 490260k reserved, 978k data, 308k init) [ cut here ]

Re: 2.6.18-mm2 boot failure on x86-64 II

2006-10-05 Thread Andi Kleen
> As of yet I haven't been able to recreate the hang. I am running > similar HW to Steve. That was on a 4 core Opteron with Tyan board (S2881) and AMD-8111 chipset. -Andi - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More ma

Re: 2.6.18-mm2 boot failure on x86-64 II

2006-10-05 Thread keith mannthey
On Fri, 2006-10-06 at 01:14 +0200, Andi Kleen wrote: > On Thursday 05 October 2006 22:51, Andi Kleen wrote: > > > > > hmm, rather than bugging you with patches now, I'll see what I can find > > > with the x86_64 machines I have access to and see can I reproduce it. > > > > I started the bisect,

Re: 2.6.18-mm2 boot failure on x86-64 II

2006-10-05 Thread Andi Kleen
On Thursday 05 October 2006 22:51, Andi Kleen wrote: > > > hmm, rather than bugging you with patches now, I'll see what I can find > > with the x86_64 machines I have access to and see can I reproduce it. > > I started the bisect, should finish soon. It ended at diff-tree d5cdb67236dba94496de