From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #forregzbot
Date: Sat, 9 Apr 2022 13:00:56 +0200 [thread overview]
Message-ID: <b6d3a868-d29f-224b-dcaf-7143fd8ce99a@leemhuis.info> (raw)
In-Reply-To: <bug-215725-62941@https.bugzilla.kernel.org/>
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@gmail.com>
#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@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
> 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@vger.kernel.org
> Reporter: winstonwu91@gmail.com
> 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.
next prev parent reply other threads:[~2022-04-09 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:38 [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure bugzilla-daemon
2022-03-29 8:01 ` Thorsten Leemhuis
2022-03-29 8:01 ` [Bug 215725] " bugzilla-daemon
2022-03-29 21:04 ` bugzilla-daemon
2022-04-09 11:00 ` Thorsten Leemhuis [this message]
2022-05-04 13:12 ` bugzilla-daemon
2022-05-04 14:21 ` bugzilla-daemon
2022-10-03 10:54 ` bugzilla-daemon
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=b6d3a868-d29f-224b-dcaf-7143fd8ce99a@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).