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

[Yinghai Lu]

On Sun, Jun 15, 2008 at 6:11 PM, Randy Dunlap <randy.dunlap@xxxxxxxxxx> 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@xxxxxxxxxx> 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@xxxxxxxxxx>
>> >> 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@xxxxxxxxx>
>> >
>> > 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:
>
> 4c4
> < # Sun Jun 15 15:00:56 2008
> ---
>> # Sun Jun 15 15:10:15 2008
> 241c241,246
> < # CONFIG_NUMA is not set
> ---
>> CONFIG_NUMA=y
>> CONFIG_K8_NUMA=y
>> CONFIG_X86_64_ACPI_NUMA=y
>> CONFIG_NODES_SPAN_OTHER_NODES=y
>> # CONFIG_NUMA_EMU is not set
>> CONFIG_NODES_SHIFT=6
> 249a255
>> CONFIG_NEED_MULTIPLE_NODES=y
> 260a267
>> CONFIG_MIGRATION=y
> 282a290
>> CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
> 309a318
>> CONFIG_ACPI_NUMA=y
>

the print out looks all right.

any chance to use normal serial console to capture the boot log?

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/