TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter. About a week ago a regression was reported to bugzilla.kernel.org that seems to be handled there already, nevertheless I'd like to add to the tracking to ensure it's not forgotten. #regzbot introduced: v5.16..v5.17 #regzbot from: Winston Wu <winstonwu91@xxxxxxxxx> #regzbot title: net: bluetooth: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215725 Quote: On 22.03.22 14:38, bugzilla-daemon@xxxxxxxxxx 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 > Product: Drivers > Version: 2.5 > Kernel Version: 5.17 > Hardware: Intel > OS: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Bluetooth > Assignee: linux-bluetooth@xxxxxxxxxxxxxxx > Reporter: winstonwu91@xxxxxxxxx > Regression: No > > 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. See the ticket for details, there were a few replies already. 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.
