From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI suspend: Blacklist boxes that require us to set SCI_EN directly on resume
Date: Mon, 17 Nov 2008 23:45:59 -0600 [thread overview]
Message-ID: <49225697.90804@shaw.ca> (raw)
In-Reply-To: <200811172333.13466.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
> Subject: ACPI suspend: Blacklist boxes that require us to set SCI_EN directly on resume
>
> Some Apple boxes evidently require us to set SCI_EN on resume
> directly, because if we don't do that, they hung somewhere in the
> resume code path. Moreover, on these boxes it is not sufficient to
> use acpi_enable() to turn ACPI on during resume. All of this is
> against the ACPI specification which states that (1) the BIOS is
> supposed to return from the S3 sleep state with ACPI enabled
> (SCI_EN set) and (2) the SCI_EN bit is owned by the hardware and we
> are not supposed to change it.
>
> For this reason, blacklist the affected systems so that the SCI_EN
> bit is set during resume on them.
>
> [NOTE: Unconditional setting SCI_EN for all system on resume doesn't
> work, because it makes some other systems crash (that's to be
> expected). Also, it is not entirely clear right now if all of the
> Apple boxes require this workaround.]
This is rather gross. The usual question arises, why does Windows work
without such a hack? Maybe there is no better solution for now, but
somebody should really look into why the behavior is different in Linux..
next prev parent reply other threads:[~2008-11-18 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 22:33 [PATCH] ACPI suspend: Blacklist boxes that require us to set SCI_EN directly on resume Rafael J. Wysocki
2008-11-18 5:45 ` Robert Hancock [this message]
2008-11-20 13:17 ` Pavel Machek
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=49225697.90804@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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