Intel 8087:07dc Bluetooth highly unreliable

[Rijnhard Hessel]

I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21.

* adapter failing to power on after suspend/resume
* random errors littering dmesg
* now it went ballistic and caused my UI to freeze, not from anything I could identify that I did.

inxi -EbA

System:
  Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
    Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
Machine:
  Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
    serial: <superuser required>
  Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: <superuser required>
    UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
CPU:
  Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
    min/max: 800/3500
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    driver: snd_hda_intel
  Device-2: Intel 8 Series/C220 Series High Definition Audio
    driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: 30:3A:64:EA:9C:EA

attached kernel logs

[iam (iam-linux-kernel-bugs)]

I have Intel Corporation Wireless 7260 (rev 73) with 8087:07dc Intel Corp. Bluetooth module.
From time to time, pausing and playing audio over A2DP causes Bluetooth stack to stall with the following in kernel log:

Bluetooth: hci0: command 0x041f tx timeout
Bluetooth: hci0: command 0x0406 tx timeout
Bluetooth: hci0: command 0x0c03 tx timeout
Bluetooth: hci0: HCI reset during shutdown failed
Bluetooth: hci0: urb 0000000044e22bee failed to resubmit (113)
Bluetooth: hci0: urb 00000000fc976241 failed to resubmit (113)
Bluetooth: hci0: urb 00000000a59b126a failed to resubmit (113)
Bluetooth: hci0: urb 00000000215e997b failed to resubmit (113)

Note that "HCI reset during shutdown failed" happened when I tried to disable Bluetooth and enable it again.
Removing btusb and btintel modules and inserting them again helps.

Bluetooth: hci0: read Intel version: 370710018002030d57
Bluetooth: hci0: Intel device is already patched. patch num: 57

Kernel version: 5.0.11. Happened on 4.9-4.19 as well.
Fedora's firmware package: linux-firmware.noarch 20190416-95.fc30

[iam (iam-linux-kernel-bugs)]

The problem still occurs frequently, on a recent Linux kernel 5.5.13 and Bluetooth firmware file intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq

If anyone knows how to debug this issue and how can I provide more debug information to you, please respond.
The issue happens with many different headphones and speakers.

[tnielsen (tnielsen-linux-kernel-bugs)]

