The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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: Wed, 12 Jan 2005 00:42:57 +0100	[thread overview]
Message-ID: <m1d5wb4jni.fsf@muc.de> (raw)
In-Reply-To: <20050111151656.A24171@build.pdx.osdl.net> (Chris Wright's message of "Tue, 11 Jan 2005 15:16:56 -0800")

Chris Wright <chrisw@osdl.org> writes:

> Backing out the x86_64 specific bits of the numnodes -> node_online_map
> patch and the generic bits from wli, kills my machine at boot.

And with it it included it works? Why do you back it out then? 
>
> It hits the early_idt_handler and dies straight away.  What would help
> to debug this thing?

First a bit of information, like what kind of machine, logs etc.
(kernel bug reporting 101, it's not that difficult, isn't it?) 

If you have a dual Opteron system and enabled CONFIG_ACPI_NUMA
then numa=noacpi may work. There is a known problem with some
Tyan BIOS. Fix for that is upcomming.

-Andi

  reply	other threads:[~2005-01-11 23:46 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 [this message]
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
  -- 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=m1d5wb4jni.fsf@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