Re: [PATCH] Fix early panic issue on machines with memless node

[David Rientjes]

On Tue, 5 May 2009, Jack Steiner wrote:

> I was able to duplicate your original problem. Your patch below solves the
> problem. AFAICT, it causes no new reqgressions to the various configurations
> that I'm testing. (I'll add the "mem=2G" to my configs that I test).
> 

Great, it would be helpful to catch these problems before 2.6.30 is 
released.  I've passed my patch along to Ingo.

> However, I see a new regression that was not present a couple of weeks ago.
> Configurations that have nodes with cpus and no memory panic during
> boot. This occurs both with and without your patch and is not related to "mem=".
> 
> I need to isolate the problem but here is the stack trace. :
> 	Pid: 0, comm: swapper Not tainted 2.6.30-rc4-next-20090505-medusa #12
> 	Call Trace:
> 	 [<ffffffff806b919e>] early_idt_handler+0x5e/0x71
> 	 [<ffffffff802920fe>] ? build_zonelists_node+0x4c/0x8d
> 	 [<ffffffff8029333f>] __build_all_zonelists+0x1ae/0x55a
> 	 [<ffffffff80293932>] build_all_zonelists+0x1b5/0x263
> 	 [<ffffffff806b9b6e>] start_kernel+0x17a/0x3c5
> 	 [<ffffffff806b9140>] ? early_idt_handler+0x0/0x71
> 	 [<ffffffff806b92a7>] x86_64_start_reservations+0xae/0xb2
> 	 [<ffffffff806b93fd>] x86_64_start_kernel+0x152/0x161
> 

Please post your .config since it apparently differs from x86_64 defconfig 
judging by my debugging symbols and also the full output of the panic.
--
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/