From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [2.6.33-rc5] Weird deadlock when shutting down
Date: Sat, 20 Feb 2010 21:44:47 +0800 [thread overview]
Message-ID: <20100220134447.GA3000@hack> (raw)
In-Reply-To: <1266665331.12525.0.camel@jlt3.sipsolutions.net>
On Sat, Feb 20, 2010 at 12:28:51PM +0100, Johannes Berg wrote:
>On Sat, 2010-02-20 at 17:06 +0800, Américo Wang wrote:
>> On Sat, Feb 20, 2010 at 4:56 PM, Johannes Berg
>> <johannes@sipsolutions.net> wrote:
>> > On Sat, 2010-02-20 at 15:13 +0800, Américo Wang wrote:
>> >
>> >> Does my following untested patch help?
>> >
>> > Sorry, no. I'll hook up a screen to the box after I return from the
>> > fresh market.
>> >
>>
>> Are you sure there is no difference? :-/
>
>It deadlocks after
>
>Disabling non-boot CPUs ...
>
>Not sure if that counts as a difference...
>
I am not sure neither...
That message is displayed before shutting down the devices.
To verify, you can add some printk() in the end of
__cpufreq_remove_dev(), or enable CONFIG_CPU_FREQ_DEBUG.
Thanks!
next prev parent reply other threads:[~2010-02-20 13:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 4:41 [2.6.33-rc5] Weird deadlock when shutting down Benjamin Herrenschmidt
2010-02-18 9:36 ` Johannes Berg
2010-02-18 16:31 ` Linus Torvalds
2010-02-18 18:45 ` Johannes Berg
2010-02-20 7:13 ` Américo Wang
2010-02-20 8:56 ` Johannes Berg
2010-02-20 9:06 ` Américo Wang
2010-02-20 10:53 ` Johannes Berg
2010-02-20 11:28 ` Johannes Berg
2010-02-20 12:07 ` Johannes Berg
2010-02-20 13:44 ` Américo Wang [this message]
2010-02-20 13:57 ` Johannes Berg
2010-02-21 9:51 ` Américo Wang
2010-02-21 10:17 ` Johannes Berg
2010-02-22 8:19 ` Américo Wang
2010-02-22 8:39 ` Johannes Berg
2010-02-21 10:43 ` Johannes Berg
2010-02-21 10:55 ` Xiaotian Feng
2010-02-21 11:12 ` Xiaotian Feng
2010-02-21 11:14 ` Johannes Berg
2010-02-21 11:22 ` Johannes Berg
2010-02-22 8:34 ` Américo Wang
2010-02-22 9:04 ` Johannes Berg
2010-02-22 9:12 ` Américo Wang
2010-02-22 9:14 ` Johannes Berg
2010-02-22 9:21 ` Américo Wang
2010-02-22 8:22 ` Américo Wang
2010-02-20 7:42 ` Dave Young
2010-02-20 8:46 ` Johannes Berg
2010-02-20 4:46 ` Américo Wang
2010-02-20 8:45 ` Johannes Berg
2010-02-20 9:30 ` Américo Wang
2010-02-20 10:52 ` Johannes Berg
2010-03-25 11:28 ` David Howells
2010-03-26 2:43 ` Américo Wang
2010-03-26 12:22 ` David Howells
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=20100220134447.GA3000@hack \
--to=xiyou.wangcong@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/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