[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8e1da0908190647k54cce424m560016ffeec04412@mail.gmail.com>
Date: Wed, 19 Aug 2009 21:47:00 +0800
From: Dave Young <hidave.darkstar@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Ingo Molnar <mingo@...e.hu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: -mm hang while shutdown with printk_delay
On Tue, Aug 18, 2009 at 12:12 PM, Dave Young<hidave.darkstar@...il.com> wrote:
> On Tue, Aug 18, 2009 at 11:30 AM, Andrew
> Morton<akpm@...ux-foundation.org> wrote:
>> On Tue, 18 Aug 2009 11:25:22 +0800 Dave Young <hidave.darkstar@...il.com> wrote:
>>
>>> Hi,
>>>
>>> Test with printk_delay=200,
>>>
>>> /sbin/halt -p
>>>
>>> kernel hang after following message:
>>>
>>> Disabling non-boot CPUs
>>>
>>> There's no such problem with 2.6.31-rc6
>>
>> umm, OK. But -mm contains six patches:
>>
>> printk-boot_delay-rename-printk_delay_msec-to-loops_per_msec.patch
>> printk-boot_delay-rename-printk_delay_msec-to-loops_per_msec-fix.patch
>> printk-boot_delay-rename-printk_delay_msec-to-loops_per_msec-fix-2.patch
>> printk-add-printk_delay-to-make-messages-readable-for-some-scenarios.patch
>> printk-add-printk_delay-to-make-messages-readable-for-some-scenarios-fix.patch
>> printk-add-printk_delay-to-make-messages-readable-for-some-scenarios-cleanup.patch
>>
>> from yourself. Are they the cause?
>>
>
> Actually I tested 2.6.31-rc6 with the above six patches applied,
> there's no such problem.
>
I'm manually bisecting the mm patch series, hope find cause.
> --
> Regards
> dave
>
--
Regards
dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists