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, 06 Oct 2022 23:48:06 +0000 [thread overview]
Message-ID: <bug-215880-11613-KcuVjbAg8M@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 #41 from Damien Le Moal (damien.lemoal@wdc.com) ---
(In reply to jason600 from comment #40)
> I have been using Damien Lemoal's patch for the last couple of days on
> kernel 5.19.8, it works fine for me, and no obvious issues.
>
> I also tried in on kernel 6.0, again works fine and no obvious issues.
>
> (In reply to damien.lemoal from comment #39)
> > I am not sure at all this is correct though. This actually may break other
> > suspend/resume flavors. If we could somehow synchronize scsi pm resume to
> > run *after* ata pm resume, all problems should go away I think.
>
> With regard to Damiens comments, and the problems with this patch last time
> it was submitted, I think it would be a good idea to have more people
> testing this patch before re-submitting it.
I did not submit that patch on the lists, because I am not convinced this is
the right approach. It is a "hack" right now. As mentioned, the problem is that
scsi and ata pm resume are running at the same time because the dev/pm code
does not seem to know the dependency between the devices (struct dev). Would
need to dig further into that first to see if a cleaner solution can be coded.
Will try, but busy, so it may take some time. I first need to be able to
recreate the issue on my systems. Will start with that :)
--
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:[~2022-10-06 23:48 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 [this message]
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
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-KcuVjbAg8M@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).