From: Jens Axboe <jens.axboe@oracle.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Carlos R. Mafra" <crmafra2@gmail.com>,
Soeren Sonnenburg <kernel@nn7.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, tomas.winkler@intel.com,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: Suspend to RAM regression in 2.6.28-rc2 (bisected)
Date: Mon, 27 Oct 2008 20:13:07 +0100 [thread overview]
Message-ID: <20081027191307.GI22217@kernel.dk> (raw)
In-Reply-To: <1225134571.3796.41.camel@johannes.berg>
On Mon, Oct 27 2008, Johannes Berg wrote:
> On Mon, 2008-10-27 at 20:06 +0100, Jens Axboe wrote:
> > On Mon, Oct 27 2008, Carlos R. Mafra wrote:
> > > On Mon 27.Oct'08 at 19:44:42 +0100, Johannes Berg wrote:
> > > > On Mon, 2008-10-27 at 19:31 +0100, Johannes Berg wrote:
> > > > > On Mon, 2008-10-27 at 19:07 +0100, Soeren Sonnenburg wrote:
> > > > >
> > > > > > > Johannes, can you pls have a look?
> > > > >
> > > > > I did, and I have no idea. Makes no sense at all.
> > > >
> > > > The only thing I can remotely think of is that iwlwifi doesn't like
> > > > being called back from within the call that it did to mac80211, which
> > > > obviously happens here. But I have no idea, the code as it stands is
> > > > correct, just the interaction with iwlwifi's resume seems to be broken.
> > > >
> > > > Try this patch instead:
> > >
> > > Yep, with this patch it also works!
> >
> > Confirmed here as well, my x60 is happy again.
>
> Thanks. Another alternative I could think of is deferring the
> notifications to a work struct, but I'd rather see that in the driver I
> think, not sure though, could be argued either way.
If you want something else tested, just let me know. I don't care a
whole lot about how it gets fixed, as long as it does :-). I use STR
heavily, so it's quite a burden to have it broken.
--
Jens Axboe
next prev parent reply other threads:[~2008-10-27 19:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081027162054.GA4015@localhost.aei.mpg.de>
2008-10-27 17:32 ` Suspend to RAM regression in 2.6.28-rc2 (bisected) Rafael J. Wysocki
2008-10-27 18:07 ` Soeren Sonnenburg
2008-10-27 18:31 ` Johannes Berg
2008-10-27 18:44 ` Johannes Berg
2008-10-27 19:00 ` Carlos R. Mafra
2008-10-27 19:03 ` Johannes Berg
2008-10-27 19:11 ` Carlos R. Mafra
2008-10-27 19:13 ` Johannes Berg
2008-10-27 20:39 ` Carlos R. Mafra
2008-10-27 20:51 ` Rafael J. Wysocki
2008-10-27 20:52 ` Carlos R. Mafra
2008-10-27 21:07 ` Rafael J. Wysocki
2008-10-27 22:05 ` Carlos R. Mafra
2008-10-27 21:07 ` Tomas Winkler
2008-10-27 22:28 ` Carlos R. Mafra
2008-10-27 22:40 ` Tomas Winkler
2008-10-27 22:50 ` Rafael J. Wysocki
2008-10-27 23:12 ` Tomas Winkler
2008-10-27 23:23 ` Harvey Harrison
2008-10-28 15:30 ` Rafael J. Wysocki
2008-10-28 16:12 ` Tomas Winkler
2008-10-28 6:32 ` Christian Borntraeger
2008-10-27 19:06 ` Jens Axboe
2008-10-27 19:09 ` Johannes Berg
2008-10-27 19:13 ` Jens Axboe [this message]
2008-10-27 19:16 ` Johannes Berg
2008-10-27 19:20 ` Jens Axboe
[not found] ` <200810271839.39236.rjw@sisk.pl>
2008-10-27 17:57 ` Carlos R. Mafra
2008-10-27 18:00 ` John W. Linville
2008-10-27 18:16 ` Rafael J. Wysocki
2008-10-27 18:36 ` Carlos R. Mafra
2008-10-27 18:51 ` Carlos R. Mafra
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=20081027191307.GI22217@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=crmafra2@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
--cc=tomas.winkler@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 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).