From: Marcel Holtmann <marcel@holtmann.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: regressions@lists.linux.dev, stable <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: Re: regression: Bluetooth interface broken on systems with Mediatek CPU
Date: Mon, 9 Aug 2021 15:26:18 +0200 [thread overview]
Message-ID: <7621B196-B25E-475C-8D6E-AE6CFDFF8183@holtmann.org> (raw)
In-Reply-To: <a9cd03da-b816-eed3-7e77-d539924cbe88@roeck-us.net>
Hi Guenter,
> [ Greg asked me to submit a report to regressions@, so here it is. ]
>
> The following error was observed on Chromebooks with MT8183 CPU
> (ASUS Chromebook Detachable CM3, HP Chromebook 11a, and others):
>
> [ 224.735198] Bluetooth: qca_setup() hci0: setting up ROME/QCA6390
> [ 225.205024] Bluetooth: qca_read_soc_version() hci0: QCA Product ID :0x00000008
> [ 225.205040] Bluetooth: qca_read_soc_version() hci0: QCA SOC Version :0x00000044
> [ 225.205045] Bluetooth: qca_read_soc_version() hci0: QCA ROM Version :0x00000302
> [ 225.205049] Bluetooth: qca_read_soc_version() hci0: QCA Patch Version:0x000003e8
> [ 225.205055] Bluetooth: qca_uart_setup() hci0: QCA controller version 0x00440302
> [ 225.205061] Bluetooth: qca_download_firmware() hci0: QCA Downloading qca/rampatch_00440302.bin
> [ 227.252653] Bluetooth: hci_cmd_timeout() hci0: command 0xfc00 tx timeout
> ...
> [ 223.604971] Bluetooth: qca_recv() hci0: Frame reassembly failed (-84)
> [ 223.605027] Bluetooth: qca_recv() hci0: Frame reassembly failed (-84)
> (repeated several times)
> ...
>
> The Bluetooth interface on those Chromebooks can not be enabled.
>
> Bisect suggests that upstream commit 0ea9fd001a14 ("Bluetooth: Shutdown
> controller after workqueues are flushed or cancelled") introduced the problem.
> Reverting it fixes the problem.
>
> The problem was also reported at [1] on a Mediatek Pumpkin board.
>
> As of this writing, the problem is still present in the upstream kernel
> as well as in all stable releases which include commit 0ea9fd001a14.
post it to the linux-bluetooth@vger mailing list. This is Qualcomm driver
specific and maybe they broke something. However there is an ongoing
discussion about your bi-sected commit regarding Mediatek Bluetooth device
where this seems to also have caused a problem.
Regards
Marcel
prev parent reply other threads:[~2021-08-09 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 22:21 regression: Bluetooth interface broken on systems with Mediatek CPU Guenter Roeck
2021-08-09 2:35 ` Kai-Heng Feng
2021-08-09 4:10 ` Guenter Roeck
2021-08-09 4:48 ` Kai-Heng Feng
2021-08-09 19:18 ` Guenter Roeck
2021-08-09 13:26 ` Marcel Holtmann [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=7621B196-B25E-475C-8D6E-AE6CFDFF8183@holtmann.org \
--to=marcel@holtmann.org \
--cc=gregkh@linuxfoundation.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux@roeck-us.net \
--cc=regressions@lists.linux.dev \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).