[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAD=FV=WDx-WcosBWf2yd3sLx5pEyjOgbs_Y5RBF=+b=0q3dBww@mail.gmail.com>
Date: Wed, 19 Nov 2025 08:55:45 -0800
From: Doug Anderson <dianders@...omium.org>
To: incogcyberpunk@...ton.me
Cc: Thorsten Leemhuis <regressions@...mhuis.info>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>, "marcel@...tmann.org" <marcel@...tmann.org>,
"luiz.dentz@...il.com" <luiz.dentz@...il.com>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
"johan.hedberg@...il.com" <johan.hedberg@...il.com>, "sean.wang@...iatek.com" <sean.wang@...iatek.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] Bluetooth adapter provided by `btusb` not recognized
since v6.13.2
Hi,
On Wed, Nov 19, 2025 at 12:05 AM <incogcyberpunk@...ton.me> wrote:
>
> I can confirm that reverting the commit `Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()` with the following commit details , solves this regression that has been present in both the stable and the mainline kernels since 6.13.2
>
> Commit Details:
> - Title: Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()
> - commit id: 4194766ec8756f4f654d595ae49962acbac49490
> - [ Upstream commit e9087e828827e5a5c85e124ce77503f2b81c3491 ]
> - Author: Douglas Anderson <dianders@...omium.org>
> - Date: Wed Jan 15 19:36:36 2025 -0800
>
> Reverting the above mentioned commit and building the latest mainline kernel without the trouble-causing commit fixes the issue and the bluetooth adapter now is properly recognized and bluetooth works flawlessly.
Hopefully fixed by this commit:
https://lore.kernel.org/r/20251119085354.1.I1ae7aebc967e52c7c4be7aa65fbd81736649568a@changeid
Can you confirm and add your Tested-by in response to that patch if it works?
-Doug
Powered by blists - more mailing lists