linux-kernel - Re: WARNING: at net/mac80211/scan.c:267 ieee80211_scan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1253124149.26521.438.camel@rc-desk>
Date:	Wed, 16 Sep 2009 11:02:29 -0700
From:	reinette chatre <reinette.chatre@...el.com>
To:	Maciej Rutecki <maciej.rutecki@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Wireless List <linux-wireless@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"Zhu, Yi" <yi.zhu@...el.com>
Subject: Re: WARNING: at net/mac80211/scan.c:267
 ieee80211_scan_completed+0x299/0x2b0 	[mac80211]()

Hi Maciej,

On Wed, 2009-09-16 at 10:36 -0700, Maciej Rutecki wrote:
> 2009/9/16 reinette chatre <reinette.chatre@...el.com>:
> >
> > 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.

You mentioned that you tried to connect to two networks. From the logs I
can understand that the connection to the first network took a long
time. This is also not due to the warnings you encountered (the warnings
only showed up after you disconnected from second network). The reason
why the connection to the first network took so long was some protocol
exchange problems with AP. Here is the relevant information from your
log:

[  117.741190] wlan0: deauthenticating by local choice (reason=3)
[  117.741308] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  117.745515] wlan0 direct probe responded
[  117.745523] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  117.747256] wlan0: authenticated
[  117.747288] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  117.749529] wlan0: RX AssocResp from 00:1b:11:f6:0f:28 (capab=0x431 status=0 aid=1)
[  117.749536] wlan0: associated
[  121.404153] wlan0: deauthenticated from 00:1b:11:f6:0f:28 (Reason: 6)
[  124.123203] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  124.126121] wlan0 direct probe responded
[  124.126129] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  124.127876] wlan0: authenticated
[  124.127906] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  124.130164] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28 (capab=0x431 status=0 aid=1)
[  124.130172] wlan0: associated
[  128.263997] wlan0: disassociated (Reason: 3)
[  128.280067] wlan0: deauthenticating by local choice (reason=3)
[  130.968263] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  130.970685] wlan0 direct probe responded
[  130.970692] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  130.972497] wlan0: authenticated
[  130.972529] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  130.974780] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28 (capab=0x431 status=0 aid=1)
[  130.974787] wlan0: associated
[  134.511593] wlan0: deauthenticated from 00:1b:11:f6:0f:28 (Reason: 6)
[  137.216183] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  137.218606] wlan0 direct probe responded
[  137.218614] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  137.220520] wlan0: authenticated
[  137.220555] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  137.222808] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28 (capab=0x431 status=0 aid=1)
[  137.222815] wlan0: associated
[  140.758586] wlan0: deauthenticated from 00:1b:11:f6:0f:28 (Reason: 6)
[  143.513364] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  143.524448] wlan0 direct probe responded
[  143.524456] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  143.526207] wlan0: authenticated
[  143.526238] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  143.540625] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28 (capab=0x431 status=0 aid=1)
[  143.540632] wlan0: associated
[  162.901260] b44: eth0: powering down PHY
[  162.919757] wlan0: deauthenticating by local choice (reason=3)

As you can see the AP keeps deauthenticating you with Reason 6. This
means "Incorrect frame type or subtype received from unauthenticated
station". Can you try to connect using wpa_supplicant? When you do make
sure there is no other network managing applications (like network
manager, wicd, or even other instances of wpa_supplicant etc) running.

The connection to the second network went very fast - completed in one
second. But a disconnection was requested locally just as fast. Do you
perhaps have more than one network managing application running?

Reinette


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