[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 7 Jul 2008 11:39:17 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [Bug #10872] x86_64 boot hang when CONFIG_NUMA=n
On Mon, 7 Jul 2008 08:32:18 +0200 Ingo Molnar wrote:
>
> * Linus Torvalds <torvalds@...ux-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@...il.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.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
View attachment "netcon-4556.log" of type "text/x-log" (78557 bytes)
View attachment "netcon-4557.log" of type "text/x-log" (11344 bytes)
Powered by blists - more mailing lists