From: TJ <linux@tjworld.net>
To: linux-acpi@vger.kernel.org
Subject: Re: Any known issues of premature suspend?
Date: Mon, 23 Jul 2007 14:36:39 +0100 [thread overview]
Message-ID: <1185197799.9798.4.camel@bagoas> (raw)
In-Reply-To: <1185153966.1346.29.camel@bagoas>
On Mon, 2007-07-23 at 02:26 +0100, TJ wrote:
> I'm currently debugging a weird issue where the PC appears to be
> attempting to S3 suspend prematurely in acpi_enter_sleep_state().
I added further debug messages to acpi_enter_sleep_state() and found
that the issue occurs when ACPI_FLUSH_CPU_CACHE() is called.
The log shows:
kernel: [ 251.532000] hwsleep-0285 [03] enter_sleep_state :
Entering sleep state [S3]
kernel: [ 251.532000] hwsleep-0308 [03] enter_sleep_state :
Writing PM1A (SLP_TYP data) 1401
kernel: [ 251.532000] hwsleep-0319 [03] enter_sleep_state :
Writing PM1B (SLP_TYP data) 1401
kernel: [ 251.532000] hwsleep-0326 [03] enter_sleep_state : Just
written PM1B (SLP_TYP data). status=0x0
kernel: [ 251.532000] hwsleep-0343 [03] enter_sleep_state : About
to flush CPU cache
kernel: [ 251.532000] Back to C!
The standard kernel build uses CONFIG_PARAVIRT so it appears that
paravirt_ops.wbinvd() is used to handle the flush.
I'm building a kernel without PARAVIRT now to see if it is the issue,
but I'm still in the dark as to why this would happen.
TJ.
---drivers/acpi/hardware/hwsleep.c::acpi_enter_sleep_state()----
/* Write #2: SLP_TYP + SLP_EN */
#ifdef DEBUG_RESUME
ACPI_DEBUG_PRINT((ACPI_DB_INIT, "About to flush CPU cache\n"));
#endif
ACPI_FLUSH_CPU_CACHE();
#ifdef DEBUG_RESUME
ACPI_DEBUG_PRINT((ACPI_DB_INIT, "Writing PM1A (SLP_TYP + SLP_EN) %x\n",
PM1Acontrol));
#endif
prev parent reply other threads:[~2007-07-23 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1761554AbXGVXPI/20070722231508Z+217@vger.kernel.org>
2007-07-23 1:26 ` Any known issues of premature suspend? TJ
2007-07-23 13:36 ` TJ [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=1185197799.9798.4.camel@bagoas \
--to=linux@tjworld.net \
--cc=linux-acpi@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