From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: David Spinadel <dvdspndl@gmail.com>,
linux-wireless@vger.kernel.org, hostap@lists.shmoo.com
Subject: Re: rcutree tree warning during P2P device support testing
Date: Wed, 20 Mar 2013 16:08:59 +0100 [thread overview]
Message-ID: <1363792139.8224.10.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5149CD81.40301@broadcom.com>
> I am testing the P2P device support patches. Upon stopping the
> wpa_supplicant I get the following warning and when I unload brcmfmac it
> hangs resulting in hung_task_timeout message. The whole rcu stuff still
> needs to settle in my brain. I suspect the warning is related to
> brcmfmac unload failure, but maybe you have some ideas where I should look.
Hmm, why would stopping the supplicant cause brcmfmac to unload?? Or are
you saying you first stop the supplicant, which gets you that warning,
and then unload fails?
> [ 1634.039095] WARNING: at kernel/rcutree.c:1960
> rcu_process_callbacks+0x469/0x560()
> [ 1634.133917] Call Trace:
> [ 1634.139833] [<c1039c92>] warn_slowpath_common+0x72/0xa0
> [ 1634.148659] [<c10c61f9>] ? rcu_process_callbacks+0x469/0x560
> [ 1634.157914] [<c10c61f9>] ? rcu_process_callbacks+0x469/0x560
> [ 1634.167121] [<c1039ce2>] warn_slowpath_null+0x22/0x30
> [ 1634.175725] [<c10c61f9>] rcu_process_callbacks+0x469/0x560
Can't say I understand this warning ...
> [ 3606.381631] INFO: task khubd:30 blocked for more than 120 seconds.
> [ 3606.388366] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [ 3606.396931] khubd D f4f01cd8 0 30 2 0x00000000
> [ 3606.403609] f4f01d10 00000092 00000000 f4f01cd8 00000246 c1748000
> c183fb40 c183fb40
> [ 3606.411731] d46b6273 0000031c f53e7b40 f4d323c0 c1748000 00000246
> 00000000 f0820090
> [ 3606.419807] 00000246 f4f01cd8 00000046 00000001 00000046 00000000
> 00000002 f0820090
> [ 3606.427881] Call Trace:
> [ 3606.430518] [<c1097aeb>] ? trace_hardirqs_on+0xb/0x10
> [ 3606.435907] [<c1525ff3>] schedule+0x23/0x60
> [ 3606.440402] [<f8230c65>] wiphy_unregister+0xa5/0x2e0 [cfg80211]
This seems to be because you don't remove the p2p device if it's still
present when you unload the driver. Call cfg80211_unregister_wdev() at
some appropriate place.
johannes
next prev parent reply other threads:[~2013-03-20 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 14:53 rcutree tree warning during P2P device support testing Arend van Spriel
2013-03-20 15:08 ` Johannes Berg [this message]
2013-03-20 21:17 ` Arend van Spriel
2013-03-20 21:29 ` Johannes Berg
2013-03-20 21:46 ` Arend van Spriel
2013-03-20 21:55 ` Johannes Berg
2013-03-21 12:04 ` Arend van Spriel
2013-03-21 12:21 ` 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=1363792139.8224.10.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=dvdspndl@gmail.com \
--cc=hostap@lists.shmoo.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).