From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: mjg59@srcf.ucam.org, linux-kernel@vger.kernel.org
Subject: System automatically wakes up because of Intel Rapid Start Technology
Date: Mon, 22 Dec 2014 14:59:38 +0100 [thread overview]
Message-ID: <9927036.n7iZq92iLW@xps13> (raw)
Hi,
I'd like to ask those of you who own a system that supports Intel Rapid
Start Technology (IRST) to perform a simple test to determine whether my
laptop (XPS13 9333) is the only system affected by a bug related to IRST
that I recently found or not.
In the past months I noticed random transitions from S3 to S0 with no
apparent reason.
After some recent tests I found a way to trigger those automatic state
transitions. It seems that the timer in charge of the resume of the
system for the transition to S4 is not re-initialized on resume/suspend.
Exactly "wakeup_time" minutes after the transition from S0 to S3, the
system will automatically transition from S3 to S0 instead of S4 if
within that interval it transitioned to S0 at least once.
Everything works as expected if the system is never resumed or if the
system is suspended after "wakeup_time" minutes have passed since the
first suspension to ram.
In addition to that, changing the values of wakeup_time and
wakeup_events seems to have no effect until the timer has expired.
According to the Implementation Guide [1] there are no special
requirements other than the standard S3 ACPI support. Still, IRST works
as intended only on Windows. This makes me wonder whether the problem is
due to some vendor specific change or not.
To quickly replicate the problem, follow the following steps: set the
timer to 1 minute and suspend the system. Immediately after that, resume
and suspend the system again. If it automatically wakes up after 1
minute has passed since the first suspension, then the system is
affected by the bug. If this is the case, I'd suggest to default
wakeup_events to 0 or 2 to prevent issues and add some sort of warning
somewhere to let users know about this problem.
Regards,
Gabriele
[1] http://downloadmirror.intel.com/22647/eng/Intel%20Rapid%20Start%20Technology%20Deployment%20Guide%20v1.0.pdf
next reply other threads:[~2014-12-22 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 13:59 Gabriele Mazzotta [this message]
2014-12-22 14:44 ` System automatically wakes up because of Intel Rapid Start Technology Matthew Garrett
2014-12-22 14:48 ` Matthew Garrett
2014-12-22 14:59 ` Matthew Garrett
2014-12-22 15:50 ` Gabriele Mazzotta
2014-12-22 16:10 ` Gabriele Mazzotta
2014-12-22 16:13 ` Matthew Garrett
2014-12-22 18:02 ` Matthew Garrett
2014-12-22 18:41 ` Gabriele Mazzotta
2014-12-22 18:57 ` Gabriele Mazzotta
2014-12-22 16:12 ` Matthew Garrett
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=9927036.n7iZq92iLW@xps13 \
--to=gabriele.mzt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@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