From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 218198] Suspend/Resume Regression with attached ATA devices
Date: Tue, 28 Nov 2023 08:24:01 +0000 [thread overview]
Message-ID: <bug-218198-11613-NAsEdarpyZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218198-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218198
--- Comment #2 from Dieter Mummenschanz (dmummenschanz@web.de) ---
Thanks for the swift reply.
I've applied your patch. Booted up my machine and waited until it transitions
into lower package states (pc8 at the lowest). After that I closed the laptop
LID and let the machine suspend to RAM (S3). After that I reopened the LID and
gave the machine 1-3 minutes time to transition to lower package states which
it now does.
I've attached the dmesg part including your patch when the machine enters
suspend. One thing is odd though:
[ 109.424369] ata5.00: qc timeout after 5000 msecs (cmd 0xe0)
[ 109.424397] ata5.00: STANDBY IMMEDIATE failed (err_mask=0x4)
this shouldn't be there, right?
Regarding automatic transitioning I'm not sure how this works. However even
though I've set CONFIG_SATA_MOBILE_LPM_POLICY=3 in the kernel config, I have to
call an init script explicitly forcing the scsi host to use low power when
idle:
for foo in /sys/class/scsi_host/host*/link_power_management_policy;
do echo med_power_with_dipm > $foo;
done
Otherwise the machine is stuck at PC2 state always.
So we have a fix I guess?
Anyway if there is anything alse I can try or provide you with more debug
output please let me know.
--
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:[~2023-11-28 8:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 7:06 [Bug 218198] New: Suspend/Resume Regression with attached ATA devices bugzilla-daemon
2023-11-28 7:08 ` [Bug 218198] " bugzilla-daemon
2023-11-28 7:47 ` [Bug 218198] New: " Damien Le Moal
2023-11-28 7:47 ` [Bug 218198] " bugzilla-daemon
2023-11-28 8:24 ` bugzilla-daemon [this message]
2023-11-29 10:42 ` Niklas Cassel
2023-11-29 18:47 ` Phillip Susi
2023-11-30 8:48 ` Niklas Cassel
2023-11-28 8:24 ` bugzilla-daemon
2023-11-28 9:54 ` bugzilla-daemon
2023-11-28 9:55 ` bugzilla-daemon
2023-11-29 10:42 ` bugzilla-daemon
2023-11-29 18:10 ` bugzilla-daemon
2023-12-15 15:28 ` Niklas Cassel
2023-11-29 18:10 ` bugzilla-daemon
2023-11-29 18:11 ` bugzilla-daemon
2023-11-29 18:47 ` bugzilla-daemon
2023-11-30 8:49 ` bugzilla-daemon
2023-12-03 19:50 ` Phillip Susi
2023-12-03 19:50 ` bugzilla-daemon
2023-12-04 9:31 ` bugzilla-daemon
2023-12-05 21:37 ` Phillip Susi
2023-12-05 21:37 ` bugzilla-daemon
2023-12-06 6:51 ` bugzilla-daemon
2023-12-07 13:55 ` Phillip Susi
2023-12-07 13:55 ` bugzilla-daemon
2023-12-15 10:51 ` bugzilla-daemon
2023-12-15 15:28 ` bugzilla-daemon
2023-12-18 10:18 ` bugzilla-daemon
2023-12-18 10:29 ` Damien Le Moal
2024-01-11 16:12 ` Niklas Cassel
2023-12-18 10:20 ` [Bug 218198] " bugzilla-daemon
2023-12-18 10:21 ` bugzilla-daemon
2023-12-18 10:21 ` bugzilla-daemon
2023-12-18 10:22 ` bugzilla-daemon
2023-12-18 10:22 ` bugzilla-daemon
2023-12-18 10:29 ` bugzilla-daemon
2023-12-18 10:36 ` bugzilla-daemon
2024-03-05 13:32 ` 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-218198-11613-NAsEdarpyZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-scsi@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.