From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Jack <ostroffjh@users.sourceforge.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable again with kernel 6.0
Date: Tue, 25 Oct 2022 09:02:49 +0200 [thread overview]
Message-ID: <ab082d3c-9ba6-b1bd-a895-65ea58cec926@molgen.mpg.de> (raw)
In-Reply-To: <RJ4W7HKW.X5Y4H63W.RFY63IY6@7AFBARQQ.HKEIB7DO.6ME2HPJY>
Dear Jack,
Thank you for your work on this driver.
Am 24.10.22 um 23:11 schrieb Jack:
> Cheap USB BT dongles that are bad clones of CSR "ID 0a12:0001 Cambridge
> Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" have had historic
> problems, due to various bad behaviors. See [Bug 60824]
> [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle
> unusable (https://bugzilla.kernel.org/show_bug.cgi) for more details and
> background. The patch in that bug was initially mainlined in 5.9, and
> underwent several revisions since then. It has continued to work
> through all of the 5.19 series, but it does not work with any of the 6.0
> kernels.
>
> I have made three unsuccessful attempts to git bisect using vanilla
> sources. All settled on totally irrelevant commits. These have all
> used v6.0-rc1 and v5.19 as the starting bad and good commits.
Thank you for trying to bisect the issue. Too bad, it’s inconclusive.
Did you or can you please test the commits below, relating to the merges
of the Bluetooth trees.
1. b8c3bf0ed2edf2deaedba5f0bf0bb54c76dee71d
2. 1d1ab5d39be7590bb2400418877bff43da9e75ec
3. 2e64fe4624d19bc71212aae434c54874e5c49c5a
4. 4a934eca7b39df35569f97a070701d6846ce46df
5. 14202eff214e1e941fefa0366d4c3bc4b1a0d500
6. c69ecb0ea4c96b8b191cbaa0b420222a37867655
7. 6e0e846ee2ab01bc44254e6a0a6a6a0db1cba16d
8. 5588d628027092e66195097bdf6835ddf64418b3
> Having read all the pages on filing a [REGRESSION} bug, I'm a bit
> intimidated to file something without sufficient information to be taken
> seriously, but will do so using this information, if that seems the best
> course of action.
Having the regression documented is the most important thing, and it
will be taken seriously even if the reporter has not fully analyzed or
solved it.
[…]
Kind regards,
Paul
next prev parent reply other threads:[~2022-10-25 7:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 21:11 [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable again with kernel 6.0 Jack
2022-10-25 7:02 ` Paul Menzel [this message]
2022-10-25 18:00 ` Jack
2022-10-25 19:38 ` Luiz Augusto von Dentz
2022-10-26 3:41 ` quic_zijuhu
2022-10-27 9:48 ` quic_zijuhu
2022-11-09 19:12 ` [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle Swyter
2022-11-09 19:40 ` Jack
2022-11-09 20:43 ` Luiz Augusto von Dentz
2022-11-09 21:14 ` Swyter
2022-11-15 6:20 ` Mika Laitio
2022-11-15 6:41 ` Swyter
2022-10-26 9:17 ` [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable again with kernel 6.0 #forregzbot Thorsten Leemhuis
2022-12-01 14:41 ` Thorsten Leemhuis
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=ab082d3c-9ba6-b1bd-a895-65ea58cec926@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ostroffjh@users.sourceforge.net \
/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).