From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Julian Wollrath <jwollrath@web.de>, linux-wireless@vger.kernel.org
Subject: Re: WARNING: at net/wireless/mlme.c:517
Date: Fri, 04 Jan 2013 14:30:59 +0100 [thread overview]
Message-ID: <1357306259.11302.20.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50E325B5.205@lwfinger.net> (sfid-20130101_190652_609944_FB0A8B6D)
On Tue, 2013-01-01 at 12:06 -0600, Larry Finger wrote:
> > [ 436.155998] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
> > [ 436.158343] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411
> > status=0 aid=4) [ 436.158478] wlan0: associated [ 436.158538] IPv6:
> > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 446.153705]
> > ------------[ cut here ]------------ [ 446.153765] WARNING: at
> > net/wireless/mlme.c:517 cfg80211_mlme_disassoc+0x17d/0x190 [cfg80211]()
>
> This one indicates that there was a call to disassociate when the device was not
> associated. It might have been informative to have seen the logged messages
> earlier than 436.155474 seconds.
>
> Johannes: Why is this a WARN_ON condition? Certainly, the returned -ENOTCON does
> the right thing, even though some part of the system got confused.
That's why it's a warning, it points to an internal state confusion --
current_bss should always be assigned if sme_state is SME_CONNECTED. Or
so I thought, evidently that's not the case. I don't see how this
happens in the code though.
johannes
prev parent reply other threads:[~2013-01-04 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 14:45 WARNING: at net/wireless/mlme.c:517 Julian Wollrath
2013-01-01 18:06 ` Larry Finger
2013-01-01 22:15 ` Julian Wollrath
2013-01-01 22:28 ` Larry Finger
2013-01-02 11:00 ` Julian Wollrath
2013-01-02 17:00 ` Larry Finger
2013-01-03 9:31 ` Julian Wollrath
2013-01-07 15:06 ` Julian Wollrath
2013-01-04 13:30 ` Johannes Berg [this message]
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=1357306259.11302.20.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=jwollrath@web.de \
--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).