Re: [Bug 10872] x86_64 boot hang when CONFIG_NUMA=n

Yinghai Lu
2008-06-16T04:15:32Z

On Sun, Jun 15, 2008 at 6:11 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Sun, 15 Jun 2008 12:18:42 -0700 Yinghai Lu wrote:
>
>> On Sun, Jun 15, 2008 at 9:35 AM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> > On Sat, 14 Jun 2008 22:12:04 +0200 (CEST) Rafael J. Wysocki wrote:
>> >
>> >> This message has been generated automatically as a part of a report
>> >> of recent regressions.
>> >>
>> >> The following bug entry is on the current list of known regressions
>> >> from 2.6.25. Please verify if it still should be listed.
>> >>
>> >>
>> >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=10872
>> >> Subject : x86_64 boot hang when CONFIG_NUMA=n
>> >> Submitter : Randy Dunlap <randy.dunlap@oracle.com>
>> >> Date : 2008-06-05 21:50 (10 days old)
>> >> References : http://marc.info/?l=linux-kernel&m=121270308607116&w=4
>> >> http://lkml.org/lkml/2008/6/11/355
>> >> Handled-By : Yinghai Lu <yhlu.kernel@gmail.com>
>> >
>> > Yes, still happens for me on 2.6.26-rc6-git2.
>> >
>>
>> please send out whole boot log with numa on and numa off
>> and boot with debug
>>
>> please apply attached debug patch too.
>
> OK, did all of that.
> I should probably note that in both cases, the kernel is loaded/booted by using kexec.
> Both boot logs are captured generated via netconsole.
>
> The failing boot log is netcon-4409.log. The working boot log (CONFIG_NUMA=y) is
> netcon-4410.log. Enabling CONFIG_NUMA makes the following changes:

how about the numa=off on the kernel with CONFIG_NUMA=y?

YH