From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.linux-foundation.org
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>
Subject: Re: [linux-pm] [Regression][git head f4b87dee9] ath9k doesn't work correctly after resume from suspend to RAM
Date: Sun, 23 May 2010 21:20:16 +0200 [thread overview]
Message-ID: <201005232120.16814.rjw@sisk.pl> (raw)
In-Reply-To: <201005230013.37578.rjw@sisk.pl>
On Sunday 23 May 2010, Rafael J. Wysocki wrote:
> On Saturday 22 May 2010, Rafael J. Wysocki wrote:
> > Hi,
> >
> > With current -git on Acer Ferrari One the ath9k driver doesn't seem to work
> > after resume from suspend to RAM. NetworkManager seems to think that it works,
> > but it doesn't really connect with the AP and doesn't try to obtain an IP
> > address.
>
> Sorry, this was incorrect. It actually tries to obtain an IP address, but
> fails. Apparently, it can't obtain the address without being reloaded.
iwlagn also has problems after resume from suspend to RAM (tested on
Toshiba Portege R500). In this case resume works once, but then the next
attempt to suspend fails (I had to reboot the box every time that happened).
If iwlagn is unloaded, it is possible to suspend and resume the system
arbitrary number of times, but then iwlagn doesn't work when its reloaded
(it doesn't detect wireless networks).
Rafael
next prev parent reply other threads:[~2010-05-23 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 21:53 [Regression][git head f4b87dee9] ath9k doesn't work correctly after resume from suspend to RAM Rafael J. Wysocki
2010-05-22 22:13 ` Rafael J. Wysocki
2010-05-23 19:20 ` Rafael J. Wysocki [this message]
2010-05-23 22:59 ` [linux-pm] " Rafael J. Wysocki
2010-05-24 8:14 ` Johannes Berg
2010-05-23 22:40 ` Rafael J. Wysocki
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=201005232120.16814.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maciej.rutecki@gmail.com \
--cc=mcgrof@gmail.com \
--cc=torvalds@linux-foundation.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