From: Matt Mackall <mpm@selenic.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: 2.6.21-mm2: ACPI exception on resume
Date: Wed, 23 May 2007 16:15:17 -0500 [thread overview]
Message-ID: <20070523211517.GK11115@waste.org> (raw)
In-Reply-To: <200705232256.28366.rjw@sisk.pl>
On Wed, May 23, 2007 at 10:56:27PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, 23 May 2007 19:48, Matt Mackall wrote:
> > On Wed, May 23, 2007 at 02:13:30PM -0300, Henrique de Moraes Holschuh wrote:
> > > On Wed, 23 May 2007, Rafael J. Wysocki wrote:
> > > > While I agree with that, it would really be helpful if you tested the latest -rc
> > > > kernel and saw if the bug was present in there.
> > > >
> > > > If the bug is not present in the latest -rc, it'll be possible to identify the
> > > > patch that causes it to appear in -mm and find the reason of the breakage.
> > >
> > > And, once we know the reason, we will be able to find out how to best fix the
> > > problem.
> > >
> > > So, do please test latest -rc, or bissect to the last known-good kernel. As
> > > I said, we need further data points to do anything.
> >
> > This isn't conclusive as this bug is fairly hard to trigger, but it
> > looks like the culprit may have been this patch and not anything in
> > -mm or mainline. So the below patch doesn't help the problem it was
> > intended for (lid switch no longer wakes up S2R after a S2D cycle) and
> > appears to be implicated in making my EC unhappy.
>
> Yes, this was just a debug patch.
>
> We broke quite a few systems by placing platform_finish() before
> device_resume() and I suspected your system could be one of them.
>
> Apparently, that's not the case.
>
> In 2.6.22-rc2 we also moved platform_prepare() to after device_suspend()
> and that's why I asked you to test this kernel.
Will get to it eventually.
--
Mathematics is the supreme nostalgia of our time.
prev parent reply other threads:[~2007-05-23 21:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 16:57 2.6.21-mm2: ACPI exception on resume Matt Mackall
2007-05-19 18:24 ` Rafael J. Wysocki
2007-05-19 22:40 ` Matt Mackall
2007-05-19 23:05 ` Rafael J. Wysocki
2007-05-19 20:45 ` Henrique de Moraes Holschuh
2007-05-19 22:38 ` Matt Mackall
2007-05-20 3:52 ` Henrique de Moraes Holschuh
2007-05-21 22:23 ` Matt Mackall
2007-05-21 23:03 ` Henrique de Moraes Holschuh
2007-05-22 22:45 ` Matt Mackall
2007-05-23 0:19 ` Henrique de Moraes Holschuh
2007-05-23 1:48 ` Matt Mackall
2007-05-23 4:19 ` Henrique de Moraes Holschuh
2007-05-23 4:41 ` Ray Lee
2007-05-23 12:51 ` Henrique de Moraes Holschuh
2007-05-23 22:50 ` Ray Lee
2007-05-24 0:28 ` Henrique de Moraes Holschuh
2007-05-24 1:37 ` Ray Lee
2007-05-27 21:02 ` Pavel Machek
2007-05-23 8:57 ` Rafael J. Wysocki
2007-05-23 17:13 ` Henrique de Moraes Holschuh
2007-05-23 17:48 ` Matt Mackall
2007-05-23 20:56 ` Rafael J. Wysocki
2007-05-23 21:15 ` Matt Mackall [this message]
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=20070523211517.GK11115@waste.org \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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