Re: WARNING: at net/mac80211/scan.c:267 ieee80211_scan_completed+0x299/0x2b0 [mac80211]()

From: Maciej Rutecki
Date: Wed Sep 16 2009 - 13:37:17 EST


2009/9/16 reinette chatre <reinette.chatre@xxxxxxxxx>:
>
> The important information is not what you posted here, but still in the
> dmesg file you provided. In that log we see the following right before
> the warnings:
>
> [ Â163.126590] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
> [ Â163.130027] wlan0 direct probe responded
> [ Â163.130032] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
> [ Â163.131924] wlan0: authenticated
> [ Â163.131952] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
> [ Â163.134325] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28 (capab=0x431 status=0 aid=1)
> [ Â163.134331] wlan0: associated
> [ Â163.155938] wlan0: deauthenticating by local choice (reason=3)
>
> It shows that association was successful, but something in userspace requested a disconnect.

Hmm. Yes, connect takes more time than in 2.6.31.
>
>>
>> [ Â163.208063] ------------[ cut here ]------------
>> [ Â163.208114] WARNING: at net/mac80211/scan.c:267
>> ieee80211_scan_completed+0x299/0x2b0 [mac80211]()
>
> I cannot get an exact line match based on the kernel information you
> provided. I assume it is the first warning in
> ieee80211_scan_completed(). This is not serious as it indicates that
> mac80211 received a "scan completed" indication when it was not
> scanning.
>
>
>> [ Â163.232845] ------------[ cut here ]------------
>> [ Â163.232908] WARNING: at net/wireless/core.c:613
>> wdev_cleanup_work+0xbb/0xe0 [cfg80211]()
>
> This warning has just been reported in linux-wireless also. Perhaps you
> can follow its discussion there. See
> http://thread.gmane.org/gmane.linux.kernel.wireless.general/39607

Thanks for information


--
Maciej Rutecki
http://www.maciek.unixy.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/