All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Mel Gorman <mel@csn.ul.ie>
Cc: keith mannthey <kmannth@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>, andrew <akpm@osdl.org>
Subject: Re: [Bug] [2.6.18-rc5-mm1] system no boot early death  x86_64
Date: Sat, 9 Sep 2006 15:41:02 +0200	[thread overview]
Message-ID: <200609091541.02337.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0609081134520.7094@skynet.skynet.ie>

On Friday 08 September 2006 12:40, Mel Gorman wrote:
> On Thu, 7 Sep 2006, keith mannthey wrote:
> > On Thu, 2006-09-07 at 11:20 -0700, keith mannthey wrote:
> >> Hello,
> >>   I was booting rc4-mm3.  With rc5-mm1 I am hanging early... Mel I don't
> >> know if this is related to your code but I will soon know. (I don't get
> >> your debug info in early console.)
> >>   I was working on patches for the reserve based memory hot add path in
> >> srat.c (the initial error is fixed by Mels patches but there is more to
> >> do)
>
> That is some good news at least.
>
> > and was just moving to rc5-mm1 to sync up and then more trouble.
> >
> >> This is with reserve based hot-add not enabled at the command line.
> >
> > Well this isn't fully adding up but here is what I found.
> >
> > If I drop
> > x86_64-mm-drop-640k-reservation.patch
> > x86_64-mm-remove-e820-fallback.patch
> > and
> > x86_64-mm-remove-e820-fallback-fix.patch
> >
> > I build and boot.  All files in the series upto x86_64-mm-drop-640k-
> > reservation.patch work just fine.  Dropping this patch makes things
> > better. The e820 patches were removed to make the rest of the series
> > apply.
>
> I am having trouble reproducing this. However, I recently got access to a
> machine similar to yours. I can say that sometimes the stability of
> 2.6.18-rc4-mm3 and 2.6.18-rc5-mm1 was totally useless (but the symptons
> different to yours) and the box would easily crash for reasons I could not
> pin down. As stability problems had been reported on the machine earlier
> by other users, I was inclined to blame the hardware. Now I'm not sure.
>
> > It is not clear what changes would cause me to die setting up the
> > bootmem allocator on my first node...
>
> Unless your machine really has something special in the low 640K that is
> required and bad things happen if it's written to at a bad time.

That would be a BIOS bug then.  If anything is there it has to be reserved.

But maybe it just breaks something that only worked by accident before.

-Andi

      reply	other threads:[~2006-09-09 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 18:20 [Bug] [2.6.18-rc5-mm1] system no boot early death x86_64 keith mannthey
2006-09-08  0:28 ` keith mannthey
2006-09-08 10:40   ` Mel Gorman
2006-09-09 13:41     ` Andi Kleen [this message]

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=200609091541.02337.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=kmannth@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    /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.