From: Dave Young <hidave.darkstar@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: -mm hang while shutdown with printk_delay
Date: Wed, 19 Aug 2009 21:47:00 +0800 [thread overview]
Message-ID: <a8e1da0908190647k54cce424m560016ffeec04412@mail.gmail.com> (raw)
In-Reply-To: <a8e1da0908172112kca79a1en7042fc1738ad1336@mail.gmail.com>
On Tue, Aug 18, 2009 at 12:12 PM, Dave Young<hidave.darkstar@gmail.com> wrote:
> On Tue, Aug 18, 2009 at 11:30 AM, Andrew
> Morton<akpm@linux-foundation.org> wrote:
>> On Tue, 18 Aug 2009 11:25:22 +0800 Dave Young <hidave.darkstar@gmail.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
next prev parent reply other threads:[~2009-08-19 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 3:25 Dave Young
2009-08-18 3:30 ` Andrew Morton
2009-08-18 4:12 ` Dave Young
2009-08-19 13:47 ` Dave Young [this message]
2009-08-20 3:33 ` Dave Young
2009-08-24 2:59 ` Dave Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8e1da0908190647k54cce424m560016ffeec04412@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®