From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: attempt to scan fails (device busy) if essid/ssid was changed recently
Date: Fri, 10 Apr 2009 23:47:01 +0300 [thread overview]
Message-ID: <1239396421.13792.6.camel@maxim-laptop> (raw)
In-Reply-To: <1239395434.13792.3.camel@maxim-laptop>
On Fri, 2009-04-10 at 23:30 +0300, Maxim Levitsky wrote:
> On Tue, 2009-04-07 at 22:37 +0200, Johannes Berg wrote:
> > On Tue, 2009-04-07 at 23:24 +0300, Maxim Levitsky wrote:
> >
> > > First I get this in kernel logs:
> > >
> > >
> > > > [ 29.971903] WARNING:
> > > at /home/maxim/software/kernel/linux-2.6/net/wireless/core.h:79
> > > nl80211_send_wiphy+0x8bd/0xa20 [cfg80211]()
> >
> > Eh, I don't think that is present in a recent wireless tree.
>
> It is.
>
> I have just compiled iwlwifi.git tree, and same message is there:
And I found out why device is always busy, when wpa supplicant tries to
scan. It is the disassociation sequence.
Does kernel notify, when disassociation have finished?
Maybe it is still better not to fail scan request, but block?
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-04-10 20:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 0:00 attempt to scan fails (device busy) if essid/ssid was changed recently Maxim Levitsky
2009-04-07 8:18 ` Johannes Berg
2009-04-07 12:51 ` Maxim Levitsky
2009-04-07 12:56 ` Johannes Berg
2009-04-07 13:04 ` Maxim Levitsky
2009-04-07 13:13 ` Johannes Berg
2009-04-07 13:20 ` Maxim Levitsky
2009-04-07 13:27 ` Johannes Berg
2009-04-07 13:51 ` Maxim Levitsky
2009-04-07 20:24 ` Maxim Levitsky
2009-04-07 20:37 ` Johannes Berg
2009-04-10 20:30 ` Maxim Levitsky
2009-04-10 20:47 ` Maxim Levitsky [this message]
2009-04-11 11:35 ` Johannes Berg
2009-04-11 11:34 ` Johannes Berg
2009-04-11 23:55 ` Maxim Levitsky
2009-04-12 7:06 ` Johannes Berg
2009-04-12 12:49 ` Maxim Levitsky
2009-04-08 14:26 ` Dan Williams
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=1239396421.13792.6.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--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