From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Lockup with ath5k, rtnl_mutex related?
Date: Tue, 05 Oct 2010 10:29:46 +0200 [thread overview]
Message-ID: <1286267386.3641.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4CAA6468.3030706@candelatech.com>
On Mon, 2010-10-04 at 16:34 -0700, Ben Greear wrote:
> I'm (also) trying to debug an issue with an ath5k system that deadlocks.
>
> We have sysrq output for the held locks, process backtraces, etc.
>
> One thing that has me confused is that the locks-held output shows
> a large number of processes owning the rtnl_mutex. Any idea
> how to tell what process *really* owns it?
Can't really -- the mutex code acquires the lockdep dep_map before it
even manages to lock, so that it can detect recursive locking.
johannes
next prev parent reply other threads:[~2010-10-05 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 23:34 Lockup with ath5k, rtnl_mutex related? Ben Greear
2010-10-05 8:29 ` Johannes Berg [this message]
2010-10-05 8:41 ` [PATCH] mac80211: fix deadlock with multiple interfaces Johannes Berg
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=1286267386.3641.8.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).