From: "Michael S. Tsirkin" <m.s.tsirkin@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
yi.zhu@intel.com, 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: new: regression iwl3945/mac80211 endless after suspend associate/deassociate loop
Date: Mon, 1 Sep 2008 19:07:01 +0300 [thread overview]
Message-ID: <20080901160658.GA11063@google.com> (raw)
Starting with 2.6.27-rc5, my T60p sometimes fails to associate
with an access point after suspend to ram/resume.
This does not seem to ever happen on 2.6.27-rc4.
When this happens, I observe the following messages in dmesg:
(AP mac masked out with XX):
[16433.458084] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[16433.502490] PM: Adding info for No Bus:iwl-phy4:radio
[16433.502666] Registered led device: iwl-phy4:radio
[16433.502764] PM: Adding info for No Bus:iwl-phy4:assoc
[16433.502822] Registered led device: iwl-phy4:assoc
[16433.502870] PM: Adding info for No Bus:iwl-phy4:RX
[16433.503006] Registered led device: iwl-phy4:RX
[16433.503055] PM: Adding info for No Bus:iwl-phy4:TX
[16433.503111] Registered led device: iwl-phy4:TX
[16433.505268] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16433.522344] ADDRCONF(NETDEV_UP): eth1: link is not ready
[16433.704125] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16433.705986] eth1: authenticated
[16433.705997] eth1: associate with AP XX:XX:XX:XX:XX:XX
[16433.708406] eth1: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x411 status=0 aid=1)
[16433.708412] eth1: associated
[16433.709659] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[16443.712280] eth1: disassociating by local choice (reason=3)
[16443.712902] eth1: disassociating by local choice (reason=3)
[16444.692059] eth1: no IPv6 routers present
[16445.997384] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16445.999304] eth1: authenticated
[16445.999312] eth1: associate with AP XX:XX:XX:XX:XX:XX
[16446.001784] eth1: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x411 status=0 aid=1)
[16446.001790] eth1: associated
[16446.008222] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16446.009539] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16446.012433] eth1: authenticated
[16446.012440] eth1: associate with AP XX:XX:XX:XX:XX:XX
[16446.015149] eth1: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x411 status=0 aid=1)
[16446.015155] eth1: associated
[16456.017223] eth1: disassociating by local choice (reason=3)
[16456.019751] eth1: disassociating by local choice (reason=3)
[16458.298346] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16458.300319] eth1: authenticated
[16458.300339] eth1: associate with AP XX:XX:XX:XX:XX:XX
[16458.305557] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16458.314765] eth1: authenticated
[16458.314781] eth1: associate with AP XX:XX:XX:XX:XX:XX
[16458.318666] eth1: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x411 status=0 aid=1)
[16458.318673] eth1: associated
[16468.321210] eth1: disassociating by local choice (reason=3)
[16470.604081] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16470.606122] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16470.608330] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16470.608367] eth1: authenticated
[16470.608374] eth1: associate with AP XX:XX:XX:XX:XX:XX
[16470.614629] eth1: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x411 status=0 aid=1)
[16470.614648] eth1: associated
[16480.617268] eth1: disassociating by local choice (reason=3)
[16480.619939] eth1: disassociating by local choice (reason=3)
[16482.896840] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16482.899593] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16482.899626] eth1: authenticated
[16482.899633] eth1: associate with AP XX:XX:XX:XX:XX:XX
[16482.906006] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16482.906048] eth1: authenticated
[16482.906055] eth1: associate with AP XX:XX:XX:XX:XX:XX
[16482.907625] eth1: authenticate with AP XX:XX:XX:XX:XX:XX
[16482.909446] eth1: authenticated
[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)
Reverting 8ab65b03b7893da4a49009e7e356e36e27b0c407 seems to make
the card associate properly after suspend, for me.
--
MST
next reply other threads:[~2008-09-01 16:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 16:07 Michael S. Tsirkin [this message]
2008-09-02 1:38 ` new: regression iwl3945/mac80211 endless after suspend associate/deassociate loop Zhu Yi
2008-09-02 6:10 ` Johannes Berg
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=20080901160658.GA11063@google.com \
--to=m.s.tsirkin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.