lkml.org 
[lkml]   [2008]   [Jul]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Bug #10872] x86_64 boot hang when CONFIG_NUMA=n
On Mon, 7 Jul 2008 11:39:17 -0700 Randy Dunlap wrote:

> On Mon, 7 Jul 2008 08:32:18 +0200 Ingo Molnar wrote:
>
> >
> > * Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> > > > This still happens with 2.6.26-rc9. Using CONFIG_NUMA=y boots OK.
> > >
> > > Ok, then it wasn't the nr_zones thing.
> > >
> > > Since it seems to be repeatable for you, can you bisect it?
> >
> > one guess would be:
> >
> > | commit e8ee6f0ae5cd860e8e6c02807edfa3c1fa01bcb5
> > | Author: Yinghai Lu <yhlu.kernel@gmail.com>
> > | Date: Sun Apr 13 01:41:58 2008 -0700
> > |
> > | x86: work around io allocation overlap of HT links
> >
> > but ... since CONFIG_NUMA makes it work, i'm not sure about that.
> >
> > Randy, could you post the full CONFIG_NUMA bootlog as well, does it show
> > any difference in resource allocations?
>
> Good and bad boot logs are attached. There are several differences, but I don't
> see any that are significant.
>
> I've started bisecting with:
>
> $ git bisect start
> $ git bisect bad v2.6.26-rc1
> $ git bisect good v2.6.25
>
> That's only about 1.29M lines of changes.

git bisect and normal rebooting did not find a problem.

I'll repeat this using kexec to boot the new kernel and see if that
locates any issues... since I normally use kexec to load/test new kernels
and that was how the failure occurred (occurs).

---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/


\
 
 \ /
  Last update: 2008-07-08 00:45    [W:0.164 / U:0.180 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site