From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220016] New: USB devices plugged into USB hubs on 6.14.2-300.fc42.x86_64 do not work
Date: Wed, 16 Apr 2025 00:25:05 +0000 [thread overview]
Message-ID: <bug-220016-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220016
Bug ID: 220016
Summary: USB devices plugged into USB hubs on
6.14.2-300.fc42.x86_64 do not work
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: joe@solidadmin.com
Regression: No
Created attachment 307967
--> https://bugzilla.kernel.org/attachment.cgi?id=307967&action=edit
6.14.2-300.fc42.x86_64 journalctl -k output
Upgrading to 6.14.2 results in any USB device plugged into a USB hub to not
work correctly. Downgrading to 6.13.7-200.fc41.x86_64 allows for all USB
devices to work as expected. This issue also seems to be present in 6.15.0 as
well.
Here is the downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=2353984
with more details. Another user on the RH BZ with a very similar motherboard is
reporting that none of their USB devices are working when upgrading to 6.14.2
I have attached the journalctl -k output for 6.13.7-200.fc41.x86_64 and one
thing that seems notable is:
Apr 14 20:06:49 kernel: ahci 0000:26:00.0: version 3.0
Apr 14 20:06:49 kernel: ahci 0000:26:00.0: probe with driver ahci failed with
error -12
Apr 14 20:06:49 kernel: ahci 0000:27:00.0: probe with driver ahci failed with
error -12
Apr 14 20:06:49 kernel: xhci_hcd 0000:23:00.0: init 0000:23:00.0 fail, -16
Apr 14 20:06:49 kernel: xhci_hcd 0000:23:00.0: probe with driver xhci_hcd
failed with error -16
Apr 14 20:06:49 kernel: xhci_hcd 0000:28:00.1: init 0000:28:00.1 fail, -16
Apr 14 20:06:49 kernel: xhci_hcd 0000:28:00.1: probe with driver xhci_hcd
failed with error -16
Apr 14 20:06:49 kernel: xhci_hcd 0000:28:00.3: init 0000:28:00.3 fail, -16
Apr 14 20:06:49 kernel: xhci_hcd 0000:28:00.3: probe with driver xhci_hcd
failed with error -16
and in the 6.13.7-200.fc41.x86_64 output, this is not present. I have attached
the 6.13.7-200.fc41.x86_64 journalctl -k output as well and the lspci -v output
is below.
# lspci -v|rg -A 15 USB
06:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0
Host Controller (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Device 8815
Flags: bus master, fast devsel, latency 0, IRQ 94, IOMMU group 85
Memory at f3600000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [64] Express Endpoint, IntMsgNum 0
Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=8 Masked-
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Capabilities: [150] Advanced Error Reporting
Capabilities: [2a0] Access Control Services
Capabilities: [370] Transaction Processing Hints
Kernel driver in use: xhci_hcd
--
23:00.0 USB controller: ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller
(prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Device 87c1
Flags: bus master, fast devsel, latency 0, IRQ 65, IOMMU group 51
Memory at f0600000 (64-bit, non-prefetchable) [size=32K]
Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [68] MSI-X: Enable+ Count=8 Masked-
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0
Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device 0201
Capabilities: [100] Advanced Error Reporting
Capabilities: [200] Secondary PCI Express
Capabilities: [300] Latency Tolerance Reporting
Capabilities: [400] L1 PM Substates
Kernel driver in use: xhci_hcd
--
28:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host
Controller (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Device 8815
Flags: bus master, fast devsel, latency 0, IRQ 75, IOMMU group 50
Memory at f0100000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [64] Express Endpoint, IntMsgNum 0
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Kernel driver in use: xhci_hcd
28:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host
Controller (prog-if 30 [XHCI])
Subsystem: Advanced Micro Devices, Inc. [AMD] Device 148c
Flags: bus master, fast devsel, latency 0, IRQ 76, IOMMU group 50
Memory at f0000000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [64] Express Endpoint, IntMsgNum 0
Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=8 Masked-
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Kernel driver in use: xhci_hcd
--
2c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0
Host Controller (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Device 8815
Flags: bus master, fast devsel, latency 0, IRQ 85, IOMMU group 62
Memory at f0700000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [64] Express Endpoint, IntMsgNum 0
Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=8 Masked-
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Capabilities: [150] Advanced Error Reporting
Capabilities: [2a0] Access Control Services
Capabilities: [370] Transaction Processing Hints
Kernel driver in use: xhci_hcd
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-04-16 0:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 0:25 bugzilla-daemon [this message]
2025-04-16 0:26 ` [Bug 220016] USB devices plugged into USB hubs on 6.14.2-300.fc42.x86_64 do not work bugzilla-daemon
2025-04-16 7:21 ` bugzilla-daemon
2025-04-16 8:53 ` bugzilla-daemon
2025-04-16 17:20 ` bugzilla-daemon
2025-04-16 17:43 ` bugzilla-daemon
2025-04-16 17:43 ` bugzilla-daemon
2025-04-16 17:51 ` bugzilla-daemon
2025-04-16 21:38 ` bugzilla-daemon
2025-04-16 22:19 ` bugzilla-daemon
2025-04-17 13:22 ` bugzilla-daemon
2025-04-18 16:25 ` bugzilla-daemon
2025-04-18 17:37 ` bugzilla-daemon
2025-04-18 17:38 ` bugzilla-daemon
2025-04-18 17:38 ` bugzilla-daemon
2025-04-18 17:39 ` bugzilla-daemon
2025-04-18 17:45 ` bugzilla-daemon
2025-04-18 17:53 ` bugzilla-daemon
2025-04-18 18:05 ` bugzilla-daemon
2025-04-18 18:05 ` bugzilla-daemon
2025-04-18 18:06 ` bugzilla-daemon
2025-04-18 18:06 ` bugzilla-daemon
2025-04-18 18:09 ` bugzilla-daemon
2025-04-21 17:35 ` bugzilla-daemon
2025-04-25 16:05 ` bugzilla-daemon
2025-04-25 19:34 ` bugzilla-daemon
2025-04-25 19:35 ` bugzilla-daemon
2025-04-28 17:06 ` bugzilla-daemon
2025-04-28 19:00 ` bugzilla-daemon
2025-04-30 10:39 ` bugzilla-daemon
2025-04-30 10:44 ` bugzilla-daemon
2025-04-30 14:46 ` bugzilla-daemon
2025-04-30 14:46 ` 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-220016-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