Skip to contentSkip to conversation

New: Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

Bug 220460 [email protected] 1 participant 13 messages Aug 17, 2025 – Aug 25, 2025 USB

lore
Share & tools
lore

[email protected]

author
#0 lore raw

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

            Bug ID: 220460
           Summary: Plugging USB-C adapter into one port results in
                    `Failed to set U2 timeout to 0x3f,error code -110`
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 308500
--> https://bugzilla.kernel.org/attachment.cgi?id=308500&action=edit
Output of dmesg (Linux 6.16.1) with dynamic debug of xhci_hcd and usbcore

Attachments for linux-usb list message [Plugging USB-C adapter into one port
results in Failed to set U2 timeout to 0x3f,error code -110](https://lore.kernel.org/linux-usb/[email protected]/T/#mb4ac7d8ec970fa3a3cfb451d725d28482b2ad0d5)

From Mathias’ answer:

Quoted 11 lines

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

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#1 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

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

--- Comment #1 from Artem S. Tashkinov ([email protected]) --- Is this a regression?

Does it work under Windows?

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#2 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #2 from Paul Menzel ([email protected]) ---

Quoted 3 lines

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

I wanted to attach the contents of /sys/kernel/debug/tracing/trace, but Bugzilla (Nginx) aborts with error 413 Request Entity Too Large for the 4 MB file despite listing 5 MB as limit. So, I uploaded it [1], until Bugzilla setup is fixed.

[1]:
https://owww.molgen.mpg.de/~pmenzel/20250817--dell-xps-13-9370--linux-6.16.1-messages--tracing-trace.txt

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#3 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #3 from Paul Menzel ([email protected]) --- Created attachment 308513
--> https://bugzilla.kernel.org/attachment.cgi?id=308513&action=edit
Content of /sys/kernel/debug/tracing/trace

The bugzilla.kernel.org admins fixed the issue, so I attach it here, and invalidate the URL from the last comment.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#4 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

Paul Menzel ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

 Attachment #308513|0                           |1

is obsolete| |

--- Comment #4 from Paul Menzel ([email protected]) --- Created attachment 308514
--> https://bugzilla.kernel.org/attachment.cgi?id=308514&action=edit
Content of /sys/kernel/debug/tracing/trace

Looks like the file wasn’t fully downloaded to my system. Try again, and obsolete the other file.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#5 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #5 from Mathias Nyman ([email protected]) --- Thanks, trace show the link between host and hub goes to an error state immediately after enabling U1 and U2 link power save states.

Hub driver sends a SetPortFeature U1 timeout 41us to hub port 1. hub is now allowed to set port 1 link to U1 power save state after 41us of inactivity:

862.173255: xhci_queue_trb: CTRL: @0x00000000fffc7600 bRequestType 23 bRequest 03 wValue 0017 wIndex 2901 wLength 0 length 8 TD size 0 intr 0 type 'Setup Stage' flags I:i:c

Tell xHCI host that the new MEL (maximum exit latency) to get link up and running has changed, set a new value of 747us:

862.173694: xhci_dbg_context_change: Set up evaluate context for LPM MEL change.
862.173696: xhci_configure_endpoint: RS 00001 super-speed Ctx Entries 3 MEL 747 us Port# 4/0 [TT Slot 0 Port# 0 TTT 0 Intr 0] Addr 0 State enabled/disabled

Hub driver sends a SetPortFeature U2 timeout 16128us to hub port 1. hub is now allowed to set port 1 link to U1 power save state after 16128us of inactivity:

862.173771: xhci_queue_trb: CTRL: @0x00000000fffc7620 bRequestType 23 bRequest 03 wValue 0018 wIndex 3f01 wLength 0 length 8 TD size 0 intr 0 type 'Setup Stage' flags I:i:c

Link suddenly goes to error (Inactive) state, most likely due to failure to enter U1/U2. Could also be related to bad U1,U2 MEL or SEL (system exit latecy) values.

862.175770: xhci_handle_event: EVENT: @0x00000000ff8facd0 TRB 0000000004000000 status 'Success' len 0 slot 0 ep 0 type 'Port Status Change Event' flags e:c 862.175802: xhci_handle_port_status: port 4-1: 0x004202c0 Powered Not-connected Disabled Link:Inactive PortSpeed:0 Change: CSC PLC Wake:

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#6 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #6 from Mathias Nyman ([email protected]) --- Could you take the same logs when connecting the dock to the working USB-C port?

Also output of "lsusb -v" (as root) with working dock could be useful

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#7 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #7 from Paul Menzel ([email protected]) --- Yes, I am going to do so later. Just to avoid misunderstandings:

1. Even with the error messages, the USB-C hub seems to work. (I just tested the Ethernet port though.)
2. Does “working dock“ dock mean, the USB-C port where I get no error messages?

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#8 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #8 from Paul Menzel ([email protected]) --- Created attachment 308535
--> https://bugzilla.kernel.org/attachment.cgi?id=308535&action=edit
Output of sudo lsusb -v with LMP adapter connected to left USB-C port with no errors/warnings

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#9 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #9 from Paul Menzel ([email protected]) --- Created attachment 308536
--> https://bugzilla.kernel.org/attachment.cgi?id=308536&action=edit
Linux 6.16.1 messages (dmesg) with LMP adapter connected to left USB-C ports (first with erros, then second without)

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#10 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #10 from Paul Menzel ([email protected]) --- Created attachment 308537
--> https://bugzilla.kernel.org/attachment.cgi?id=308537&action=edit
Content of /sys/kernel/debug/tracing/trace with LMP plugged first into left port with errors, and then to other left port without errors

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#11 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #11 from Paul Menzel ([email protected]) --- Created attachment 308545
--> https://bugzilla.kernel.org/attachment.cgi?id=308545&action=edit
Output of dmesg (Linux 6.16.1) with dynamic debug of xhci_hcd and usbcore, USB-C connector plugged both ways

It turns out, that I am only able to reproduce the issue, when the USB-C connector is plugged in a certain position. Without wrangling the cable, it can be described, that it happens with the adapter logo on the top side, and switch it (and the connector) upside down, it’s not reproducible. Does that make sense? New logs attached.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
author
#12 lore raw

[Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`

In reply to [email protected]

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

--- Comment #12 from Paul Menzel ([email protected]) --- Created attachment 308546
--> https://bugzilla.kernel.org/attachment.cgi?id=308546&action=edit
Content of /sys/kernel/debug/tracing/trace, USB-C connector plugged both ways

Signature · 4 lines
You may reply to this email to add a comment.

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