From: "Michael S. Tsirkin" <m.s.tsirkin@gmail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Zhu Yi <yi.zhu@intel.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
reinette.chatre@intel.com, linux-wireless@vger.kernel.org,
Jan-Espen Pettersen <sigsegv@radiotube.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: new: regression iwl3945/mac80211 endless after suspend associate/deassociate loop
Date: Tue, 2 Sep 2008 17:58:41 +0300 [thread overview]
Message-ID: <20080902145840.GE19172@google.com> (raw)
In-Reply-To: <1220362201.3176.4.camel@borkbork.foobar.com>
On Tue, Sep 02, 2008 at 09:30:01AM -0400, Dan Williams wrote:
> On Tue, 2008-09-02 at 16:04 +0300, Michael S. Tsirkin wrote:
> > On Tue, Sep 02, 2008 at 08:10:09AM +0200, Johannes Berg wrote:
> > > Zhu Yi wrote:
> > > > On Mon, 2008-09-01 at 19:07 +0300, Michael S. Tsirkin wrote:
> > > >> [16482.909453] eth1: associate with AP XX:XX:XX:XX:XX:XX
> > > >> [16482.918553] eth1: RX ReassocResp from XX:XX:XX:XX:XX:XX
> > > >> (capab=0x411 status=0 aid=1)
> > > >> [16482.918564] eth1: associated
> > > >> [16492.920224] eth1: disassociating by local choice (reason=3)
> > > >> [16492.920986] eth1: disassociating by local choice (reason=3)
> > > >
> > > > It is exactly 10 seconds the local STA sends the deauth_leaving frame
> > > > before associated everytime. I wonder if it is the timeout for some
> > > > wireless config tools. NM?
> > >
> > > "by local choice" means wext requested this, not a kernel bug.
> > >
> > > johannes
> >
> > Sure, it's wpa_supplicant in ubuntu gutsy doing it.
> >
> > $wpa_supplicant -version
> > wpa_supplicant v0.5.8
> > Copyright (c) 2003-2007, Jouni Malinen <j@w1.fi> and contributors
> >
> > But it happens to work fine without 8ab65b03b7893da4a49009e7e356e36e27b0c407.
>
> That's really odd; that patch (the don't-send-empty-extended-rates-IE
> patch) shouldn't have anything to do with this behavior, if it did you
> wouldn't get associated to the AP in the first place I think. You're
> 100% sure that this patch is causing the problem?
No, not sure. But reverting it seems to have helped.
And there does not seem to be anything else relevant between rc4 and
rc5.
> Can you post the
> output of running wpa_supplicant with the "-dddt" flags
I put up a (sanitized) -dd output here
http://bugzilla.kernel.org/show_bug.cgi?id=11476
> and also post
> the 'iwlist scan' output for your AP?
>
> Dan
OK, I will look into collecting this data.
next prev parent reply other threads:[~2008-09-02 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 16:07 new: regression iwl3945/mac80211 endless after suspend associate/deassociate loop Michael S. Tsirkin
2008-09-02 1:38 ` Zhu Yi
2008-09-02 6:10 ` Johannes Berg
2008-09-02 13:04 ` Michael S. Tsirkin
2008-09-02 13:30 ` Dan Williams
2008-09-02 14:58 ` Michael S. Tsirkin [this message]
2008-09-02 15:06 ` John W. Linville
2008-09-02 20:53 ` Michael S. Tsirkin
2008-09-02 15:10 ` Dan Williams
2008-09-02 17:24 ` Jouni Malinen
2008-09-02 20:50 ` Michael S. Tsirkin
2008-09-03 12:07 ` Jouni Malinen
2008-09-02 13:18 ` Michael S. Tsirkin
2008-09-02 13:20 ` Michael S. Tsirkin
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=20080902145840.GE19172@google.com \
--to=m.s.tsirkin@gmail.com \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.com \
--cc=rjw@sisk.pl \
--cc=sigsegv@radiotube.org \
--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;
as well as URLs for NNTP newsgroup(s).