Linux wireless drivers development
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Maciej Rutecki <maciej.rutecki@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Wireless List <linux-wireless@vger.kernel.org>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>,
	"Zhu, Yi" <yi.zhu@intel.com>
Subject: Re: WARNING: at net/mac80211/scan.c:267 ieee80211_scan_completed+0x299/0x2b0 	[mac80211]()
Date: Wed, 16 Sep 2009 11:02:29 -0700	[thread overview]
Message-ID: <1253124149.26521.438.camel@rc-desk> (raw)
In-Reply-To: <8db1092f0909161036t5bae781eqa6f0a0df308ec4cd@mail.gmail.com>

Hi Maciej,

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



  reply	other threads:[~2009-09-16 18:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  9:36 WARNING: at net/mac80211/scan.c:267 ieee80211_scan_completed+0x299/0x2b0 [mac80211]() Maciej Rutecki
2009-09-16 17:27 ` reinette chatre
2009-09-16 17:36   ` Maciej Rutecki
2009-09-16 18:02     ` reinette chatre [this message]
2009-09-16 19:59       ` Maciej Rutecki
2009-09-16 22:13         ` reinette chatre
2009-09-17  6:32           ` Maciej Rutecki
2009-09-18 18:44             ` [Ilw] " reinette chatre
2009-09-18 20:19               ` Maciej Rutecki

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=1253124149.26521.438.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=yi.zhu@intel.com \
    /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