public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220904] [BUG] ucsi_acpi: USB 3.0 SuperSpeed not negotiated on USB-C hot-plug
Date: Tue, 30 Dec 2025 18:42:43 +0000	[thread overview]
Message-ID: <bug-220904-208809-V6FmHokPgV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220904-208809@https.bugzilla.kernel.org/>

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

--- Comment #2 from Thomas Jetzinger (thomas@jetzinger.com) ---
Created attachment 309097
  --> https://bugzilla.kernel.org/attachment.cgi?id=309097&action=edit
Disabling UCSI does NOT resolve the issue

Hi Heikki,

Here are the logs from two test scenarios. Both tests confirm the issue
persists regardless of UCSI driver status.

## System Info
 - ThinkPad X1 Carbon Gen 11 (21HMCTO1WW)
 - BIOS: N3XET63W (1.38)
 - Kernel: 6.18.2-zen2-1-zen (custom build, also tested on stock 6.12)
 - Dock: ThinkPad USB-C Dock Gen2 (40AS)

## Test 1: UCSI Enabled (Normal Configuration)

**Boot with dock connected:** USB 3.0 works
 - Ethernet (17ef:a387) on Bus 002 @ 5000M
 - USB3.1 Hub (17ef:a391) on Bus 002 @ 10000M

**After disconnect + reconnect:** USB 3.0 FAILS
 - Only USB 2.0 devices enumerate (480M on Bus 003)
 - Bus 002 (20Gbps SuperSpeed) is completely empty
 - Ethernet and USB 3.0 hub missing

Key log pattern:
 usb usb1: root hub lost power or was reset
 usb usb2: root hub lost power or was reset
 usb 3-3: new high-speed USB device number 14 using xhci_hcd  ← USB 2.0 only

## Test 2: UCSI Disabled (blacklist ucsi_acpi)

**Boot with dock connected:** USB 3.0 works (same as Test 1)

**After disconnect + reconnect:** USB 3.0 STILL FAILS
 - Identical failure pattern to Test 1
 - Same "root hub lost power or was reset" messages
 - Only high-speed (USB 2.0) enumeration

## Conclusion

Disabling UCSI does NOT resolve the issue. The problem appears to be in the
USB-C/Thunderbolt physical layer negotiation, not the UCSI driver. The repeated
"root hub lost power or was reset" messages on usb1/usb2 (Thunderbolt/USB4
buses) during hot-plug suggest the xHCI controller is being reset but failing
to re-enumerate SuperSpeed devices.

Full logs attached:
 - bug-220904-test1-ucsi-enabled.txt (Test 1 with UCSI)
 - bug-220904-test2-ucsi-disabled.txt (Test 2 without UCSI)

-- 
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:[~2025-12-30 18:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 12:00 [Bug 220904] New: [BUG] ucsi_acpi: USB 3.0 SuperSpeed not negotiated on USB-C hot-plug bugzilla-daemon
2025-12-30 11:54 ` [Bug 220904] " bugzilla-daemon
2025-12-30 18:42 ` bugzilla-daemon [this message]
2025-12-31  5:59 ` bugzilla-daemon
2025-12-31  8:54 ` bugzilla-daemon
2025-12-31  9:24 ` bugzilla-daemon
2025-12-31 10:31 ` bugzilla-daemon
2025-12-31 13:31 ` bugzilla-daemon
2025-12-31 14:46 ` bugzilla-daemon
2026-01-05 15:28 ` bugzilla-daemon
2026-01-09 12:19 ` bugzilla-daemon
2026-01-20 15:54 ` bugzilla-daemon
2026-01-20 18:56 ` bugzilla-daemon
2026-02-13 15:01 ` bugzilla-daemon
2026-02-17 11:44 ` bugzilla-daemon
2026-02-18 16:51 ` 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-220904-208809-V6FmHokPgV@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