Hello I believe this is the same problem (i took out all the plasma and networkmanager messages.
In short my jabra 65t looses connection after very short audio usage (and as a bonus kills my mouse as well if i use bt mouse) The jabra headset works fine with my phone(-s)

(uname -a
Linux linux-jn76 5.6.12-1-default #1 SMP Tue May 12 17:44:12 UTC 2020 (9bff61b) x86_64 x86_64 x86_64 GNU/Linux)

May 25 12:04:49 linux-jn76 kernel: input: Jabra Elite 65t (AVRCP) as /devices/virtual/input/input33
May 25 12:04:49 linux-jn76 obexd[2100]: CONNECT(0x0), <unknown>(0xff)
May 25 12:04:49 linux-jn76 obexd[2100]: CONNECT(0x0), <unknown>(0x0)
May 25 12:04:49 linux-jn76 obexd[2100]: SETPATH(0x5), <unknown>(0xff)
May 25 12:04:49 linux-jn76 obexd[2100]: stat(/root/phonebook/): No such file or directory (2)
May 25 12:04:49 linux-jn76 obexd[2100]: SETPATH(0x5), Not Found(0x44)
May 25 12:04:49 linux-jn76 systemd-logind[1161]: Watching system buttons on /dev/input/event19 (Jabra Elite 65t (AVRCP))
May 25 12:05:51 linux-jn76 kwin_x11[1876]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4207, resource id: 2>
May 25 12:05:51 linux-jn76 kwin_x11[1876]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4235, resource id: 3>
May 25 12:06:53 linux-jn76 kio_http_cache_cleaner[6486]: QIODevice::skip (QBuffer): WriteOnly device
May 25 12:06:53 linux-jn76 kio_http_cache_cleaner[6486]: QIODevice::skip (QBuffer): WriteOnly device
May 25 12:09:14 linux-jn76 kernel: usb 2-1.3: reset full-speed USB device number 5 using ehci-pci
May 25 12:09:36 linux-jn76 kernel: usb 2-1.3: Failed to suspend device, error -32
May 25 12:09:36 linux-jn76 obexd[2100]: disconnected: Transport got disconnected
May 25 12:09:36 linux-jn76 kernel: usb 2-1.3: USB disconnect, device number 5
May 25 12:09:36 linux-jn76 kded5[1833]: bluedevil: Removed Obex session is not ours "/org/bluez/obex/server/session3"
May 25 12:09:36 linux-jn76 dbus-daemon[1119]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.22" (uid=0 pid=1764 comm="/us>
May 25 12:09:36 linux-jn76 bluetoothd[1439]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
May 25 12:09:36 linux-jn76 bluetoothd[1439]: Unable to get io data for Phone Book Access: getpeername: Transport endpoint is not connected (107)
May 25 12:09:36 linux-jn76 bluetoothd[1439]: Endpoint unregistered: sender=:1.22 path=/MediaEndpoint/A2DPSink/sbc
May 25 12:09:36 linux-jn76 bluetoothd[1439]: Endpoint unregistered: sender=:1.22 path=/MediaEndpoint/A2DPSource/sbc
May 25 12:09:36 linux-jn76 systemd[1]: Starting Load/Save RF Kill Switch Status...
May 25 12:09:36 linux-jn76 systemd[1755]: Stopped target Bluetooth.
May 25 12:09:36 linux-jn76 systemd[1]: Stopped target Bluetooth.
May 25 12:09:36 linux-jn76 systemd[1]: Started Load/Save RF Kill Switch Status.
May 25 12:09:36 linux-jn76 kernel: usb 2-1.3: new full-speed USB device number 6 using ehci-pci
May 25 12:09:36 linux-jn76 kernel: usb 2-1.3: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
May 25 12:09:36 linux-jn76 kernel: usb 2-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
M...

[me (me-linux-kernel-bugs)]

Reporting the same issue here: in my case, an Intel AX 200 chip (device: 8087:0029)

I get a whole host of the following from dmesg:

[68815.214110] Bluetooth: hci0: No way to reset. Ignoring and continuing
[68817.230103] Bluetooth: hci0: command 0x0c2d tx timeout
[68817.230105] Bluetooth: hci0: No way to reset. Ignoring and continuing
[68819.246103] Bluetooth: hci0: command 0x1405 tx timeout
[68819.246106] Bluetooth: hci0: No way to reset. Ignoring and continuing
[68821.102115] Bluetooth: hci0: HCI reset during shutdown failed
[68833.927095] Bluetooth: hci0: urb 00000000da5061f1 failed to resubmit (113)
[68843.971063] Bluetooth: hci0: urb 000000001871b752 failed to resubmit (113)
[68857.915087] Bluetooth: hci0: urb 00000000ac41a64d failed to resubmit (113)
[68901.639104] Bluetooth: hci0: urb 00000000cabd03b6 failed to resubmit (113)
[68983.475090] Bluetooth: hci0: urb 00000000586c564c failed to resubmit (113)

As with the poster above, removing btusb and btintel modules and inserting them again helps.

[me (me-linux-kernel-bugs)]

(In reply to Chris Wales from comment #3)
> Reporting the same issue here: in my case, an Intel AX 200 chip (device:
> 8087:0029)
>
> I get a whole host of the following from dmesg:
>
> [68815.214110] Bluetooth: hci0: No way to reset. Ignoring and continuing
> [68817.230103] Bluetooth: hci0: command 0x0c2d tx timeout
> [68817.230105] Bluetooth: hci0: No way to reset. Ignoring and continuing
> [68819.246103] Bluetooth: hci0: command 0x1405 tx timeout
> [68819.246106] Bluetooth: hci0: No way to reset. Ignoring and continuing
> [68821.102115] Bluetooth: hci0: HCI reset during shutdown failed
> [68833.927095] Bluetooth: hci0: urb 00000000da5061f1 failed to resubmit (113)
> [68843.971063] Bluetooth: hci0: urb 000000001871b752 failed to resubmit (113)
> [68857.915087] Bluetooth: hci0: urb 00000000ac41a64d failed to resubmit (113)
> [68901.639104] Bluetooth: hci0: urb 00000000cabd03b6 failed to resubmit (113)
> [68983.475090] Bluetooth: hci0: urb 00000000586c564c failed to resubmit (113)
>
> As with the poster above, removing btusb and btintel modules and inserting
> them again helps.

Sorry, should add - using kernel 5.4.14

[abhishekpandit (abhishekpandit-linux-kernel-bugs)]

There's a recovery mechanism via `cmd_timeout` that the btusb driver uses to recover from these issues. For Intel chipsets, this requires having a reset gpio available and listed in the ACPI/DeviceTree. From the logs above, it looks like that's not the case.

I've had some success on a QCA chipset (6174A) by just resetting the port when this happens (see https://patchwork.kernel.org/patch/11624041/)

If you don't mind patching your kernel, you could try the following and see if it helps (you will need the series I linked above as well if you're not using bluetooth-next master branch).

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 0e143c0cecf2a1..cf86104fd62018 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -511,6 +511,7 @@ struct btusb_data {
        unsigned cmd_timeout_cnt;
 };

+static void btusb_qca_cmd_timeout(struct hci_dev *hdev);
 static void btusb_intel_cmd_timeout(struct hci_dev *hdev)
 {
        struct btusb_data *data = hci_get_drvdata(hdev);
@@ -520,7 +521,8 @@ static void btusb_intel_cmd_timeout(struct hci_dev *hdev)
                return;

        if (!reset_gpio) {
- bt_dev_err(hdev, "No way to reset. Ignoring and continuing");
+ bt_dev_err(hdev, "No reset gpio. Resetting usb instead.");
+ btusb_qca_cmd_timeout(hdev);
                return;
        }

[de99like (de99like-linux-kernel-bugs)]

hi

I have the same problem with a different chipset 8087:0029

I also got a kernel backtrace

kernel: kobject_add_internal failed for hci0:256 with -EEXIST, don't try to register things with the same name in the same directory.
kernel: Bluetooth: hci0: failed to register connection device
kernel: Bluetooth: hci0: link tx timeout
kernel: Bluetooth: hci0: killing stalled connection 75:ab:d6:65:ea:56
kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
kernel: IP: klist_next+0x1c/0x100
kernel: PGD 0 P4D 0
kernel: Oops: 0000 [#1] SMP NOPTI
kernel: Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac bnep binfmt_misc dm_crypt algif_skcipher af_alg cdc_ether usbnet r8152 mii uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 btrtl btbcm videobuf2_core btintel videodev bluetooth media ecdh_generic snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch arc4 dell_laptop intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm nls_iso8859_1 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec aes_x86_64 snd_hda_core crypto_simd glue_helper snd_hwdep cryptd intel_cstate snd_pcm intel_rapl_perf iwlmvm(OE) snd_seq_midi snd_seq_midi_event dell_wmi mac80211(OE) joydev input_leds dell_smbios snd_rawmidi
kernel: serio_raw dcdbas snd_seq iwlwifi(OE) snd_seq_device snd_timer dell_wmi_descriptor wmi_bmof snd idma64 intel_wmi_thunderbolt virt_dma cfg80211(OE) soundcore rtsx_pci_ms compat(OE) memstick ucsi_acpi intel_lpss_pci intel_lpss typec_ucsi processor_thermal_device intel_soc_dts_iosf typec int3403_thermal int340x_thermal_zone intel_hid mac_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid i915 i2c_algo_bit drm_kms_helper rtsx_pci_sdmmc syscopyarea psmouse thunderbolt sysfillrect sysimgblt fb_sys_fops rtsx_pci drm wmi i2c_hid hid video
kernel: CPU: 3 PID: 17609 Comm: kworker/u17:3 Tainted: G W OE 4.15.0-1097-oem #107-Ubuntu
kernel: Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.6.0 07/07/2020
kernel: Workqueue: hci0 hci_rx_work [bluetooth]
kernel: RIP: 0010:klist_next+0x1c/0x100
kernel: RSP: 0018:ffffbf86c742fc80 EFLAGS: 00010282
kernel: RAX: 0000000000000000 RBX: ffff996fce487000 RCX: 0000000000000000
kernel: RDX: ffffffffc0f4b230 RSI: ffffbf86c742fcc0 RDI: 0000000000000000
kernel: RBP: ffffbf86c742fcb0 R08: 0000377d840d5913 R09: ffff996ffbf49818
kernel: R10: 0000000000000000 R11: 00007fe43cbf3014 R12: ffffbf86c742fcc0
kernel: R13: 0000000000000000 R14: ffff996ff532c000 R15: ffff996fce487000
kernel: FS: 0000000000000000(0000) GS:ffff99700e4c0000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 0000000000000020 CR3: 00000001a320a002 CR4: 00000000003606e0
kernel: Call Trace:
kernel: ? bt_link_release+0x20/0x20 [bluetooth]
kernel: device_find_child+0x5c/0xb0
kernel: ? bt_li...

[kalmaevlv (kalmaevlv-linux-kernel-bugs)]

hi, i am seeing the same problem. I think the reason is the automatic saving of energy.
In my case, if you use the powertop tool and carefully look at the Tunables tab, you can find Autosuspend for unknown USB device 1-1.3 (8087: 07dc)
change the state to bad and the problem no longer persists until the next system reboot.

uname -a
Linux dns-book 5.8.0-33-generic #36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

lspci
07:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

lsusb
Bus 001 Device 003: ID 8087:07dc Intel Corp.

[iam (iam-linux-kernel-bugs)]

(In reply to Leonid Kalmaev from comment #7)
> hi, i am seeing the same problem. I think the reason is the automatic saving
> of energy.

Maybe you're right. I had autosuspend disabled for this device but for unknown reason it automatically re-enabled, probably after laptop suspend-resume cycle.
Right now I'm running Bluetooth audio for 2 days with automatic suspend disabled, so far so good.

I'll check whether the bug happens during the week and close the bug with detailed autosuspend disabling procedure description.

[iam (iam-linux-kernel-bugs)]

It's been 12 days without any issues.

Workaround this bug by executing the following command, which disables Bluetooth autosuspend:

    echo 'options btusb enable_autosuspend=0' | sudo tee /etc/modprobe.d/bluetooth.conf

Reboot afterwards.

[kalmaevlv (kalmaevlv-linux-kernel-bugs)]

(In reply to ValdikSS from comment #9)
> It's been 12 days without any issues.
>
> Workaround this bug by executing the following command, which disables
> Bluetooth autosuspend:
>
> echo 'options btusb enable_autosuspend=0' | sudo tee
> /etc/modprobe.d/bluetooth.conf
>
> Reboot afterwards.

Hi. This does not work for some reason in the case of sleep. After waking up from sleep in powertop I see a good state again. Can you advise on more options for this to work correctly?

[iam (iam-linux-kernel-bugs)]

(In reply to Leonid Kalmaev from comment #10)

> Hi. This does not work for some reason in the case of sleep. After waking up
> from sleep in powertop I see a good state again. Can you advise on more
> options for this to work correctly?

It seems there's a bug (or a feature) in kernel, which switches the devices in power save mode after suspend, without triggering UDEV events. Here's what tlp developer says: https://github.com/linrunner/TLP/issues/545

>Imho the kernel never issued udev new device events for existing devices after
>resume. You may look into it yourself by enabling TLP's trace mode with
>TLP_DEBUG="run udev usb".

I use tlp software, with bluetooth module powersave blacklist configured and patch which is mentioned in the URL above applied (`set_usb_suspend 0 auto` in tlp resume handler)

[Sebastien Bacher (seb128)]

Thank you for your bug report but that's the Ubuntu tracker, report Mint issues to them

[Rijnhard Hessel (rijnhard)]

~seb128 I dont think thats fair, this is very likely kernel-related, and the kernel is AFAIK an ubuntu kernel.

Unless I am misunderstanding something

[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 1998103

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.

[Rijnhard Hessel (rijnhard)]

Unforntunately there is no kernel core dump for this error. just the hci subsystem losing its mind, as attached in the logs.

Happy to see what else I can provide

[Rijnhard Hessel (rijnhard)]

Link to related Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=203535

[wiredknight375 (wiredknight375-linux-kernel-bugs)]

Not sure if this will be helpful, and happy to try and help with testing (will need some guidance)

Link to issue I logged on Launchpad. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998103

[Rijnhard Hessel (rijnhard)]

So today, everything is working fine.
pause music, step away from PC to have a snack & coffee.
During that time this happened in the logs:

Dec 01 15:59:41 HESSEL-MSI-MINT kernel: Bluetooth: hci0: command 0x0804 tx timeout
Dec 01 15:59:46 HESSEL-MSI-MINT bluetoothd[987]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110)
Dec 01 15:59:46 HESSEL-MSI-MINT pulseaudio[3495]: Transport Acquire() failed for transport /org/bluez/hci0/dev_40_ED_98_1A_3F_39/sep7/fd0 (Input/output error)
Dec 01 15:59:46 HESSEL-MSI-MINT pulseaudio[3495]: Transport Acquire() failed for transport /org/bluez/hci0/dev_40_ED_98_1A_3F_39/sep7/fd0 (Operation Not Authorized)
Dec 01 15:59:46 HESSEL-MSI-MINT bluetoothd[987]: profiles/audio/a2dp.c:a2dp_resume() avdtp_start failed
Dec 01 15:59:48 HESSEL-MSI-MINT bluetoothd[987]: profiles/audio/avdtp.c:cancel_request() Abort: Connection timed out (110)

Me being oblivious, comes back, hits play, blasts Motionless in White through the speakers to my open plan office.

then these logs shows up:
Dec 01 16:03:03 HESSEL-MSI-MINT pulseaudio[3495]: Refused to switch profile to a2dp_sink: Not connected
Dec 01 16:03:06 HESSEL-MSI-MINT pulseaudio[3495]: Refused to switch profile to a2dp_sink: Not connected

And now attempting to reconnect Blueman fails with Adapter not powered (and device is not soft/hard blocked)

Then if I attempt to turn it on via bluetoothctl:
Agent registered
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Busy

[Rijnhard Hessel (rijnhard)]

Attached latest dmesg.

Firstly I think I messed up and that this may not be related to the attached kernel ticket. (I really am trying to provide meaningful information but without guidance its pretty hard).

I think this is actually related to the VIA Labs VL812 USB hub (2109:0812).

inxi --usb
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
  Device-1: 1-1.3:5 info: Intel Bluetooth wireless interface
    type: Bluetooth rev: 2.0
  Device-2: 1-1.4:4 info: Suyin USB 2.0 Webcam Device type: Video rev: 2.0
  Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
  Device-1: 2-1.4:3 info: MSI steel series rgb keyboard type: HID rev: 1.1
  Hub-5: 3-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0
  Device-1: 3-1:5 info: SteelSeries ApS Rival 650 Wireless type: HID,Mouse
    rev: 2.0
  Hub-6: 3-2:2 info: VIA Labs VL812 Hub ports: 4 rev: 2.1
  Device-1: 3-2.4:4 info: Metadot Das Keyboard 4 type: Keyboard,HID
    rev: 1.1
  Hub-7: 4-0:1 info: Super-speed hub ports: 4 rev: 3.0
  Hub-8: 4-2:112 info: VIA Labs VL812 Hub ports: 4 rev: 3.0

I'll explain what lead me to this.
Today when I plugged my vape into my PC to charge, and it immediately killed my Bluetooth mid-meeting, in fact, bluetoothctl list returned no adapters/controllers.

Then saw the USB hub losing its mind and then the kernel, in its wisdom, decided to just restart the entire hub, which correlated perfectly with the intel bluetooth disappearing from existence.
Then it proceeds to spam my kernel logs with connecting/disconnecting devices (assuming this is the vape).

tldr I fixed it by resetting the actual bluetooth USB device:

Step 1: get the offending USB hub from kernel logs
Step 2: lsusb -d 2109:0812 -t
notice that the bluetooth USB device is attached to this hub (albeit not with the VendorId or ProductId of the bluetooth device)
Step 3: reset Bluetooth USB device directly, sudo usbreset 8087:07dc
Step 4: all works again

I would really appreciate some guidance on how I can do a better job of this Bug...

[toni.andjelkovic (toni.andjelkovic-linux-kernel-bugs)]

Same issue here with a Qualcomm Atheros QCA6174 chip (Acer Aspire 5) and a recent 6.1.15 kernel (Fedora 37).

Reloading kernel modules or messing with the USB power settings did not help. A simple reboot won't do either, you need to poweroff the machine.

My workaround was to disable the Wi-Fi connection to my Android smartphone's Personal Hotspot and use USB or Bluetooth tethering instead. Looks like this bug occurs only when Wi-Fi and Bluetooth are used at the same time.

[dan (dan-linux-kernel-bugs)]

I can confirm similar same results as Toni A. with a Qualcomm Atheros QCA6390 (Dell XPS 15 9500)on Kernels 6.2.7-arch1-1 and 6.1.20-1-lts.

[wiredknight375 (wiredknight375-linux-kernel-bugs)]

Can confirm WiFi was also on on my end. Intel WiFi though.