linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 218198] Suspend/Resume Regression with attached ATA devices
Date: Thu, 07 Dec 2023 13:55:45 +0000	[thread overview]
Message-ID: <bug-218198-11613-pWKj6cstOG@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 #16 from Phillip Susi (phill@thesusis.net) ---
bugzilla-daemon@kernel.org writes:

> No or at least I don't see this behaviour. However the drives occasional seem
> to have some trouble waking up after resume and hdparm -Y:

That's strange.  Once the drive is woken back up that should once again,
prevent pc8, just like it did before being put to SLEEP.

> [59984.831894] ata5.00: exception Emask 0x0 SAct 0x2000000 SErr 0x10000
> action
> 0x6
> [59984.831907] ata5.00: waking up from sleep
> [59984.831914] ata5: hard resetting link
> [59985.145261] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
> [59985.148840] ata5.00: supports DRM functions and may not be fully
> accessible
> [59985.153322] ata5.00: supports DRM functions and may not be fully
> accessible
> [59985.156822] ata5.00: configured for UDMA/133
> [59985.166903] ahci 0000:00:17.0: port does not support device sleep
> [59985.167045] ata5: EH complete
> [59985.167268] ata5.00: Enabling discard_zeroes_data

That's normal.  The way to wake the drive up from SLEEP is to issue a
link hard reset.  That's just the kernel showing that it's doing that.
At least the first part is normal, I'm not sure about the bit about DRM
functions.  The bit about the port not supporting device sleep seems to
be your main issue with it not getting to pc8 using ALPM.

> Regarding your patches: Anything I can test for you? :)

Keep an eye on the libata list.  Hopefully I'll clean them up and post
them in the next few days.  Initially it will just be to keep hdparm -Y
from being woken up for silly reasons.  Sorting out the bigger problems
with runtime pm so that the kernel can automatically put things to sleep
when idle is going to be a bigger issue than I first thought.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-12-07 13:55 UTC|newest]

Thread overview: 38+ 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
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 [this message]
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
2023-12-18 10:20 ` 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-pWKj6cstOG@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).