All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Robin Holt <holt@sgi.com>, Russ Anderson <rja@sgi.com>,
	Yinghai Lu <yinghai@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	tglx@linutronix.de, "H. Peter Anvin" <h.peter.anvin@intel.com>,
	Jack Steiner <steiner@sgi.com>
Subject: Re: [BUG] x86: bootmem broken on SGI UV
Date: Sun, 10 Oct 2010 06:56:05 -0500	[thread overview]
Message-ID: <20101010115605.GC14064@sgi.com> (raw)
In-Reply-To: <20101010114459.GY14068@sgi.com>

On Sun, Oct 10, 2010 at 06:44:59AM -0500, Robin Holt wrote:
> On Sun, Oct 10, 2010 at 12:43:19PM +0200, Ingo Molnar wrote:
> > 
> > * Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > 
> > > * Robin Holt <holt@sgi.com> wrote:
> > > 
> > > > On Sat, Oct 09, 2010 at 07:59:45AM -0500, Russ Anderson wrote:
> > > > > Yes, Yinghai's patch fixes the problem.
> > > > > Thank you very much.
> > > > 
> > > > Will this be included in 2.6.36?  It is needed for boot in order for UV
> > > > systems to boot.
> > > 
> > > -tip uses memblock APIs. If this happens with vanilla -git as well 
> > > then we need a bootmem backport for the fix.
> > 
> > And to answer your question: yes, we can queue it up for -final as well 
> > if it's a recent regression - 'doesnt boot at all' bugs are nasty. But 
> > i'm not sure this is a bootmem problem so please double check vanilla 
> > v2.6.36-rc7 as well.
> 
> The 36-rc7 kernel does not boot at all either.  I don't have any decent
> debug tools to dig in further.  It does fail on the same machine that
> Russ was testing with, but passes on any that have a single blade as
> the kernel Russ first identified as being a problem had.  Based upon my
> vague recollection of the boot messages, it appears to fail in a similar
> point in boot.  I would assume it is a similar problem.

2.6.35 fails as well.  I will bisect for as long as time permits.

Robin

  reply	other threads:[~2010-10-10 11:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 21:34 [BUG] x86: bootmem broken on SGI UV Russ Anderson
2010-10-08 21:43 ` H. Peter Anvin
2010-10-08 22:15 ` Yinghai Lu
2010-10-08 22:57 ` Yinghai Lu
2010-10-09 12:59   ` Russ Anderson
2010-10-09 16:39     ` Robin Holt
2010-10-09 18:06       ` Yinghai Lu
2010-10-09 18:17         ` [PATCH -v2] x86, numa: Fix cross nodes memory configuration Yinghai Lu
2010-10-09 18:39         ` [BUG] x86: bootmem broken on SGI UV Linus Torvalds
2010-10-10 10:41       ` Ingo Molnar
2010-10-10 10:43         ` Ingo Molnar
2010-10-10 11:44           ` Robin Holt
2010-10-10 11:56             ` Robin Holt [this message]
2010-10-10 14:05               ` Ingo Molnar
2010-10-10 22:51                 ` Robin Holt
2010-10-11  2:52                   ` [PATCH -v3] x86, numa: Fix cross nodes memory configuration Yinghai Lu
2010-10-11 22:01                     ` [tip:x86/urgent] x86, numa: For each node, register the memory blocks actually used tip-bot for Yinghai Lu
2010-10-11 22:05                       ` David Rientjes
2010-10-11 22:21                         ` H. Peter Anvin
2010-10-11 22:28                     ` tip-bot for Yinghai Lu
  -- strict thread matches above, loose matches on Subject: below --
2010-10-10  1:04 [BUG] x86: bootmem broken on SGI UV Anvin, H Peter

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=20101010115605.GC14064@sgi.com \
    --to=holt@sgi.com \
    --cc=h.peter.anvin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rja@sgi.com \
    --cc=steiner@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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.