From: Johannes Berg <johannes@sipsolutions.net>
To: Alex Romosan <romosan@sycorax.lbl.gov>
Cc: linux-wireless@vger.kernel.org, ilw@linux.intel.com
Subject: Re: iwlwifi unable to reconnect after suspend since v3.9-rc1
Date: Wed, 27 Mar 2013 21:13:16 +0100 [thread overview]
Message-ID: <1364415196.8388.26.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <87k3oszk2g.fsf@sycorax.lbl.gov>
On Wed, 2013-03-27 at 13:03 -0700, Alex Romosan wrote:
> > Could you try this patch?
> >
> > http://p.sipsolutions.net/617a8667db243e11.txt
>
> with this patch applied i can take the network down and bring it back
> again. this is the log:
> [ 84.440148] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
> [ 84.442819] iwlwifi 0000:03:00.0: I iwl_trans_pcie_reclaim [Q 0] 0 -> 1 (1)
> [ 84.442844] iwlwifi 0000:03:00.0: I iwlagn_rx_reply_tx TXQ 0 status PASSIVE_NO_RX (0x00000090) rate_n_flags 0x800d retries 0
> [ 84.442855] iwlwifi 0000:03:00.0: I iwlagn_rx_reply_tx FrameCnt = 1, idx=0
> [ 84.442884] iwlwifi 0000:03:00.0: I iwlagn_rx_reply_tx TXQ 0 status PASSIVE_NO_RX (0x00000090)
> [ 84.442896] iwlwifi 0000:03:00.0: I iwlagn_rx_reply_tx initial_rate 0x800d retries 0, idx=0 ssn=1 seq_ctl=0x90
> [ 84.532849] iwlwifi 0000:03:00.0: I iwl_trans_pcie_reclaim [Q 0] 1 -> 2 (2)
> [ 84.532867] iwlwifi 0000:03:00.0: I iwlagn_rx_reply_tx TXQ 0 status SUCCESS (0x00000201)
> [ 84.532875] iwlwifi 0000:03:00.0: I iwlagn_rx_reply_tx initial_rate 0x400d retries 0, idx=1 ssn=2 seq_ctl=0x0
Ah so it's even the same packet because we set
IEEE80211_TX_STAT_TX_FILTERED.
Note the delay here -- roughly between 84.4428 and 84.5328 we wait for a
beacon.
I'll apply the patch and add your tested-by, like this:
http://p.sipsolutions.net/7e871bfb5a0b272a.txt
OK?
johannes
next prev parent reply other threads:[~2013-03-27 20:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 20:52 iwlwifi unable to reconnect after suspend since v3.9-rc1 Alex Romosan
2013-03-27 13:14 ` Johannes Berg
2013-03-27 17:35 ` Alex Romosan
2013-03-27 17:41 ` Johannes Berg
2013-03-27 18:02 ` Alex Romosan
2013-03-27 19:02 ` Johannes Berg
2013-03-27 19:08 ` Alex Romosan
2013-03-27 19:11 ` Johannes Berg
2013-03-27 19:14 ` Johannes Berg
2013-03-27 19:33 ` Alex Romosan
2013-03-27 19:44 ` Johannes Berg
2013-03-27 20:03 ` Alex Romosan
2013-03-27 20:13 ` Johannes Berg [this message]
2013-03-27 20:29 ` Alex Romosan
2013-03-27 17:42 ` Johannes Berg
2013-03-27 17:48 ` Alex Romosan
2013-03-27 17:54 ` Johannes Berg
2013-03-27 18:58 ` Alex Romosan
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=1364415196.8388.26.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=romosan@sycorax.lbl.gov \
/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).