Messages in this thread |  | | | Date | Sun, 6 Jul 2008 23:57:05 -0700 | | From | "Yinghai Lu" <> | | Subject | Re: [Bug #10872] x86_64 boot hang when CONFIG_NUMA=n | |
On Sun, Jul 6, 2008 at 11:32 PM, Ingo Molnar <mingo@elte.hu> 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?
>
l looked resource allocations in that bootlog.
all my AMD test servers work well with Randy's config (!NUMA)
( Linus tree or tip tree)
YH
|  |