From: Chris Clayton <chris2553@googlemail.com>
To: 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: Fri, 31 Dec 2021 06:21:47 +0000 [thread overview]
Message-ID: <50ea1b0e-28d7-6d04-9c03-4becc4db143b@googlemail.com> (raw)
In-Reply-To: <02077a37-46d6-c94f-fa08-9da7ee99e42c@googlemail.com>
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.
> A full dmesg log is attached. I've also attached Two files containing the output from "lsusb -v" run on 5.10.89 and
> 5.16-rc7.
>
> Please let me know if I can provide any other diagnostic information or test any patches. You'll need to cc me on
> replies because I'm not subscribed to LKML or linux-bluetooth.
>
> Thanks
next prev parent reply other threads:[~2021-12-31 6:21 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 [this message]
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
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=50ea1b0e-28d7-6d04-9c03-4becc4db143b@googlemail.com \
--to=chris2553@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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