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: Tue, 29 Nov 2022 03:26:51 +0000	[thread overview]
Message-ID: <bug-216728-208809-zd2zdDhkfl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216728-208809@https.bugzilla.kernel.org/>

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

--- Comment #11 from Chris Chiu (chris.chiu@canonical.com) ---
Created attachment 303316
  --> https://bugzilla.kernel.org/attachment.cgi?id=303316&action=edit
dmesg with PCI_DEBUG

[   35.907673] pcieport 0000:03:02.0: waiting 100 ms for downstream link, after
activation
[   35.907687] pcieport 0000:03:00.0: waiting 100 ms for downstream link, after
activation
[   37.038857] xhci_hcd 0000:38:00.0: waiting additional 100 ms to become
accessible
[   37.039165] thunderbolt 0000:04:00.0: restoring config space at offset 0x14
(was 0x0, writing 0x9df40000)
[   37.039181] thunderbolt 0000:04:00.0: restoring config space at offset 0x10
(was 0x0, writing 0x9df00000)
[   37.039196] thunderbolt 0000:04:00.0: restoring config space at offset 0x4
(was 0x100000, writing 0x100406)
[   37.146904] xhci_hcd 0000:38:00.0: Unable to change power state from D3cold
to D0, device inaccessible
[   37.148017] pcieport 0000:03:02.0: re-enabling LTR

-- 
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:[~2022-11-29  3:26 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 [this message]
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
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-zd2zdDhkfl@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.