linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216728] Thunderbolt USB Controller died after resume on Intel CometLake platform
Date: Wed, 30 Aug 2023 00:41:14 +0000	[thread overview]
Message-ID: <bug-216728-208809-AQI0cuSwUU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216728-208809@https.bugzilla.kernel.org/>

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

Mark Blakeney (mark.blakeney@bullet-systems.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark.blakeney@bullet-system
                   |                            |s.net

--- Comment #37 from Mark Blakeney (mark.blakeney@bullet-systems.net) ---
I'd like to confirm the same issue as Matt L reports just above (yay, I finally
found somebody else reporting this issue!). I have a Dell laptop and Dell
Thunderbolt dock and normally work on 2 dock connected screens + keyboard +
mouse with the laptop screen closed. If my laptop suspends like this, and I
then unplug the dock (e.g. to take the laptop away) then the screen stays blank
when I try to resume. This started when Arch Linux updated the kernel from
6.3.9 (good) to 6.4.1 (bad) and I have tested it bad with every point release
of 6.4 since up to 6.4.12 and is also bad on today's 6.5 which just rolled in
to Arch. I have generally been using the LTS kernel (6.1.49) to avoid this bug.

Actually, if you wait 2.5 minutes then the screen does kick back in to life
although this is inconsistent now on 6.5.

@Kamil, I was guided here from your similar bug at
(https://bugzilla.redhat.com/show_bug.cgi?id=2230357). I wouldn't be so quick
to say this is a Lenovo firmware issue. Seems to me there is something dodgy
with resume and thunderbolt and kernel 6.4/6.5.

-- 
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-08-30  0:41 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 10:25 [Bug 216728] New: Thunderbolt USB Controller died after resume on Intel CometLake platform bugzilla-daemon
2022-11-22 10:27 ` [Bug 216728] " bugzilla-daemon
2022-11-22 10:29 ` bugzilla-daemon
2022-11-24  9:19 ` bugzilla-daemon
2022-11-25  1:42 ` bugzilla-daemon
2022-11-25  6:34 ` bugzilla-daemon
2022-11-25  7:58 ` bugzilla-daemon
2022-11-28 10:47 ` bugzilla-daemon
2022-11-28 12:41 ` bugzilla-daemon
2022-11-28 12:42 ` bugzilla-daemon
2022-11-28 12:54 ` bugzilla-daemon
2022-11-29  3:26 ` bugzilla-daemon
2022-11-29 11:31 ` bugzilla-daemon
2022-11-29 11:33 ` bugzilla-daemon
2022-11-30  2:50 ` bugzilla-daemon
2022-11-30  2:52 ` bugzilla-daemon
2022-11-30  8:06 ` bugzilla-daemon
2022-11-30 13:17 ` bugzilla-daemon
2022-12-14  8:25 ` bugzilla-daemon
2022-12-15 11:52 ` bugzilla-daemon
2022-12-16  7:51 ` bugzilla-daemon
2022-12-16  7:55 ` bugzilla-daemon
2023-01-13 14:33 ` bugzilla-daemon
2023-02-01  7:20 ` bugzilla-daemon
2023-02-01  7:21 ` bugzilla-daemon
2023-02-08  4:29 ` bugzilla-daemon
2023-02-08 13:54 ` bugzilla-daemon
2023-03-06 12:03 ` bugzilla-daemon
2023-05-02 10:59 ` bugzilla-daemon
2023-05-02 11:00 ` bugzilla-daemon
2023-05-02 12:31 ` bugzilla-daemon
2023-05-15  1:57 ` bugzilla-daemon
2023-07-02 18:49 ` bugzilla-daemon
2023-07-02 18:50 ` bugzilla-daemon
2023-07-05 23:52 ` bugzilla-daemon
2023-08-21 12:34 ` bugzilla-daemon
2023-08-25 11:13 ` bugzilla-daemon
2023-08-30  0:41 ` bugzilla-daemon [this message]
2023-09-14 12:30 ` bugzilla-daemon
2023-09-14 15:46 ` bugzilla-daemon
2023-09-14 22:32 ` bugzilla-daemon
2023-09-14 22:39 ` bugzilla-daemon
2023-09-15 10:31 ` bugzilla-daemon
2023-09-15 10:32 ` bugzilla-daemon
2023-09-15 23:12 ` bugzilla-daemon
2024-02-12 20:29 ` bugzilla-daemon
2024-02-12 20:30 ` bugzilla-daemon
2024-02-13  7:08 ` 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-216728-208809-AQI0cuSwUU@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).