From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Regression: Inoperative bluetooth, Intel chipset, mainline kernel 6.6.2+
Date: Thu, 30 Nov 2023 20:54:09 -0500 [thread overview]
Message-ID: <ee109942-ef8e-45b9-8cb9-a98a787fe094@moonlit-rail.com> (raw)
Greetings -
With mainline kernel 6.6.2+ (and 6.1.63, etc), bluetooth is inoperative
(reports "opcode 0x0c03 failed") on my motherboard's bluetooth adapter
(Intel chipset). Details below.
I reported this in a comment tacked onto bugzilla #218142, but got no
response, so posting here as a possibly new issue.
Details, original email:
----------------------------------------------------------------------
I have a regression going from mainline kernel 6.1.62 to 6.1.63, and
also from kernel 6.6.1 to 6.6.2; I can bisect if patch authors can't
locate the relevant commit. In the most recent kernels mentioned,
bluetooth won't function.
Hardware: ASRock "X470 Taichi" motherboard - on board chipset.
lsusb: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth.
dmesg: Bluetooth: hci0: Legacy ROM 2.x revision 5.0 build 25 week 20 2015
Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
Bluetooth: hci0: Intel BT fw patch 0x43 completed & activated
bluez: Version 5.70, bluez firmware version 1.2
Linux kernel firmware: 20231117_7124ce3
On a working kernel (such as 6.6.1), in addition to the dmesg output
above, we have this:
dmesg: Bluetooth: MGMT ver 1.22
Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
On a failed kernel (such as 6.6.2), instead of the good output above, we
have:
dmesg: Bluetooth: hci0: Opcode 0x0c03 failed: -110
Bluetooth: hci0: Opcode 0x0c03 failed: -110
...
repeats several times as bluez attempts to communicate with hci0.
----------------------------------------------------------------------
Since that email was sent, kernel firmware has been updated to
20231128_aae6052, and kernels 6.1.64 and 6.6.3 have been tried with no
change observed.
Kris
next reply other threads:[~2023-12-01 2:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 1:54 Kris Karas (Bug Reporting) [this message]
2023-12-01 6:27 ` Regression: Inoperative bluetooth, Intel chipset, mainline kernel 6.6.2+ Bagas Sanjaya
2023-12-01 8:19 ` Kris Karas (Bug Reporting)
2023-12-01 8:27 ` Paul Menzel
2023-12-03 12:17 ` Oleksandr Natalenko
2023-12-03 18:46 ` Kris Karas (Bug Reporting)
2023-12-01 6:33 ` Thorsten Leemhuis
2023-12-01 8:15 ` Greg KH
2023-12-02 6:43 ` Kris Karas (Bug Reporting)
2023-12-02 7:23 ` Paul Menzel
2023-12-02 7:50 ` Greg KH
2023-12-02 7:58 ` Kris Karas (Bug Reporting)
2023-12-02 8:15 ` Greg KH
2023-12-03 8:32 ` Kris Karas (Bug Reporting)
2023-12-03 8:38 ` Greg KH
2023-12-03 16:16 ` Basavaraj Natikar
2023-12-03 16:24 ` Basavaraj Natikar
2023-12-03 19:52 ` Oleksandr Natalenko
2023-12-04 9:12 ` Mathias Nyman
2023-12-04 10:08 ` [PATCH 1/2] Revert "xhci: Enable RPM on controllers that support low-power states" Mathias Nyman
2023-12-04 10:08 ` [PATCH 2/2] Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1" Mathias Nyman
2023-12-04 10:14 ` [1/2] Revert "xhci: Enable RPM on controllers that support low-power states" bluez.test.bot
2023-12-04 10:49 ` [PATCH 1/2] " Basavaraj Natikar
2023-12-04 14:22 ` Mathias Nyman
2023-12-04 14:49 ` Basavaraj Natikar
2023-12-04 15:06 ` Mathias Nyman
2023-12-04 15:29 ` Basavaraj Natikar
2023-12-04 23:55 ` Greg KH
2023-12-05 9:05 ` [PATCH v2] Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1" Mathias Nyman
2023-12-05 9:13 ` [v2] " bluez.test.bot
2023-12-05 18:36 ` [PATCH v2] " Mario Limonciello
2023-12-15 16:53 ` patchwork-bot+bluetooth
2023-12-15 16:53 ` [PATCH 1/2] Revert "xhci: Enable RPM on controllers that support low-power states" patchwork-bot+bluetooth
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=ee109942-ef8e-45b9-8cb9-a98a787fe094@moonlit-rail.com \
--to=bugs-a21@moonlit-rail.com \
--cc=linux-bluetooth@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).