mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Chris Wright <chrisw@osdl.org>,
	colpatch@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: node_online_map patch kills x86_64
Date: Tue, 11 Jan 2005 16:35:04 -0800	[thread overview]
Message-ID: <20050111163504.D24171@build.pdx.osdl.net> (raw)
In-Reply-To: <20050112000726.GD14443@holomorphy.com>; from wli@holomorphy.com on Tue, Jan 11, 2005 at 04:07:26PM -0800

* William Lee Irwin III (wli@holomorphy.com) wrote:
> On Tue, Jan 11, 2005 at 03:16:56PM -0800, Chris Wright wrote:
> > 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.
> > It hits the early_idt_handler and dies straight away.  What would help
> > to debug this thing?
> 
> The only part of this I'm responsible for is converting build_zonelists()
> to pass its nodemask argument by reference to address a livelock. I feel
> your pain and if not otherwise occupied I would help fix your problem
> right away.

Thanks wli.  Seems Andi understands the issue despite my unintelligible
bug report ;-)

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2005-01-12  0:43 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
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 [this message]
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=20050111163504.D24171@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=colpatch@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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®