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: Sat, 16 Sep 2023 22:07:42 +0000 [thread overview]
Message-ID: <bug-217915-208809-HQE2ErfPPV@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 #7 from Mark Blakeney (mark.blakeney@bullet-systems.net) ---
Mario, we already know that commit
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e8b908146d44310473e43b3382eca126e12d279c
caused this issue but Mika says that change (which is merely a timeout increase
from 1 sec to 60 sec) is valid and has merely exposed this latent problem.
What I don't get is that this bug occurs after the Thunderbolt dock is
disconnected and the system is then resumed so surely it has got to be a
straight out logical error that the kernel sits around for 60 secs waiting for
a device that is no longer connected?
--
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-16 22:07 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 [this message]
2023-09-17 6:57 ` bugzilla-daemon
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-HQE2ErfPPV@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).