From: Michal Pecio <michal.pecio@gmail.com>
To: Arisa Snowbell <arisa.snowbell@gmail.com>
Cc: linux-usb@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] USB-A devices not working on boot after recent USB merge
Date: Tue, 7 Oct 2025 23:17:09 +0200 [thread overview]
Message-ID: <20251007231709.6c16802e.michal.pecio@gmail.com> (raw)
In-Reply-To: <CABpa4MA9unucCoKtSdzJyOLjHNVy+Cwgz5AnAxPkKw6vuox1Nw@mail.gmail.com>
On Tue, 7 Oct 2025 22:47:52 +0200, Arisa Snowbell wrote:
> Hello,
>
> this is my first time here, so I hope I am doing everything correctly,
> if not - help would be appreciated.
>
> I found regression in the linux-mainline aka linuses branch, more
> specifically in the recent USB merge (commit
> c6006b8ca14dcc604567be99fc4863e6e11ab6e3).
>
> All my USB-C client -> USB-A host aka computer(probably all USB-A
> devices but I don't have more to test) - devices are not detected when
> I boot with this patch, I have to replug the device for it to even
> show up in dmesg logs.
> One device is mice and another one is audio DAC that also shows up as
> hub in the dmesg normally.
>
> I reverted the USB merge and everything is fine again.
Hi,
Can you bisect the merged USB development branch?
It looks like 8f5ae30d69d7 (v6.17-rc1) is likely good
and e40b984b6c4c is the merged commit, should be bad.
Regards,
Michal
next prev parent reply other threads:[~2025-10-07 21:17 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 [this message]
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
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=20251007231709.6c16802e.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=arisa.snowbell@gmail.com \
--cc=linux-usb@vger.kernel.org \
--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