[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1239396421.13792.6.camel@maxim-laptop>
Date: Fri, 10 Apr 2009 23:47:01 +0300
From: Maxim Levitsky <maximlevitsky@...il.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: linux-wireless <linux-wireless@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: attempt to scan fails (device busy) if essid/ssid was changed
recently
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
--
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/
Powered by blists - more mailing lists