From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 3.7.6+: WARNING: at net/mac80211/iface.c:705 ieee80211_do_stop
Date: Wed, 20 Feb 2013 09:43:09 -0800 [thread overview]
Message-ID: <51250B2D.3040708@candelatech.com> (raw)
In-Reply-To: <1360327897.29851.21.camel@jlt4.sipsolutions.net>
On 02/08/2013 04:51 AM, Johannes Berg wrote:
> On Wed, 2013-02-06 at 16:44 -0800, Ben Greear wrote:
>> This came from my patched 3.7.6+ kernel...it has some additional printout for the
>> WDS/flush states, in case that helps any...
>>
>> Doesn't seem to have caused any lasting harm.
>
>> [13051.973344] sta6: authenticate with 00:ab:87:60:10:10
>> [13052.099487] sta6: send auth to 00:ab:87:60:10:10 (try 1/3)
>> [13052.139177] sta6: authenticated
>> [13052.176209] sta6: Invalid WDS/flush state, type: 2 WDS: 5 flushed: 1
>> [13052.193241] ------------[ cut here ]------------
>> [13052.206642] WARNING: at /home/greearb/git/linux-3.7.dev.y/net/mac80211/iface.c:705 ieee80211_do_stop+0x647/0x6a0 [mac80211]()
>
> Humm, ok, I see what happens here ... in ieee80211_do_stop() we flush
> stations first, and then later call ieee80211_mgd_stop(). That should
> clearly be the other way around (also the AP bit there), but I'm not
> entirely sure what to do. Probably just move the ieee80211_mgd_stop()
> call up to the start of the function.
Any further thoughts on this? If you have a suggested patch to
test I can test it today..I have a test case that reliably reproduces
this currently...
Thanks,
Ben
>
> johannes
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-02-20 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 0:44 3.7.6+: WARNING: at net/mac80211/iface.c:705 ieee80211_do_stop Ben Greear
2013-02-08 12:51 ` Johannes Berg
2013-02-20 17:43 ` Ben Greear [this message]
2013-02-20 18:17 ` Johannes Berg
2013-02-20 18:42 ` Ben Greear
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=51250B2D.3040708@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).