linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220016] USB devices plugged into USB hubs on 6.14.2-300.fc42.x86_64 do not work
Date: Wed, 16 Apr 2025 17:51:29 +0000	[thread overview]
Message-ID: <bug-220016-208809-jCJ4FzPg0L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220016-208809@https.bugzilla.kernel.org/>

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

--- Comment #7 from Steven A. Falco (stevenfalco@gmail.com) ---
I appear to be having the same problem, and I've attached journal logs from a
good boot and a bad boot.  In my case I have a mouse and keyboard directly
plugged into the motherboard.

The keyboard was not working once I upgraded to kernel 6.14 but the mouse was
working.  I stepped back to kernel 6.13, and both mouse and keyboard were
working.

I tried switching which connectors the mouse and keyboard were plugged into,
and at that point the mouse wasn't working but the keyboard was working.

So with kernel 6.14 several of the motherboard jacks were not functional.

I looked at the pci information, and the usb devices are:

usb1/2  0000:23:00.0 ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller
usb3/4  0000:28:00.1 Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host
Controller
usb5/6  0000:28:00.3 Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host
Controller
usb7/8  0000:2d:00.3 Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host
Controller
usb9/10 0000:05:00.3 Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host
Controller

Apparently, with 6.14 one of the Matisse controllers was recognized, but the
other was not.  And neither of the Starship controllers were recognized.

-- 
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-04-16 17:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16  0:25 [Bug 220016] New: USB devices plugged into USB hubs on 6.14.2-300.fc42.x86_64 do not work bugzilla-daemon
2025-04-16  0:26 ` [Bug 220016] " 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 [this message]
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-jCJ4FzPg0L@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;
as well as URLs for NNTP newsgroup(s).