From: "Frédéric Riss" <frederic.riss@gmail.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
len.brown@intel.com, Pavel Machek <pavel@ucw.cz>
Subject: 2.6.18 suspend regression on Intel Macs
Date: Mon, 09 Oct 2006 20:19:41 +0200 [thread overview]
Message-ID: <1160417982.5142.45.camel@funkylaptop> (raw)
Well, I'm not sure it qualifies as a regression, because AFAIK no
official kernels can s2ram/resume Intel Macs correctly out of the box.
There has already been some discussion about the SCI_EN ACPI control bit
not being set when the Mactel boxes come out of suspend to ram.
http://marc.theaimsgroup.com/?l=linux-acpi&m=114957637501557&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=115005083610700&w=2
http://bugme.osdl.org/show_bug.cgi?id=6670
The symptom is:
irq 9: nobody cared (try booting with the "irqpoll" option)
Disabling IRQ #9
when the system comes out of sleep, making ACPI non-functional.
Two days after having released 2.6.17, Linus commited a fix for this
issue in his tree (commit 5603509137940f4cbc577281cee62110d4097b1b):
@@ -812,6 +812,9 @@ static int irqrouter_resume(struct sys_d
ACPI_FUNCTION_TRACE("irqrouter_resume");
+ /* Make sure SCI is enabled again (Apple firmware bug?) */
+ acpi_set_register(ACPI_BITREG_SCI_ENABLE, 1, ACPI_MTX_DO_NOT_LOCK);
+
I since then used lightly patched 2.6.17 kernels on my MacMini without a
problem. With the release of 2.6.18, I decided to switch to a vanilla
kernel but I realized that the above issue reappeared.
I tracked it down to the ACPI merge that took place on July 1st. More
precisely the commit 967440e3be1af06ad4dc7bb18d2e3c16130fe067 (ACPI:
ACPICA 20060623) contains the following hunk:
@@ -635,6 +663,25 @@ acpi_status acpi_hw_register_write(u8 us
case ACPI_REGISTER_PM1_CONTROL: /* 16-bit access */
+ /*
+ * Perform a read first to preserve certain bits (per ACPI spec)
+ *
+ * Note: This includes SCI_EN, we never want to change this bit
+ */
+ status = acpi_hw_register_read(ACPI_MTX_DO_NOT_LOCK,
+ ACPI_REGISTER_PM1_CONTROL,
+ &read_value);
+ if (ACPI_FAILURE(status)) {
+ goto unlock_and_exit;
+ }
+
+ /* Insert the bits to be preserved */
+
+ ACPI_INSERT_BITS(value, ACPI_PM1_CONTROL_PRESERVED_BITS,
+ read_value);
+
+ /* Now we can write the data */
+
status =
acpi_hw_low_level_write(16, value,
&acpi_gbl_FADT->xpm1a_cnt_blk);
which makes Linus' fix a no-op, because it disallows setting the SCI_EN
bit.
Fred.
next reply other threads:[~2006-10-09 18:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 18:19 Frédéric Riss [this message]
2006-10-10 10:39 ` 2.6.18 suspend regression on Intel Macs Pavel Machek
2006-10-10 10:41 ` Arjan van de Ven
2006-10-10 10:49 ` Pavel Machek
2006-10-10 15:33 ` Linus Torvalds
2006-10-10 19:08 ` Frédéric Riss
2006-10-10 19:38 ` Arjan van de Ven
2006-10-10 19:46 ` Frédéric Riss
2006-10-10 19:50 ` Pavel Machek
2006-10-10 21:49 ` Linus Torvalds
2006-10-10 22:09 ` Frédéric Riss
2006-10-10 23:53 ` Linus Torvalds
2006-10-11 6:09 ` Frédéric Riss
2006-10-11 13:16 ` suspend debugging " Pavel Machek
2006-10-11 6:35 ` Len Brown
2006-10-11 14:35 ` Linus Torvalds
2006-10-10 21:28 ` Matthew Garrett
2006-10-11 6:37 ` Len Brown
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=1160417982.5142.45.camel@funkylaptop \
--to=frederic.riss@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@osdl.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