From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Johannes Berg <johannes@sipsolutions.net>
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 12:08:59 -0700 [thread overview]
Message-ID: <87txnwacdw.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <1364410962.8388.19.camel@jlt4.sipsolutions.net> (message from Johannes Berg on Wed, 27 Mar 2013 20:02:42 +0100)
Johannes Berg <johannes@sipsolutions.net> writes:
> On Wed, 2013-03-27 at 11:02 -0700, Alex Romosan wrote:
>
>> > Humm, yes, that makes more sense. That commit fixed a bug in another
>> > commit though, I'm surprised you ended up there?! Curious ... I'll
>> > check over the commit and see if I can find anything wrong with it.
>>
>> i just reverted that commit on top of 3.9-rc4 and now i can reconnect
>> when resuming from suspend. so whatever bug that commit fixed, it also
>> introduced a new one.
>
> Hmm, actually ... I suspect this didn't introduce a bug but rather
> unmasked one in iwlwifi/mac80211 interaction.
>
> Are you sure this only happens after suspend/resume? It seems like it
> would always happen? At least if there was a beacon in the scan results
> already, which should probably always be the case...
no, it always happens, but i only noticed it after suspend/resume. when
i suspend i do an ifdown (because i haven't figured out a way to
convince my new access point not to drop idle connections) and then i do
an ifup to reconnect on resume. when i'm testing it now, i just take the
network down and then try to bring it back up.
> Can you enable iwlwifi debugging and set the iwlwifi module parameter
> debug=0x40000000 ? I have a feeling you'll see something like
> "PASSIVE_NO_RX" in there.
i'll do it and let you know. i have iwlwifi compiled in the kernel, how
do i specify it at boot time?
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
next prev parent reply other threads:[~2013-03-27 19:09 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 [this message]
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
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=87txnwacdw.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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).