mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: 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>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [2.6.33-rc5] Weird deadlock when shutting down
Date: Sat, 20 Feb 2010 17:30:55 +0800	[thread overview]
Message-ID: <2375c9f91002200130v1af400a3qe6045b484a25299@mail.gmail.com> (raw)
In-Reply-To: <1266485775.6539.6.camel@jlt3.sipsolutions.net>

On Thu, Feb 18, 2010 at 5:36 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Fri, 2010-01-29 at 15:41 +1100, Benjamin Herrenschmidt wrote:
>> Hi Ingo !
>>
>> Johannes and I see this on our quad G5s... it -could- be similar to
>> one reported a short while ago by Xiaotian Feng <xtfeng@gmail.com>
>> under the subject [2.6.33-rc4] sysfs lockdep warnings on cpu hotplug.
>>
>> Basically, the machine deadlocks right after printing the following
>> when doing a shutdown:
>>
>> halt/4071 is trying to acquire lock:
>>  (s_active){++++.+}, at: [<c0000000001ef868>]
>> .sysfs_addrm_finish+0x58/0xc0
>>
>> but task is already holding lock:
>>  (&per_cpu(cpu_policy_rwsem, cpu)){+.+.+.}, at: [<c0000000004cd6ac>]
>> .lock_policy_rwsem_write+0x84/0xf4
>>
>> which lock already depends on the new lock.
>>
>> the existing dependency chain (in reverse order) is:
>
> This is still happening with -rc8. Any news?
>

Hey, johannes

Not sure if you made some mistake here, the one you report here [1]
is _not_ the same with this one reported by Benjamin.

Please make sure what you are talking about here is the same one.

Thanks.

1. http://lkml.org/lkml/2010/2/18/33

  parent reply	other threads:[~2010-02-20  9:31 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
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 [this message]
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=2375c9f91002200130v1af400a3qe6045b484a25299@mail.gmail.com \
    --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

Powered by JetHome