From: Chris Wright <chrisw@osdl.org>
To: Andi Kleen <ak@muc.de>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: node_online_map patch kills x86_64
Date: Tue, 11 Jan 2005 17:53:13 -0800 [thread overview]
Message-ID: <20050111175313.E24171@build.pdx.osdl.net> (raw)
In-Reply-To: <20050112013805.GA74675@muc.de>; from ak@muc.de on Wed, Jan 12, 2005 at 02:38:05AM +0100
* Andi Kleen (ak@muc.de) wrote:
> On Tue, Jan 11, 2005 at 04:30:25PM -0800, Chris Wright wrote:
> > kernel direct mapping tables upto ffff810100000000 @ 8000-d000
> > PANIC: early exception rip ffffffff8078b2e3 error 0 cr2 17c498a67
> > Filesystem type ext2
> > (couple more grub messgages like kernel name, root device)
>
> Can you please boot with earlyprintk=serial,ttyS0,baud and send the full
> boot log?
>
> And also look up where ffffffff8078b2e3 is in System.map.
ffffffff8078b250 T free_area_init_node
Here's the log:
Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 selinux=0 initcall_debug 3 earlyprintk=serial,ttyS0,115200)
Linux version 2.6.10 (chrisw@fuzzy.pdx.osdl.net) (gcc version 3.4.3 20041125 (Red Hat 3.4.3-7)) #217 SMP Tue Jan 11 16:13:52 PST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009dc00 (usable)
BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007ff60000 (usable)
BIOS-e820: 000000007ff60000 - 000000007ff72000 (ACPI data)
BIOS-e820: 000000007ff72000 - 000000007ff80000 (ACPI NVS)
BIOS-e820: 000000007ff80000 - 0000000080000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec00400 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
kernel direct mapping tables upto ffff810100000000 @ 8000-d000
SRAT: PXM 0 -> APIC 0 -> Node 1
SRAT: PXM 1 -> APIC 1 -> Node 2
SRAT: Node 1 PXM 0 0-9ffff
SRAT: Node 1 PXM 0 0-3fffffff
SRAT: Node 2 PXM 1 40000000-7fffffff
Bootmem setup node 1 0000000000000000-000000003fffffff
Bootmem setup node 2 0000000040000000-000000007ff5ffff
No mptable found.
PANIC: early exception rip ffffffff8078b2e3 error 0 cr2 17c497a67
next prev parent reply other threads:[~2005-01-12 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 23:16 Chris Wright
2005-01-11 23:42 ` Andi Kleen
2005-01-12 0:30 ` Chris Wright
2005-01-12 1:38 ` Andi Kleen
2005-01-12 1:53 ` Chris Wright [this message]
2005-01-12 2:00 ` Andi Kleen
2005-01-12 2:10 ` Chris Wright
2005-01-12 0:07 ` William Lee Irwin III
2005-01-12 0:35 ` Chris Wright
2005-01-12 18:42 ` Matthew Dobson
2005-01-12 19:20 ` Chris Wright
2005-01-12 2:03 Petr Vandrovec
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=20050111175313.E24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=ak@muc.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®