From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217915] System fails to resume correctly after Thunderbolt dock disconnected while sleeping
Date: Sun, 17 Sep 2023 06:57:25 +0000 [thread overview]
Message-ID: <bug-217915-208809-bEAUTCQ4wd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217915-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217915
--- Comment #8 from Mika Westerberg (mika.westerberg@linux.intel.com) ---
Created attachment 305120
--> https://bugzilla.kernel.org/attachment.cgi?id=305120&action=edit
Mark devices as disconnected if resume fails
I can reproduce this myself now. The reason why it takes so long is indeed that
we try to resume the devices that are behind the port whose link did not come
up after suspend and since they are gone we end up waiting them for the ~60s
each.
Can you try the attached patch? On my system this makes the issue go away.
--
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-09-17 6:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 23:11 [Bug 217915] New: System fails to resume correctly after Thunderbolt dock disconnected while sleeping bugzilla-daemon
2023-09-15 23:23 ` [Bug 217915] " bugzilla-daemon
2023-09-15 23:29 ` bugzilla-daemon
2023-09-15 23:40 ` bugzilla-daemon
2023-09-16 1:22 ` bugzilla-daemon
2023-09-16 1:23 ` bugzilla-daemon
2023-09-16 17:14 ` bugzilla-daemon
2023-09-16 22:07 ` bugzilla-daemon
2023-09-17 6:57 ` bugzilla-daemon [this message]
2023-09-17 11:26 ` bugzilla-daemon
2023-09-17 19:01 ` bugzilla-daemon
2023-09-18 5:36 ` bugzilla-daemon
2023-10-10 23:23 ` 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-217915-208809-bEAUTCQ4wd@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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).