All of lore.kernel.org
 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: Mon, 12 Feb 2024 20:29:40 +0000	[thread overview]
Message-ID: <bug-216728-208809-iDSU74O8W9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216728-208809@https.bugzilla.kernel.org/>

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

Rustam Abdullaev (rustamabd@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rustamabd@gmail.com

--- Comment #45 from Rustam Abdullaev (rustamabd@gmail.com) ---
So, on my system, Lenovo X1 Extreme Gen 5, the commit
e8b908146d44310473e43b3382eca126e12d279c does not fix the disappearing
Thunderbolt issue and instead adds a 65-second delay when resuming from sleep.
Could it be that such a wait is too long? After upgrading to 6.4.1+ the wait
after each resume is excruciating.
And can anything be done to fix the Thunderbolt issue on my system?

[   49.135899] pcieport 0000:21:02.0: Unable to change power state from D3cold
to D0, device inaccessible
[   51.415400] xhci_hcd 0000:56:00.0: not ready 1023ms after resume; waiting
[   51.415407] thunderbolt 0000:22:00.0: not ready 1023ms after resume; waiting
[   52.471401] xhci_hcd 0000:56:00.0: not ready 2047ms after resume; waiting
[   52.471406] thunderbolt 0000:22:00.0: not ready 2047ms after resume; waiting
[   54.743394] xhci_hcd 0000:56:00.0: not ready 4095ms after resume; waiting
[   54.743399] thunderbolt 0000:22:00.0: not ready 4095ms after resume; waiting
[   59.095398] xhci_hcd 0000:56:00.0: not ready 8191ms after resume; waiting
[   59.095403] thunderbolt 0000:22:00.0: not ready 8191ms after resume; waiting
[   67.543405] xhci_hcd 0000:56:00.0: not ready 16383ms after resume; waiting
[   67.543410] thunderbolt 0000:22:00.0: not ready 16383ms after resume;
waiting
[   85.207405] xhci_hcd 0000:56:00.0: not ready 32767ms after resume; waiting
[   85.207409] thunderbolt 0000:22:00.0: not ready 32767ms after resume;
waiting
[  120.023396] xhci_hcd 0000:56:00.0: not ready 65535ms after resume; giving up
[  120.023401] thunderbolt 0000:22:00.0: not ready 65535ms after resume; giving
up
[  120.023570] xhci_hcd 0000:56:00.0: Unable to change power state from D3cold
to D0, device inaccessible
[  120.023628] thunderbolt 0000:22:00.0: Unable to change power state from
D3cold to D0, device inaccessible
[  120.092723] ACPI: EC: event unblocked
[  120.094771] pcieport 0000:00:1d.0: pciehp: Slot(8): Card not present
[  120.095141] xhci_hcd 0000:56:00.0: Unable to change power state from D3cold
to D0, device inaccessible
[  120.095163] xhci_hcd 0000:56:00.0: Controller not ready at resume -19
[  120.095166] xhci_hcd 0000:56:00.0: PCI post-resume error -19!
[  120.095167] xhci_hcd 0000:56:00.0: HC died; cleaning up
[  120.095175] xhci_hcd 0000:56:00.0: PM: dpm_run_callback():
pci_pm_resume+0x0/0x110 returns -19
[  120.095200] xhci_hcd 0000:56:00.0: PM: failed to resume async: error -19
[  120.110113] xhci_hcd 0000:56:00.0: remove, state 4
[  120.110120] usb usb3: USB disconnect, device number 1

-- 
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:[~2024-02-12 20:29 UTC|newest]

Thread overview: 49+ 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
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 [this message]
2024-02-12 20:30 ` bugzilla-daemon
2024-02-13  7:08 ` bugzilla-daemon
2026-04-24 19:47 ` 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-iDSU74O8W9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.