[btintel] Bluetooth crashes in Ubuntu 23.04

[Phil Buckley]

Bluetooth stops working.
Mouse (logitech M720) stopped mid scroll. Never had any problems with this mouse under Ubuntu before.

Workaround:
Reboot fixes the problem.
Switching in and out of airplane mode gets bluetooth working again

Frequency:
Second time this has happened since upgrade from 22.10 (about 2 weeks ago)

Limited knowledge fault tracing:

>sudo systemctl restart bluetooth
doesn't make any difference

>rfkill
shows no bluetooth device

>lspci
...
3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
...

Ubuntu settings - show bluetooth is off, but I didn't disable it and it can't be re-enabled.

So I assume the driver has crashed, but I don't know how to find out more about this. Could collect some more info next time it happens if someone tells me what to do.

>lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.04
Release: 23.04

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2019152/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Daniel van Vugt (vanvugt)]

Next time the problem happens, before rebooting please run:

  journalctl -b0 > journal.txt

or after rebooting:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

[Phil Buckley (pbuckley)]

I've attached the journal.txt as requested.

One more point to add - enabling/disabling flight mode within Ubuntu does not resolve the problem; but if I enable/disable on the laptop (there's a key sequence on this Entroware Apollo) then it gets Bluetooth working again. This might suggest that resetting the hardware is necessary to resolve which might indicate that the linux bluetooth support has crashed the silicon.

[Daniel van Vugt (vanvugt)]

Indeed it appears to be a kernel/hardware problem:

May 18 11:26:13 phil-Apollo kernel: Bluetooth: hci0: Hardware error 0x0c
May 18 11:26:13 phil-Apollo kernel: Bluetooth: hci0: command 0x0c1a tx timeout
May 18 11:26:13 phil-Apollo kernel: Bluetooth: hci0: Opcode 0x c1a failed: -110
May 18 11:26:13 phil-Apollo systemd-sleep[440195]: System returned from sleep state.
May 18 11:26:13 phil-Apollo bluetoothd[625]: Controller resume with wake event 0x0
May 18 11:26:13 phil-Apollo kernel: PM: suspend exit
May 18 11:26:13 phil-Apollo kernel: BUG: kernel NULL pointer dereference, address: 0000000000000070
May 18 11:26:13 phil-Apollo kernel: #PF: supervisor read access in kernel mode
May 18 11:26:13 phil-Apollo kernel: #PF: error_code(0x0000) - not-present page
May 18 11:26:13 phil-Apollo kernel: PGD 0 P4D 0
May 18 11:26:13 phil-Apollo kernel: Oops: 0000 [#1] PREEMPT SMP PTI
May 18 11:26:13 phil-Apollo kernel: CPU: 1 PID: 437412 Comm: kworker/u17:0 Tainted: G W 6.2.0-20-generic #20-Ubuntu
May 18 11:26:13 phil-Apollo kernel: Hardware name: Entroware Apollo/Apollo, BIOS 1.05.02E 03/26/2018
May 18 11:26:13 phil-Apollo kernel: Workqueue: hci0 hci_error_reset [bluetooth]
May 18 11:26:13 phil-Apollo kernel: RIP: 0010:btintel_hw_error+0xa6/0x150 [btintel]
May 18 11:26:13 phil-Apollo kernel: Code: 89 df 41 b8 c4 09 00 00 48 8d 4d e7 ba 01 00 00 00 be 22 fc 00 00 e8 19 2d 3b 00 48 89 c3 48 3d 00 f0 ff ff 0f 87 88 00 00 00 <83> 78 70 0d 75 50 48 8b 80 d0 00 00 00 4c 89 e6 48 c7 c7 84 34 7e
May 18 11:26:13 phil-Apollo kernel: RSP: 0018:ffffb1394e23be30 EFLAGS: 00010207
May 18 11:26:13 phil-Apollo kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
May 18 11:26:13 phil-Apollo kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
May 18 11:26:13 phil-Apollo kernel: RBP: ffffb1394e23be50 R08: 0000000000000000 R09: 0000000000000000
May 18 11:26:13 phil-Apollo kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff9320b2e14030
May 18 11:26:13 phil-Apollo kernel: R13: 0000000000000000 R14: ffff9320b2e14730 R15: ffff9321fea253c0
May 18 11:26:13 phil-Apollo kernel: FS: 0000000000000000(0000) GS:ffff9322f6c40000(0000) knlGS:0000000000000000
May 18 11:26:13 phil-Apollo kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 18 11:26:13 phil-Apollo kernel: CR2: 0000000000000070 CR3: 0000000046410003 CR4: 00000000003706e0
May 18 11:26:13 phil-Apollo kernel: Call Trace:
May 18 11:26:13 phil-Apollo kernel: <TASK>
May 18 11:26:13 phil-Apollo kernel: hci_error_reset+0x32/0xa0 [bluetooth]
May 18 11:26:13 phil-Apollo kernel: process_one_work+0x222/0x430
May 18 11:26:13 phil-Apollo kernel: worker_thread+0x50/0x3e0
May 18 11:26:13 phil-Apollo kernel: ? __pfx_worker_thread+0x10/0x10
May 18 11:26:13 phil-Apollo kernel: kthread+0xe6/0x110
May 18 11:26:13 phil-Apollo kernel: ? __pfx_kthread+0x10/0x10
May 18 11:26:13 phil-Apollo kernel: ret_from_fork+0x29/0x50
May 18 11:26:13 phil-Apollo kernel: </TASK>

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2019152

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Jonathan Terry (sojourn7)]

Having a similar experience in 23.10 with 6.5.0-12 thru 6.5.0-14 generic kernels.

❯ uname -a; lsb_release -a
Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic

2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c
2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception info failed (-16)
2023-12-06T16:03:58,984885-06:00 iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
2023-12-06T16:03:58,985010-06:00 iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
2023-12-06T16:03:58,985014-06:00 iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
2023-12-06T16:03:58,985018-06:00 iwlwifi 0000:00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode
2023-12-06T16:03:58,985021-06:00 iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
2023-12-06T16:03:58,985025-06:00 iwlwifi 0000:00:14.3: 0x000002F0 | trm_hw_status0
2023-12-06T16:03:58,985027-06:00 iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
2023-12-06T16:03:58,985029-06:00 iwlwifi 0000:00:14.3: 0x004DB338 | branchlink2
2023-12-06T16:03:58,985032-06:00 iwlwifi 0000:00:14.3: 0x004D119A | interruptlink1
2023-12-06T16:03:58,985034-06:00 iwlwifi 0000:00:14.3: 0x004D119A | interruptlink2
2023-12-06T16:03:58,985036-06:00 iwlwifi 0000:00:14.3: 0x000157E2 | data1
2023-12-06T16:03:58,985038-06:00 iwlwifi 0000:00:14.3: 0x00000010 | data2
2023-12-06T16:03:58,985040-06:00 iwlwifi 0000:00:14.3: 0x00000000 | data3
2023-12-06T16:03:58,985042-06:00 iwlwifi 0000:00:14.3: 0xCDC0BA9E | beacon time
2023-12-06T16:03:58,985044-06:00 iwlwifi 0000:00:14.3: 0x7C09EDE4 | tsf low
2023-12-06T16:03:58,985046-06:00 iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
2023-12-06T16:03:58,985048-06:00 iwlwifi 0000:00:14.3: 0x00000000 | time gp1
2023-12-06T16:03:58,985050-06:00 iwlwifi 0000:00:14.3: 0x7C0B338A | time gp2
2023-12-06T16:03:58,985052-06:00 iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
2023-12-06T16:03:58,985054-06:00 iwlwifi 0000:00:14.3: 0x00000053 | uCode version major
2023-12-06T16:03:58,985056-06:00 iwlwifi 0000:00:14.3: 0xE8F84E98 | uCode version minor
2023-12-06T16:03:58,985058-06:00 iwlwifi 0000:00:14.3: 0x00000370 | hw version
2023-12-06T16:03:58,985060-06:00 iwlwifi 0000:00:14.3: 0x00480002 | board version
2023-12-06T16:03:58,985062-06:00 iwlwifi 0000:00:14.3: 0x8096FD26 | hcmd
2023-12-06T16:03:58,985064-06:00 iwlwifi 0000:00:14.3: 0x00020000 | isr0
2023-12-06T16:03:58,985066-06:00 iwlwifi 0000:00:14.3: 0x00000000 | isr1
2023-12-06T16:03:58,985068-06:00 iwlwifi 0000:00:14.3: 0x48F04802 | isr2
2023-12-06T16:03:58,985069-06:00 iwlwifi 0000:00:14.3: 0x00C3000C | isr3
2023-12-06T16:03:58,985071-06:00 iwlwifi 0000:00:14.3: 0x00000000 | isr4
2023-12-06T16:03:58,985073-06:00 iwlwifi 0000:00:14.3: 0x00B40103 | last cmd Id
2023-12-06T16:03:58,985075-06:00 iwlwifi 0000:00:14.3: 0x000157E2 | wait_event
2023-12-06T16:03:58,985077-06:00 iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
2023-12-06T16:03:58,985079-06:00 iwlwifi 0000:00:14.3...

[Phil Buckley (pbuckley)]

I tried updating to a later kernel -- now running 6.6.1 and the problem has gone away.