Linux USB
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Arisa Snowbell <arisa.snowbell@gmail.com>
Cc: linux-usb@vger.kernel.org, regressions@lists.linux.dev,
	Niklas Neronin <niklas.neronin@linux.intel.com>,
	Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: [REGRESSION] USB-A devices not working on boot after recent USB merge
Date: Wed, 8 Oct 2025 08:20:55 +0200	[thread overview]
Message-ID: <20251008082055.5646dadc.michal.pecio@gmail.com> (raw)
In-Reply-To: <CABpa4MCg7yixe7O8Pp+YwvpxeC=1JPhMhAap12RjtV6pcxFYgQ@mail.gmail.com>

On Wed, 8 Oct 2025 03:15:31 +0200, Arisa Snowbell wrote:
> The first bad commit seems to be
> [719de070f764e079cdcb4ddeeb5b19b3ddddf9c1] usb: xhci-pci: add support
> for hosts with zero USB3 ports. All USB-A devices stop being
> visible/detected.

Hmm, OK. Copying xHCI people.

So the issue is that there are some USB ports on the motherboard where
devices work when they are hotplugged, but nothing is enumerated during
boot, correct?

Are all USB-A ports affected or only those limited to USB 2.0 speed?

If you look at hotplug notifications like
[    4.612030] usb 18-2: new high-speed USB device number 2 using xhci_hcd

the first number (18) is the USB bus number. You can then find the PCI
address of the xHCI controller by looking at the root hub (device 1):

$ lsusb -vs 18:1 |grep iSerial
  iSerial                 1 0000:0c:00.0


Can you reproduce the bug without rebooting by connecting some device
and then reloading the xhci driver on this particular controller?

echo 0000:0c:00.0 |tee /sys/bus/pci/drivers/xhci_hcd/unbind /sys/bus/pci/drivers/xhci_hcd/bind

Regards,
Michal

  parent reply	other threads:[~2025-10-08  6:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 20:47 [REGRESSION] USB-A devices not working on boot after recent USB merge Arisa Snowbell
2025-10-07 21:17 ` Michal Pecio
2025-10-07 22:30   ` Arisa Snowbell
2025-10-08  1:15     ` Arisa Snowbell
2025-10-08  1:41       ` Arisa Snowbell
2025-10-08  6:20       ` Michal Pecio [this message]
2025-10-08  9:02         ` Arisa Snowbell
2025-10-08 11:05           ` Michal Pecio
2025-10-08 12:16             ` Arisa Snowbell
2025-10-08 20:34               ` Michal Pecio
2025-10-08 21:29                 ` Arisa Snowbell
2025-10-08 22:25                   ` Arisa Snowbell
2025-10-09 11:14                     ` [REGRESSION] [REPRO] " Michal Pecio
2025-10-09 11:30                       ` Mathias Nyman
2025-10-09 13:27                         ` Michal Pecio
2025-10-10  8:15                           ` Mathias Nyman
2025-10-10  9:15                             ` Arisa Snowbell
2025-10-13  7:22                             ` [PATCH usb-next] usb: xhci-pci: Cleanup xhci_pci_setup() for shared HCD Michal Pecio
2025-10-13  7:55                               ` Mathias Nyman
2025-10-13  8:04                                 ` [PATCH v2 RFT] usb: xhci-pci: Fix USB2-only root hub registration Michal Pecio
2025-10-13 13:52                                   ` Arisa Snowbell
2025-10-13 14:33                                   ` Hanabishi
2025-10-13 16:03                                   ` Michal Kubecek
2025-11-14 14:06                                 ` [PATCH] usb: xhci-pci: Clean up xhci_pci_setup() Michal Pecio
2025-10-09 12:16                       ` [REGRESSION] [REPRO] USB-A devices not working on boot after recent USB merge Arisa Snowbell
2025-10-09 12:29                         ` [PATCH] usb: xhci-pci: Fix USB2-only root hub registration Michal Pecio
2025-10-09 12:49                           ` Arisa Snowbell
2025-10-09 13:08                             ` Mathias Nyman
2025-10-09 11:15                     ` [REGRESSION] USB-A devices not working on boot after recent USB merge Mathias Nyman

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=20251008082055.5646dadc.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=arisa.snowbell@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=niklas.neronin@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    /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