Bug 219211 - Bluetooth not working. Bluetooth: hci0: Opcode 0x0c03 failed: -110
Summary: Bluetooth not working. Bluetooth: hci0: Opcode 0x0c03 failed: -110
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: AMD Linux
: P3 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-29 16:56 UTC by aprilgrimoire
Modified: 2024-09-01 17:43 UTC (History)
1 user (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments
output of journalctl -b 0 (1.31 MB, text/plain)
2024-08-29 16:56 UTC, aprilgrimoire
Details
dmesg output (165.36 KB, text/plain)
2024-08-30 14:58 UTC, aprilgrimoire
Details

Description aprilgrimoire 2024-08-29 16:56:43 UTC
Created attachment 306791 [details]
output of journalctl -b 0

Bluetooth adapter not working:

(base) april@AprilGrimoire-Mechrevo ~ $ rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
(base) april@AprilGrimoire-Mechrevo ~ $ bluetoothctl 
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# list
[bluetooth]# 

I see the following error message from kernel:

[    3.545797] Bluetooth: hci0: Opcode 0x0c03 failed: -110
Comment 1 Artem S. Tashkinov 2024-08-30 06:48:56 UTC
Kernel version?

lsusb output?
Comment 2 Artem S. Tashkinov 2024-08-30 06:49:31 UTC
Full dmesg output? (attach it as a file)
Comment 3 aprilgrimoire 2024-08-30 14:55:28 UTC
(In reply to Artem S. Tashkinov from comment #1)
> Kernel version?
> 
> lsusb output?

(base) april@AprilGrimoire-Mechrevo ~ $ uname -a
Linux AprilGrimoire-Mechrevo 6.6.38-ubuntu #4 SMP PREEMPT_DYNAMIC Mon Aug 12 19:08:07 CST 2024 x86_64 AMD Ryzen 7 8845H w/ Radeon 780M Graphics AuthenticAMD GNU/Linux
(base) april@AprilGrimoire-Mechrevo ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 2b7e:b663 SunplusIT Inc HD Webcam
Bus 001 Device 003: ID 13d3:3585 IMC Networks Wireless_Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 007 Device 003: ID 24ae:187b Shenzhen Rapoo Technology Co., Ltd. Rapoo 2.4G Wireless Device
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Comment 4 aprilgrimoire 2024-08-30 14:57:31 UTC
(In reply to Artem S. Tashkinov from comment #1)
> Kernel version?
> 
> lsusb output?

Sorry the correct kernel version is

(base) april@AprilGrimoire-Mechrevo ~ $ uname -a
Linux AprilGrimoire-Mechrevo 6.10.4-gentoo #7 SMP PREEMPT_DYNAMIC Fri Aug 30 00:01:45 CST 2024 x86_64 AMD Ryzen 7 8845H w/ Radeon 780M Graphics AuthenticAMD GNU/Linux

I tried this on multiple kernel versions, and all of them didn't work.
Comment 5 aprilgrimoire 2024-08-30 14:58:34 UTC
Created attachment 306797 [details]
dmesg output
Comment 6 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-09-01 09:39:32 UTC
Did BT work in earlier kernels?
Comment 7 aprilgrimoire 2024-09-01 17:23:35 UTC
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #6)
> Did BT work in earlier kernels?

I tried as early as 6.6, and it didn't work. Should I try older ones?
Comment 8 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-09-01 17:43:15 UTC
(In reply to aprilgrimoire from comment #7)
> I tried as early as 6.6, and it didn't work. Should I try older ones?

thx. And no, then this is unlikely to be a regression (and thus nothing for me).

But FWIW: if you do not get any reaction from the maintainers here[1], mail them (see MAINTAINERS file in the kernel sources) with the bluetooth list in CC.

[1] https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/#you-submitted-the-report-to-the-wrong-place-bugzillakernelorg-can-be-one

Note You need to log in before you can comment on or make changes to this bug.