linux-kernel - Re: [boot crash] Re: [PATCHSET x86/numa] x86-64, NUMA: bring sanity to NUMA config/emulation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110217161037.GA14168@elte.hu>
Date:	Thu, 17 Feb 2011 17:10:37 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Tejun Heo <tj@...nel.org>
Cc:	linux-kernel@...r.kernel.org, x86@...nel.org, yinghai@...nel.org,
	brgerst@...il.com, gorcunov@...il.com, shaohui.zheng@...el.com,
	rientjes@...gle.com, hpa@...ux.intel.com, ankita@...ibm.com
Subject: Re: [boot crash] Re: [PATCHSET x86/numa] x86-64, NUMA: bring sanity
 to NUMA config/emulation


* Tejun Heo <tj@...nel.org> wrote:

> On Thu, Feb 17, 2011 at 01:35:11PM +0100, Ingo Molnar wrote:
> > 
> > FYI, -tip testing has found the follow boot crash:
> > 
> > [    0.000000] init_memory_mapping: 0000000000000000-000000003fff0000
> > [    0.000000]  0000000000 - 003fff0000 page 4k
> > [    0.000000] kernel direct mapping tables up to 3fff0000 @ 3fdee000-3fff0000
> > PANIC: early exception 06 rip 10:ffffffff8102f069 error 0 cr2 f06f53
> > [    0.000000] Pid: 0, comm: swapper Not tainted 2.6.38-rc5-tip+ #94135
> > [    0.000000] Call Trace:
> > [    0.000000]  [<ffffffff8199019e>] ? early_idt_handler+0x5e/0x71
> > [    0.000000]  [<ffffffff8102f069>] ? __phys_addr+0x69/0x70
> > [    0.000000]  [<ffffffff8102f009>] ? __phys_addr+0x9/0x70
> > [    0.000000]  [<ffffffff819a0156>] ? initmem_init+0xf0/0xa0d
> > [    0.000000]  [<ffffffff819a4cc2>] ? parse_crashkernel+0x40/0x2a1
> > [    0.000000]  [<ffffffff810303e0>] ? dummy_numa_init+0x0/0x70
> > [    0.000000]  [<ffffffff810284a9>] ? is_vsmp_box+0x9/0x50
> > [    0.000000]  [<ffffffff81992f4a>] ? setup_arch+0x9f9/0xaec
> > [    0.000000]  [<ffffffff813c585c>] ? printk+0x41/0x45
> > [    0.000000]  [<ffffffff81990999>] ? start_kernel+0x9d/0x3b5
> > [    0.000000]  [<ffffffff8199032b>] ? x86_64_start_reservations+0x132/0x136
> > [    0.000000]  [<ffffffff8199047d>] ? x86_64_start_kernel+0x14e/0x15d
> > 
> > Full crashlog attached below, config attached as well.
> > 
> > Testbox is a standard dual-core Athlon64 whitebox PC, with no particular 
> > weirdnesses. The box boots fine with x86/mm removed from tip:master.
> > 
> > I've excluded x86/mm from tip:master for the time being. This was with the 
> > e23bba604433 x86/mm tree.
> 
> Does the following patch from Yinghai fix the problem?
> 
>  http://thread.gmane.org/gmane.linux.kernel/1101528/focus=1101598

Yeah - i pulled your latest bits and the crash is gone.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/