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 216822] New: Thunderbolt USB Controller (Maple Ridge) and its upstream pcie port fail to runtime resume
Date: Mon, 19 Dec 2022 03:39:58 +0000	[thread overview]
Message-ID: <bug-216822-208809@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 216822
           Summary: Thunderbolt USB Controller (Maple Ridge) and its
                    upstream pcie port fail to runtime resume
           Product: Drivers
           Version: 2.5
    Kernel Version: kernel 6.0 and later
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: chris.chiu@canonical.com
        Regression: No

Created attachment 303426
  --> https://bugzilla.kernel.org/attachment.cgi?id=303426&action=edit
output of lspci -vt

The xHCI host controller(8086:1138) of the TBT4 add-on card fail to detect any
USB-C devices after boot. After forcing the runtime resume by `echo 'on' >
'/sys/bus/usb/devices/usb4/power/control`, the connected usb-c device can be
detected.
After turn on PCI_DEBUG and DEBUG of the usbcode/xhci_hcd, there seems no
problem when the usb port go into runtime suspend
```
[  579.488151] xhci_hcd 0000:13:00.0: set port remote wake mask, actual port
4-1 status  = 0xe0002a0
[  579.488221] xhci_hcd 0000:13:00.0: set port remote wake mask, actual port
4-2 status  = 0xe0002a0
[  579.488239] hub 4-0:1.0: hub_suspend
[  579.488260] usb usb4: bus auto-suspend, wakeup 1
[  579.488283] xhci_hcd 0000:13:00.0: xhci_hub_status_data: stopping usb4 port
polling
[  579.488306] xhci_hcd 0000:13:00.0: config port 4-1 wake bits, portsc:
0xa0002a0, write: 0xa0202a0
[  579.488316] xhci_hcd 0000:13:00.0: config port 4-2 wake bits, portsc:
0xa0002a0, write: 0xa0202a0
[  579.488323] xhci_hcd 0000:13:00.0: config port 3-1 wake bits, portsc:
0xa0002a0, write: 0xa0202a0
[  579.488328] xhci_hcd 0000:13:00.0: config port 3-2 wake bits, portsc:
0xa0002a0, write: 0xa0202a0
[  579.488333] xhci_hcd 0000:13:00.0: xhci_suspend: stopping usb3 port polling.
[  579.488359] xhci_hcd 0000:13:00.0: // Setting command ring address to
0x11aa08001
[  579.488536] xhci_hcd 0000:13:00.0: hcd_pci_runtime_suspend: 0
```

but no messages in kernel after plug in a usb device. I expect to see the
runtime resume first on the upstream port pcieport 0000:00:1d.0, and then the
xhci_hcd 0000:13:00.0 but nothing. Please refer to the attached lspci output
for the device information and suggest what we should do next to find out the
cause. Thanks

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-12-19  3:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  3:39 bugzilla-daemon [this message]
2022-12-19  3:40 ` [Bug 216822] Thunderbolt USB Controller (Maple Ridge) and its upstream pcie port fail to runtime resume bugzilla-daemon
2022-12-19  3:43 ` bugzilla-daemon
2022-12-22  3:50 ` bugzilla-daemon
2022-12-22  8:13 ` bugzilla-daemon
2022-12-22 14:22 ` 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-216822-208809@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).