From: Andi Kleen <ak@muc.de>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: node_online_map patch kills x86_64
Date: 12 Jan 2005 02:38:05 +0100
Date: Wed, 12 Jan 2005 02:38:05 +0100 [thread overview]
Message-ID: <20050112013805.GA74675@muc.de> (raw)
In-Reply-To: <20050111163025.T469@build.pdx.osdl.net>
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.
-Andi
next prev parent reply other threads:[~2005-01-12 1:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 23:16 node_online_map patch kills x86_64 Chris Wright
2005-01-11 23:42 ` Andi Kleen
2005-01-12 0:30 ` Chris Wright
2005-01-12 1:38 ` Andi Kleen [this message]
2005-01-12 1:53 ` Chris Wright
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
-- strict thread matches above, loose matches on Subject: below --
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=20050112013805.GA74675@muc.de \
--to=ak@muc.de \
--cc=chrisw@osdl.org \
--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