From: Johannes Berg <johannes@sipsolutions.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>
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: Tue, 07 Apr 2009 10:18:16 +0200 [thread overview]
Message-ID: <1239092296.22453.1.camel@johannes.local> (raw)
In-Reply-To: <1239062401.4705.23.camel@maxim-laptop> (sfid-20090407_020013_939126_90578556)
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
On Tue, 2009-04-07 at 03:00 +0300, Maxim Levitsky wrote:
> I noticed that always first attempt at scan fails when NM asks for scan.
> I also noticed that this happens with quite recent kernels (I think
> 2,6.28) didn't have this behavior.
I'm pretty sure it did.
> Looking a bit deeper I discovered that each time NM disconnects from a
> networks it sets random ssid/essid to the card (using wireless
> extensions)
This forces a scan
> After that scan fails for some time.
>
> as a NM free example you can run
>
> iwconfig wlan0 essid dummy
> iwlist scan
and then this fails with EBUSY.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-07 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 0:00 Maxim Levitsky
2009-04-07 8:18 ` Johannes Berg [this message]
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
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=1239092296.22453.1.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@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
all inboxes | Powered by JetHome®