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 215880] Resume process hangs for 5-6 seconds starting sometime in 5.16
Date: Thu, 20 Jul 2023 21:52:14 +0000	[thread overview]
Message-ID: <bug-215880-11613-L7fnF2ByyJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215880-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215880

--- Comment #57 from Paul Ausbeck (paula@alumni.cse.ucsc.edu) ---
The m.2/SATA to 7pin SATA adapter that I mentioned previously as on order,
arrived. Using this adapter I connected a spare Barracuda 4TB drive to one of
the m.2 slots on my Chuwi Gemibook Pro laptop. With this setup, the lack of
mouse pointer interactivity on resume exhibits exactly the same as on my Intel
dh77kc desktop.

The mouse pointer is not interactive until after "PM: suspend exit" is written
to the kernel log. Additionally, an active GUI terminal is not interactive
until the same time. This is noticeable by typing "sudo pm-suspend" in a
terminal. The resulting CR/LF and next command prompt do not appear following
resume until the same time that the mouse cursor comes alive. The Barracuda
drive connected to the Gemibook isn't as slow to spin up as the relatively old
WD 2TB in my desktop so the delay to interactivity is only about 5 seconds
instead of 10+.

The interactivity delay is present on both machines when using kernel 6.1x and
not present on both machines when using kernel 5.10x. When using kernel 5.10x,
the dmesg log on both machines shows "PM suspend exit" happens before the
slower ATA drives are "configured for UDMA/133". When using kernel 6.1x, the
dmesg log shows "PM suspend exit" occurring after the slower ATA dries are
"configured for UDMA/133".

At this point, I am convinced that this is a regression related to changes in
libata. I will take this offline now to see what I can do to help recover the
previous resume interactivity behavior.

-- 
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-07-20 21:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-215880-11613@https.bugzilla.kernel.org/>
2022-06-27  4:09 ` [Bug 215880] Resume process hangs for 5-6 seconds starting sometime in 5.16 bugzilla-daemon
2022-06-28 21:17 ` bugzilla-daemon
2022-06-28 22:30 ` bugzilla-daemon
2022-07-15 18:44 ` bugzilla-daemon
2022-08-15 11:02 ` bugzilla-daemon
2022-08-15 13:36 ` bugzilla-daemon
2022-08-16 11:08 ` bugzilla-daemon
2022-08-16 15:44 ` bugzilla-daemon
2022-08-16 16:10 ` bugzilla-daemon
2022-08-16 16:14 ` bugzilla-daemon
2022-08-16 17:11 ` bugzilla-daemon
2022-08-25 20:01 ` bugzilla-daemon
2022-08-25 20:31 ` bugzilla-daemon
2022-08-25 22:15 ` bugzilla-daemon
2022-08-26  7:00   ` Damien Le Moal
2022-08-26  7:00 ` bugzilla-daemon
2022-10-06 15:37 ` bugzilla-daemon
2022-10-06 23:48 ` bugzilla-daemon
2022-10-07  0:10 ` bugzilla-daemon
2022-10-07  0:15 ` bugzilla-daemon
2023-07-08 23:17 ` bugzilla-daemon
2023-07-09  7:09 ` bugzilla-daemon
2023-07-09 23:18 ` bugzilla-daemon
2023-07-10  0:18 ` bugzilla-daemon
2023-07-10  0:47 ` bugzilla-daemon
2023-07-10  1:02 ` bugzilla-daemon
2023-07-10  1:07 ` bugzilla-daemon
2023-07-10  2:51 ` bugzilla-daemon
2023-07-10  3:48 ` bugzilla-daemon
2023-07-10 17:00 ` bugzilla-daemon
2023-07-10 22:48 ` bugzilla-daemon
2023-07-11 21:39 ` bugzilla-daemon
2023-07-11 22:55 ` bugzilla-daemon
2023-07-20 21:52 ` bugzilla-daemon [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=bug-215880-11613-L7fnF2ByyJ@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).