linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	linux-usb@vger.kernel.org, Kai-Heng Feng <kaihengf@nvidia.com>
Subject: Re: Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`
Date: Thu, 14 Aug 2025 16:49:17 +0300	[thread overview]
Message-ID: <97d9420f-1a7f-433c-bdd7-b7bab6c45f00@linux.intel.com> (raw)
In-Reply-To: <e6fa9169-fff7-4e44-90a4-e0efe4e176fd@molgen.mpg.de>

On 13.8.2025 10.47, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> On an Intel Kaby Lake-R Dell XPS 13 9370, plugging in an 8-port LMP USB-C mini Dock into the port on the left side closer to the panel, Linux 6.16 logs:
> 
>      [    0.000000] Linux version 6.16-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian 6.16-1~exp1 (2025-07-31)
>      […]
>      [    0.000000] DMI: Dell Inc. XPS 13 9370/0RMYH9, BIOS 1.21.0 07/06/2022
>      […]
>      [   99.566522] xhci_hcd 0000:39:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
>      [   99.566565] usb 4-2.1: Failed to set U2 timeout to 0x3f,error code -110
>      [   99.566787] hub 4-2.1:1.0: USB hub found
>      [   99.587655] hub 4-2.1:1.0: config failed, can't read hub descriptor (err -22)
>      [   99.594669] usb 4-2.1: Failed to suspend device, error -19
>      […]
> 

Looks like the left side port is connected to a PCI hotpluggable Alpine Ridge xHCI controller.
This whole xHCI host will only appear on the PCI bus once a device is connected to the USB-C port

The right side port is handled by the other xHC that is always visible and already properly running.

The logs point towards Link Power Management or, runtime suspend race
issues with the two chained external USB 3 hubs.

Could you try running with the following kernel parameters set:
"usbcore.quirks=2109:0817:k"
to prevent Link Power Management (LPM) for the external hubs

"usbcore.autosuspend=-1"
to prevent runtime suspend of all usb devices

Does adding either one, or both help?

Could you also take logs and traces with dynamic debug and tracing enabled:

mount -t debugfs none /sys/kernel/debug
echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control
echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable
echo 1 > /sys/kernel/debug/tracing/tracing_on
< Reproduce issue >
Send output of dmesg
Send content of /sys/kernel/debug/tracing/trace

Thanks
Mathias

  reply	other threads:[~2025-08-14 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13  7:47 Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110` Paul Menzel
2025-08-14 13:49 ` Mathias Nyman [this message]
2025-08-21  7:44   ` Paul Menzel
2025-08-21 14:40     ` Mathias Nyman

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=97d9420f-1a7f-433c-bdd7-b7bab6c45f00@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kaihengf@nvidia.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /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).