regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Bug 215576] New: HSP/HFP mSBC profile broken with QCA6174 #forregzbot
Date: Sun, 10 Apr 2022 10:56:50 +0200	[thread overview]
Message-ID: <0cfc124d-9540-9f55-81a0-67b73dce0528@leemhuis.info> (raw)
In-Reply-To: <efcf48d3-5a11-5f20-a27a-6fbe2acc5e2f@leemhuis.info>

On 07.03.22 12:24, Thorsten Leemhuis wrote:
> 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.

#regzbot monitor:
https://lore.kernel.org/all/20220401233826.122544-1-luiz.dentz@gmail.com/
#regzbot fixed-by: 38a1944deda4d9


> On 08.02.22 07:49, Thorsten Leemhuis wrote:
>> [TLDR: I'm adding the regression report below to regzbot, the Linux
>> kernel regression tracking bot; all text you find below is compiled from
>> a few templates paragraphs you might have encountered already already
>> from similar mails.]
>>
>> Hi, this is your Linux kernel regression tracker speaking.
>>
>> CCing the regression mailing list, as it should be in the loop for all
>> regressions, as explained here:
>> https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
>>
>> On 07.02.22 19:00, bugzilla-daemon@kernel.org wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=215576
>>>
>>>             Bug ID: 215576
>>>            Summary: HSP/HFP mSBC profile broken with QCA6174
>>>            Product: Drivers
>>>            Version: 2.5
>>>     Kernel Version: 5.16.7
>>>           Hardware: x86-64
>>>                 OS: Linux
>>>               Tree: Mainline
>>>             Status: NEW
>>>           Severity: normal
>>>           Priority: P1
>>>          Component: Bluetooth
>>>           Assignee: linux-bluetooth@vger.kernel.org
>>>           Reporter: mike@mjones.io
>>>         Regression: No
>>>
>>> Created attachment 300405
>>>   --> https://bugzilla.kernel.org/attachment.cgi?id=300405&action=edit
>>> dmesg with 5.16.7
>>>
>>> Between v5.15 and v5.16, mSBC via pipewire stopped working with the QCA6174
>>> adapter.
>>>
>>> Switching to the HSP/HFP profile with mSBC codec in pipewire produces a loud
>>> buzzing sound, and the microphone does not function. When using PulseAudio
>>> instead of pipewire, the buzzing is absent but audio input/output also don't
>>> work.
>>>
>>> Other users are reporting the same issue at [1].
>>>
>>> I ran a git bisect between these two versions and the issue seems to have been
>>> caused by this commit:
>>>
>>> [b2af264ad3af437238c9500aa830ebcafb180e05] Bluetooth: Add support for
>>> HCI_Enhanced_Setup_Synchronous_Connection command
>>>
>>> [1] https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2019
>>
>> To be sure this issue doesn't fall through the cracks unnoticed, I'm
>> adding it to regzbot, my Linux kernel regression tracking bot:
>>
>> #regzbot ^introduced b2af264ad3af437238c9500aa830ebcafb180e05
>> #regzbot title bluetooth: HSP/HFP mSBC profile broken with QCA6174
>> #regzbot ignore-activity
>> #regzbot link https://bugzilla.kernel.org/show_bug.cgi?id=215576
>>
>> Reminder for developers: when fixing the issue, please add a 'Link:'
>> tags pointing to the report (the mail quoted above) using
>> lore.kernel.org/r/, as explained in
>> 'Documentation/process/submitting-patches.rst' and
>> 'Documentation/process/5.Posting.rst'. This allows the bot to connect
>> the report with any patches posted or committed to fix the issue; this
>> again allows the bot to show the current status of regressions and
>> automatically resolve the issue when the fix hits the right tree.
>>
>> I'm sending this to everyone that got the initial report, to make them
>> aware of the tracking. I also hope that messages like this motivate
>> people to directly get at least the regression mailing list and ideally
>> even regzbot involved when dealing with regressions, as messages like
>> this wouldn't be needed then.
>>
>> Don't worry, I'll send further messages wrt to this regression just to
>> the lists (with a tag in the subject so people can filter them away), if
>> they are relevant just for regzbot. With a bit of luck no such messages
>> will be needed anyway.
>>
>> 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.
>>

  reply	other threads:[~2022-04-10  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-215576-62941@https.bugzilla.kernel.org/>
2022-02-08  6:49 ` [Bug 215576] New: HSP/HFP mSBC profile broken with QCA6174 Thorsten Leemhuis
2022-03-07 11:24   ` [Bug 215576] New: HSP/HFP mSBC profile broken with QCA6174 #forregzbot Thorsten Leemhuis
2022-04-10  8:56     ` Thorsten Leemhuis [this message]
2022-05-30 10:38       ` 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=0cfc124d-9540-9f55-81a0-67b73dce0528@leemhuis.info \
    --to=regressions@leemhuis.info \
    --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).