From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218142] Bluetooth adapter fails to recognize on kernel 5.15.0-88-generic
Date: Tue, 21 Nov 2023 01:15:03 +0000 [thread overview]
Message-ID: <bug-218142-62941-W4Bx7AgMkT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218142-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218142
Kris Karas (bugs-a21@moonlit-rail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugs-a21@moonlit-rail.com
--- Comment #2 from Kris Karas (bugs-a21@moonlit-rail.com) ---
Given Artem mentioned 6.6.1 in comment 1, this bug might apply to me as well.
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.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-11-21 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-218142-62941@https.bugzilla.kernel.org/>
2023-11-14 5:50 ` [Bug 218142] Bluetooth adapter fails to recognize on kernel 5.15.0-88-generic bugzilla-daemon
2023-11-21 1:15 ` bugzilla-daemon [this message]
2023-12-02 7:13 ` bugzilla-daemon
2023-12-02 7:29 ` bugzilla-daemon
2023-12-02 18:47 ` bugzilla-daemon
2023-12-02 18:47 ` bugzilla-daemon
2023-12-03 12:20 ` bugzilla-daemon
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=bug-218142-62941-W4Bx7AgMkT@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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).