Bug 215725
| Summary: | Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Winston Wu (winstonwu91) |
| Component: | Bluetooth | Assignee: | linux-bluetooth (linux-bluetooth) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | luiz.dentz, pmenzel+bugzilla.kernel.org, regressions |
| Priority: | P1 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| Kernel Version: | 5.17 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
|
Description
Winston Wu
2022-03-22 13:38:15 UTC
Hi, this is your Linux kernel regression tracker. On 22.03.22 14:38, bugzilla-daemon@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=215725 > > Bug ID: 215725 > Summary: Basilisk X Hyperspeed Bluetooth LE mouse fail to > connect under 5.17 with Opcode 0x2043 failure Hey bluetooth maintainers, what's up here? That's a report about a regression that was submitted more than a week ago. Has anything happened to get it fixed? Reminder: this ideally should be fixed in 5.17.y before 5.16.y becomes EOL, which I guess will happen in round about two or three weeks from now. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them and lack knowledge about most of the areas they concern. I thus unfortunately will sometimes get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight. (In reply to Winston Wu from comment #0) > I am using AX201 wireless card (lsusb shows Bus 001 Device 004: ID 8087:0026 > Intel Corp. AX201 Bluetooth) and the mouse stopped working with bluetooth > mode under 5.17. 5.16 does not have such problem. Could you please attach the HCI trace using btmon -w? (In reply to Luiz Von Dentz from comment #2) > (In reply to Winston Wu from comment #0) > > I am using AX201 wireless card (lsusb shows Bus 001 Device 004: ID > 8087:0026 > > Intel Corp. AX201 Bluetooth) and the mouse stopped working with bluetooth > > mode under 5.17. 5.16 does not have such problem. > > Could you please attach the HCI trace using btmon -w? Winston Wu, did you miss this, are you having trouble with this, or what's the status here? Hi it seems that the problem no longer presents after 5.17.3 or so…
> 在 2022年5月4日，上午9:12，bugzilla-daemon@kernel.org 写道：
>
> https://bugzilla.kernel.org/show_bug.cgi?id=215725
>
> The Linux kernel's regression tracker (Thorsten Leemhuis)
> (regressions@leemhuis.info) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |regressions@leemhuis.info
>
> --- Comment #3 from The Linux kernel's regression tracker (Thorsten Leemhuis)
> (regressions@leemhuis.info) ---
> (In reply to Luiz Von Dentz from comment #2)
>> (In reply to Winston Wu from comment #0)
>>> I am using AX201 wireless card (lsusb shows Bus 001 Device 004: ID
>> 8087:0026
>>> Intel Corp. AX201 Bluetooth) and the mouse stopped working with bluetooth
>>> mode under 5.17. 5.16 does not have such problem.
>>
>> Could you please attach the HCI trace using btmon -w?
>
> Winston Wu, did you miss this, are you having trouble with this, or what's
> the
> status here?
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You reported the bug.
(In reply to Winston Wu from comment #4) > Hi it seems that the problem no longer presents after 5.17.3 or so… Thank you for reporting back. If you have time, it’d be great if you could figure out the exact commit. Otherwise, it’d be great if you closed the issue/bug report. PS: If you reply via email, please do not quote/cite the original email, as the quote is not hidden in the Bugzilla comment, making it hard to read. |