From: "Frédéric RISS" <frederic.riss@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: robert.moore@intel.com, "len.brown" <len.brown@intel.com>
Subject: 2.6.21-rc suspend regression
Date: Wed, 21 Mar 2007 23:54:04 +0100 [thread overview]
Message-ID: <1174517644.5633.31.camel@funkylaptop> (raw)
My MacMini (Intel Core Duo, EFI mode) doesn't come out of suspend to ram
with current git. This was working great with 2.6.20. A long bisection
phase[1] brought me to that old commit:
Commit c5a7156959e89b32260ad6072bbf5077bcdfbeee
Author: Bob Moore <robert.moore@intel.com> 2007-02-02 17:48:19
Committer: Len Brown <len.brown@intel.com> 2007-02-03 03:14:22
ACPICA: Disable all wake GPEs after first one recieved
Change for GPE support: when a wake GPE is
received, now all wake GPEs are immediately disabled to
prevent the waking GPE from firing again, and to prevent
other wake GPEs from interrupting the wake process.
Signed-off-by: Alexey Starikovskiy <alexey.y.starikovskiy@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
This commit prevents the box to come out of sleep. Unfortunately, simply
reverting from current master produces a conflict. If I resolve the
conflict by hand the kernel won't come out of sleep either :-(
Looking at Adrian's regression lists, it seems a lot of other things
could produce the failures to resume... but that's a starting point. Do
the ACPI guys have an idea how this patch breaks my system?
I'll happily provide more info if needed.
Fred.
[1]: The ACPICA merge is based on 2.6.20-rc7 and not 2.6.20, thus I had
to bisect it by cherry-picking 40c373cc3af9720d1cec0e32c3da26b1d220a95b
(which is necessary to suspend the Mini in EFI mode) at each iteration.
This added to the fact that the ACPI merge bisection broke the build at
one point made the whole process a bit more painful that it need be.
next reply other threads:[~2007-03-21 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 22:54 Frédéric RISS [this message]
2007-03-21 23:01 ` Tino Keitel
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=1174517644.5633.31.camel@funkylaptop \
--to=frederic.riss@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@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
all inboxes | Powered by JetHome®