From: Andi Kleen <ak@suse.de>
To: Janne M O Heikkinen <jmoheikk@cc.helsinki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64: 2.6.14 with NUMA panics at boot
Date: Sat, 29 Oct 2005 12:01:05 +0200 [thread overview]
Message-ID: <200510291201.06613.ak@suse.de> (raw)
In-Reply-To: <Pine.OSF.4.61.0510290058420.417368@rock.it.helsinki.fi>
On Saturday 29 October 2005 00:06, Janne M O Heikkinen wrote:
> On Sat, 28 Oct 2005, Andi Kleen wrote:
> > Janne M O Heikkinen <jmoheikk@cc.helsinki.fi> writes:
> >> With CONFIG_K8_NUMA I get the following right after boot:
> >> PANIC: early exception rip ffffffff8023429f error 0 cr2 0
> >> PANIC: early exception rip ffffffff8011893a error 0 cr2 ffffffffff5fd023
> >
> > Did earlier kernels work? Please post full log with earlyprintk=vga
> > or earlyprintk=serial,ttySx,baud
>
> 2.6.13.4 works just fine, this is what I got with earlyprintk=vga:
>
> Loading K-2.6.14
> Bootdata ok (command line is auto BOOT_IMAGE=K-2.6.14 ro root=901
> resume=/dev/md0 selinux=0 splash=verbose console=tty0 earlyprintk=vga)
> Linux version 2.6.14-smp (jamse@linux) (gcc version 4.0.2) #3 SMP
> PREEMPT Fri Oct 28 20:49:34 EEST 2005one.
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable)
> BIOS-e820: 00000000bfff0000 - 00000000bffff000 (ACPI data)
> BIOS-e820: 00000000bffff000 - 00000000c0000000 (ACPI NVS)
> BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
> BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
> SRAT: PXM 0 -> APIC 0 -> CPU 0 -> Node 0
> SRAT: PXM 1 -> APIC 1 -> CPU 1 -> Node 1
> SRAT: Node 0 PXM 0 100000-7fffffff
> SRAT: Node 1 PXM 1 80000000-bfffffff
> SRAT: Node 1 PXM 1 80000000-13fffffff
> SRAT: Node 0 PXM 0 0-7fffffff
> Bootmem setup node 0 0000000000000000-000000007fffffff
> PANIC: early exception rip ffffffff8023429f error 0 cr2 0
> PANIC: early exception rip ffffffff8011893a error 0 cr2 ffffffffff5fd02
And it boots with numa=noacpi ?
-Andi
next prev parent reply other threads:[~2005-10-29 10:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 19:26 x86_64: 2.6.14 with NUMA panics at boot Janne M O Heikkinen
2005-10-28 21:06 ` Andi Kleen
2005-10-28 22:06 ` Janne M O Heikkinen
2005-10-28 22:21 ` Janne M O Heikkinen
2005-10-29 10:01 ` Andi Kleen [this message]
2005-10-29 11:08 ` Janne M O Heikkinen
2005-10-29 14:54 ` Janne M O Heikkinen
2005-10-29 16:41 ` Andi Kleen
2005-10-29 17:30 ` Dave Hansen
2005-10-31 0:17 ` Bob Picco
2005-10-31 2:12 ` Andi Kleen
2005-10-31 1:40 ` Bob Picco
2005-10-31 3:28 ` Andi Kleen
2005-10-31 2:46 ` Bob Picco
2005-11-02 5:07 ` Martin J. Bligh
2005-11-02 18:08 ` Andy Whitcroft
2005-11-03 14:43 ` Bob Picco
2005-11-03 17:06 ` Andy Whitcroft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510291201.06613.ak@suse.de \
--to=ak@suse.de \
--cc=jmoheikk@cc.helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.