From: Johannes Berg <johannes@sipsolutions.net>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Xiaotian Feng <xtfeng@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: Mon, 22 Feb 2010 10:14:11 +0100 [thread overview]
Message-ID: <1266830051.5609.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <2375c9f91002220112q351044a4ycf4ee7dc2630c16d@mail.gmail.com>
On Mon, 2010-02-22 at 17:12 +0800, Américo Wang wrote:
> Since it hangs in put_cpu() which is just preempt_enable(), so I began
> to suspect if we need a synchronize_sched(), or some barrier perhaps.
> I am not sure at all.
Right.
> Before other experts look at this, I think doing a bisect would be
> very useful.
I was afraid you'd say that, it'll take forever though since I need to
walk over to it after every shutdown, see if it turned off and then turn
it on again (and possibly off).... I guess I'll get started on that.
johannes
next prev parent reply other threads:[~2010-02-22 9:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 4:41 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
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 [this message]
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=1266830051.5609.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
--cc=xtfeng@gmail.com \
/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
Powered by JetHome