From: Johannes Berg <johannes@sipsolutions.net>
To: Bob Copeland <bcopeland@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Sujith Manoharan <Sujith.Manoharan@atheros.com>,
Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH v2] mac80211: resume properly, add suspend/resume test
Date: Fri, 13 Mar 2009 22:19:53 +0100 [thread overview]
Message-ID: <1236979193.5235.52.camel@johannes.local> (raw)
In-Reply-To: <b6c5339f0903131151m2dc43fbo52ace9d9070096c@mail.gmail.com> (sfid-20090313_195123_661173_7AA0BF95)
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On Fri, 2009-03-13 at 14:51 -0400, Bob Copeland wrote:
> > [ 289.753866]
> > [ 289.753869] =================================
> > [ 289.754164] [ INFO: inconsistent lock state ]
> > [ 289.754372] 2.6.29-rc7-wl-17155-g2f7ab92-dirty #29
> > [ 289.754598] ---------------------------------
> > [ 289.754805] inconsistent {in-softirq-W} -> {softirq-on-W} usage.
>
> [softirq-on-W stack looks like:
>
> sta_notify
> ath_node_detach
> ath_tx_node_cleanup
> spin_lock()
>
> vs the ath9k_tx_tasklet]
>
> > Looks like we need to disable BHs for the sta functions or something?
> Yup... or pm can take sta_lock with spin_lock_irqsave() like the other
> callers of sta_notify.
Yes, we probably should do that in mac80211 for consistency, I'll cook
up a patch tomorrow or so.
> Feel free to add my Acked-by on both the PM patches. I'd been using
> CONFIG_PM_DEBUG to simulate suspend/resume but since you have to
> do 'devices' anyway to get the desired effect, the debug file here
> is nicer.
PM_DEBUG works too, this just seemed a little more self-contained.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-13 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 10:25 [PATCH] mac80211: resume properly, add suspend/resume test Johannes Berg
2009-03-13 10:44 ` [PATCH v2] " Johannes Berg
2009-03-13 10:48 ` Johannes Berg
2009-03-13 10:50 ` Johannes Berg
2009-03-13 12:10 ` Helmut Schaa
2009-03-13 12:15 ` Johannes Berg
2009-03-13 10:58 ` Johannes Berg
2009-03-13 18:51 ` Bob Copeland
2009-03-13 21:19 ` Johannes Berg [this message]
2009-03-20 16:03 ` Jouni Malinen
2009-03-21 7:59 ` Johannes Berg
2009-03-23 19:43 ` John W. Linville
2009-03-23 19:50 ` 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=1236979193.5235.52.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Sujith.Manoharan@atheros.com \
--cc=bcopeland@gmail.com \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@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