From: reinette chatre <reinette.chatre@intel.com>
To: Maciej Rutecki <maciej.rutecki@gmail.com>
Cc: "ilw@linux.intel.com" <ilw@linux.intel.com>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Ilw] Re: WARNING: at net/mac80211/scan.c:267 ieee80211_scan_completed+0x299/0x2b0 [mac80211]()
Date: Fri, 18 Sep 2009 11:44:54 -0700 [thread overview]
Message-ID: <1253299494.26521.664.camel@rc-desk> (raw)
In-Reply-To: <8db1092f0909162332r4ffeef09jdb87f7fc69ff8e9e@mail.gmail.com>
Hi Maciej,
On Wed, 2009-09-16 at 23:32 -0700, Maciej Rutecki wrote:
> [ 249.340094] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
> [ 249.345339] wlan0 direct probe responded
> [ 249.345347] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
> [ 249.347122] wlan0: authenticated
> [ 249.347152] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
> [ 249.349703] wlan0: RX AssocResp from 00:1b:11:f6:0f:28 (capab=0x431
> status=0 aid=1)
> [ 249.349711] wlan0: associated
> [ 253.411858] wlan0: deauthenticated from 00:1b:11:f6:0f:28 (Reason:
> 6)
This still appears to be the main issue here, that AP deauthenticates.
Could you run wpa_supplicant with debugging (-dddt) ? When you have
these logs, could you please open a bug report at
http://bugzilla.intellinuxwireless.org/ to enable us to track it?
Thank you
Reinette
next prev parent reply other threads:[~2009-09-18 18:44 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
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 ` reinette chatre [this message]
2009-09-18 20:19 ` [Ilw] " 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=1253299494.26521.664.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 \
/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