All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: "K, Kiran" <kiran.k@intel.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: 5.16.0-rc7+ Bluetooth error
Date: Mon, 3 Jan 2022 13:35:23 +0000	[thread overview]
Message-ID: <b583dc48-a6b6-f6c7-4a5a-678d985ce358@googlemail.com> (raw)
In-Reply-To: <DM8PR11MB55735DD3A1EA9132E1A71733F5499@DM8PR11MB5573.namprd11.prod.outlook.com>



On 03/01/2022 09:55, K, Kiran wrote:
> Hi Luiz, Chris,
> 
>> -----Original Message-----
>> From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
>> Sent: Saturday, January 1, 2022 1:23 AM
>> To: Chris Clayton <chris2553@googlemail.com>
>> Cc: LKML <linux-kernel@vger.kernel.org>; linux-bluetooth@vger.kernel.org;
>> K, Kiran <kiran.k@intel.com>
>> Subject: Re: 5.16.0-rc7+ Bluetooth error
>>
>> Hi Chris,
>>
>> On Fri, Dec 31, 2021 at 2:35 AM Chris Clayton <chris2553@googlemail.com>
>> wrote:
>>>
>>> On 30/12/2021 09:21, Chris Clayton wrote:
>>>> Hi,
>>>>
>>>> I pulled the latest changes into my clone of Linus' tree and built
>>>> and installed the kernel. (git describe gives
>>>> v5.16-rc7-9-ge7c124bd0463). I'm seeing errors reported by the
>>>> bluetooth subsystem that i don't see in 5.15.12 or 5.10.89
>>>>
>>>> The problem seems to occur twice during system startup and on each
>> occasion I see a batch of identical error messages:
>>>>
>>>> [    3.980822] Bluetooth: hci0: Failed to read codec capabilities (-56)
>>>> [    3.982812] Bluetooth: hci0: Failed to read codec capabilities (-56)
>>>> [    3.984812] Bluetooth: hci0: Failed to read codec capabilities (-56)
>>>> [    3.986608] Bluetooth: hci0: Failed to read codec capabilities (-56)
>>>> [    3.987621] Bluetooth: hci0: Failed to read codec capabilities (-56)
>>>> [    3.988606] Bluetooth: hci0: Failed to read codec capabilities (-56)
>>>> [    3.989650] Bluetooth: hci0: Failed to read codec capabilities (-56)
>>>>
>>>
>>> Sorry, I should have said that despite the above errors, my bluetooth
>> devices still work fine.
>>
>> Would be great to have the HCI trace (btmon).
>>
>> @Kiran K Is this to be expected?
> 
> May be the BT controller here is not supporting HCI_READ_CODEC_CAPABILITIES command.
> 
> This has been fixed - https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=107fe0482b549a0e43a971e5fd104719c6e495ef
> 

I've applied the patch to 5.16.0-rc8 and the error messages are no longer produced. My bluetooth devices are stiil working.

Tested-By: Chris Clayton <chris2553@googlemail.com>

> A check has been added to read codec capabilities only if supported.
> 
> Thanks,
> Kiran
> 

      reply	other threads:[~2022-01-03 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30  9:21 5.16.0-rc7+ Bluetooth error Chris Clayton
2021-12-31  6:21 ` Chris Clayton
2021-12-31 19:53   ` Luiz Augusto von Dentz
2022-01-01 11:03     ` Chris Clayton
2022-01-01 13:20       ` Chris Clayton
2022-01-03  9:55     ` K, Kiran
2022-01-03 13:35       ` Chris Clayton [this message]

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=b583dc48-a6b6-f6c7-4a5a-678d985ce358@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.