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: Fri, 15 Sep 2023 23:40:36 +0000 [thread overview]
Message-ID: <bug-217915-208809-xk0BKypSuK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217915-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217915
Mark Blakeney (mark.blakeney@bullet-systems.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dev@mattleach.net,
| |mika.westerberg@linux.intel
| |.com
Kernel Version| |6.4, 6.5
Regression|No |Yes
--- Comment #3 from Mark Blakeney (mark.blakeney@bullet-systems.net) ---
Note the sequence I did to capture that dmesg output was:
1. Added thunderbolt.dyndbg=+p to boot and rebooted.
2. Have laptop lid closed and working with 2 screens + keyboard + mouse on
dock.
3. Suspended my laptop.
4. Unplugged dock.
5. Opened lid on laptop and witnessed the 60s blank screen delay.
6. Captured the dmesg output and attached here.
Unlike the dmesg capture I did for bug #216728, this time I did not reconnect
the dock because I wish to point out clearly that this must be a bug in Linux
given that at the time the bug occurs (i.e. the screen does not recover after
resume) the dock is physically disconnected.
I should also reiterate on this bug that user Matt L on the original bug has a
Dell XPS laptop and thunderbolt dock and reports this exact same issue as me so
have CC him here.
--
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-15 23:40 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 [this message]
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
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-xk0BKypSuK@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).