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 20:14:56 +0100 [thread overview]
Message-ID: <1364411696.8388.21.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <87txnwacdw.fsf@sycorax.lbl.gov>
On Wed, 2013-03-27 at 12:08 -0700, Alex Romosan wrote:
> > 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.
Ah, right, I guess I'm a little surprised it ever works at all ... We'll
see in the log though.
johannes
next prev parent reply other threads:[~2013-03-27 19:15 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 [this message]
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=1364411696.8388.21.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 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.