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: Fri, 13 Feb 2026 15:01:04 +0000	[thread overview]
Message-ID: <bug-220904-208809-uCtqUC5rIa@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 #13 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
I was able to recreate this with a USB-C hub and forced xHC reset in resume.

So far no simple solution to solve this. I tried disabling the port in resume
path before host reset, tried toggling port power before host reset, but
nothing helped.

So looks like we need to focus on why your Intel xHC at 0000:00:0d.0 is
reset in resume, and avoid that.

Your log shows you have the  XHCI_RESET_ON_RESUME quirk BIT(7) set, which
explains the reset.

[1.901865] xhci_hcd 0000:00:0d.0: hcc params 0x20007fc1 hci version 0x120
quirks 0x0000000200009890

Intel xHC hosts don't normally have this set. Looks like its forced in kernel
cmdline at boot in your case:

Kernel command line: ... xhci_hcd.quirks=0x80 rw quiet splash

Any idea why this is set? 
Can you try to remove it and see if it works

-- 
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:[~2026-02-13 15:01 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
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 [this message]
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-uCtqUC5rIa@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