All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org, chrisw@osdl.org
Subject: Re: node_online_map patch kills x86_64
Date: Wed, 12 Jan 2005 03:03:31 +0100	[thread overview]
Message-ID: <624682967EF@vcnet.vc.cvut.cz> (raw)

On 12 Jan 05 at 2:38, Andi Kleen 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.

You should go through your x86-64-bugs mailbox ;-)   I've sent two
"hacks" your way, with explanation.  It is not nice to have node_online_map
to initialize with '1', then your nodes are #1 and #2 instead of #0 and
#1, and as node #0 has no memory and is not online at all, things broke.
Plus k8topology is broken too.

http://www.x86-64.org/lists/bugs/msg01278.html

                                                Petr Vandrovec
                                                


             reply	other threads:[~2005-01-12  2:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12  2:03 Petr Vandrovec [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=624682967EF@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=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 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.