From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 219346] [BISECTED] Disable ACPI PM Timer breaks suspend on all Amber Lake machines
Date: Thu, 03 Oct 2024 12:50:24 +0000 [thread overview]
Message-ID: <bug-219346-215701-gMtT1FEF5g@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219346-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219346
--- Comment #4 from Todd Brandt (todd.e.brandt@intel.com) ---
ok I just tested with your patch, it fixed S3, but S2idle and S4 are still
broken and still hang the system. The only difference is when S2idle or S4 hang
the system will display this on the screen:
[ OK ] Started Show Plymouth Boot Screen
[ OK ] Started Forward Password R#s to Plymouth Directory
Watch.plymouth-start.service
[ OK ] Reached target Local Encrypted Volumes.
systemd-journal-flush.service
[ OK ] Finished Flush Journal to Persistent Storange
[ OK ] Created slice Slice /system/systemd-backlight
Starting Load/Save Screen #f backlight:intel_backlight...
[ OK ] Finished Load/Save Screen # of backlight:intel_backlight.
systemd-backlight@backlight:intel_backlight.service
And it hangs, doesn't respond to any keypresses, it just sits there. So in
short the only two changes are:
1) fixes S3
2) leave S2idle and S4 broken but displays a weird status on the screen on hang
So this is clearly affecting more than just S3, that timer has some purpose in
Amber Lake that breaks when the timer is shut down.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-10-03 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 10:17 [Bug 219346] New: [BISECTED] Disable ACPI PM Timer breaks suspend on all Amber Lake machines bugzilla-daemon
2024-10-03 10:47 ` [Bug 219346] " bugzilla-daemon
2024-10-03 11:02 ` bugzilla-daemon
2024-10-03 11:46 ` bugzilla-daemon
2024-10-03 12:50 ` bugzilla-daemon [this message]
2024-10-03 13:11 ` bugzilla-daemon
2024-10-03 20:29 ` bugzilla-daemon
2024-10-03 22:47 ` bugzilla-daemon
2024-10-03 23:59 ` bugzilla-daemon
2024-10-06 11:09 ` bugzilla-daemon
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=bug-219346-215701-gMtT1FEF5g@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.