From: Zhu Yi <yi.zhu@intel.com>
To: "Michael S. Tsirkin" <m.s.tsirkin@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
reinette.chatre@intel.com, linux-wireless@vger.kernel.org,
johannes@sipsolutions.net,
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, 02 Sep 2008 09:38:56 +0800 [thread overview]
Message-ID: <1220319536.28282.128.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20080901160658.GA11063@google.com>
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?
What did you do to make it reassociate after resume? If you are using
some automatic config tools, can you try iwconfig manually instead?
Thanks,
-yi
next prev parent reply other threads:[~2008-09-02 1:41 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 [this message]
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
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=1220319536.28282.128.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=m.s.tsirkin@gmail.com \
--cc=reinette.chatre@intel.com \
--cc=rjw@sisk.pl \
--cc=sigsegv@radiotube.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;
as well as URLs for NNTP newsgroup(s).