[RESPONDED] Bluetooth restarts on Ubuntu kernel 6.5.0-14 11th Gen

Framework Laptop 13 Linux
1

I only see this issue on 6.5.0-14, booting with 6.5.0-13 serves as a workaround.

I’m using a bluetooth mouse and with the latest Ubuntu kernel the mouse disconnects and re-connects every few seconds. At these moments, I see the following messages appearing in the journal:

Dez 15 10:35:38 frame kernel: usb 3-4: new full-speed USB device number 13 using xhci_hcd
Dez 15 10:35:39 frame kernel: usb 3-4: device descriptor read/64, error -71
Dez 15 10:35:39 frame kernel: usb 3-4: device descriptor read/64, error -71
Dez 15 10:35:39 frame kernel: usb 3-4: new full-speed USB device number 14 using xhci_hcd
Dez 15 10:35:40 frame kernel: usb 3-4: device descriptor read/64, error -71
Dez 15 10:35:40 frame kernel: usb 3-4: device descriptor read/64, error -71
Dez 15 10:35:40 frame kernel: usb usb3-port4: attempt power cycle
Dez 15 10:35:40 frame kernel: usb 3-4: new full-speed USB device number 15 using xhci_hcd
Dez 15 10:35:40 frame kernel: usb 3-4: Device not responding to setup address.
Dez 15 10:35:41 frame kernel: usb 3-4: Device not responding to setup address.
Dez 15 10:35:41 frame kernel: usb 3-4: device not accepting address 15, error -71
Dez 15 10:35:41 frame kernel: usb 3-4: new full-speed USB device number 16 using xhci_hcd
Dez 15 10:35:41 frame kernel: usb 3-4: Device not responding to setup address.
Dez 15 10:35:41 frame kernel: usb 3-4: Device not responding to setup address.
Dez 15 10:35:41 frame kernel: usb 3-4: device not accepting address 16, error -71
Dez 15 10:35:41 frame kernel: usb usb3-port4: unable to enumerate USB device

Please advise where to report this issue and for which package?

2

I have noticed that Bluetooth and Ubuntu on the OEM kernel does not work through gnome settings. You have to use bluetoothctr and even then performance is terrible with a lot of lag.

I’m only mentioning this here for information. This is not Framework’s problem to fix, but rather Canonicals. Framework’s super awesome Linux customer support specialists might have something to say to help, but that is just them being awesome.

3

Hi @Tom_Adler,

Are you using an external USB Bluetooth dongle by chance? Instead of the Bluetooth provided by the Wifi/Bluetooth card in the laptop? Are there any other USB devices attached by chance?

Also noted you’e using 6.5.0-14/6.5.0-13, may I ask which version of Ubuntu you’re using? For Ubuntu LTS, you would want to use the tested OEM C kernel mentioned in step 9 of the guide.

Interesting. OEM C kernel, fully updated? Not something I have had experienced myself. Just used OEM C kernel on Ubuntu 22.04 with my Bluetooth mouse Friday for testing, using the built in Bluetooth with the Intel card.

I’d be interested in hearing more so I might replicate this. Thanks @2disbetter :slight_smile:

1 Like
4

Yep using the latest OEM kernel. It is a standalone 11th gen mainboard in a Coolermaster case. I suppose bluetooth reception could be getting messed with. I am trying to use a 8-bit bt controller about 1.5 meters (5 feet) from the coolermaster case, and I am just seeing huge lage. Trying to play Spelunky, for example, is neigh impossible because of the lag.

5

Hi @Matt_Hartley,

Are you using an external USB Bluetooth dongle by chance? Instead of the Bluetooth provided by the Wifi/Bluetooth card in the laptop? Are there any other USB devices attached by chance?

I’m using the onboard Bluetooth, not a dongle. There were no USB devices attached, and the laptop was on AC via the kit charger.

Also noted you’e using 6.5.0-14/6.5.0-13, may I ask which version of Ubuntu you’re using?

I’m using the non-LTS version 23.10, fully upgraded.

6

Thanks Tom,

Let’s get this into a ticket as we may need to dig deeper on this.

7

Hmm, yeah, it could be the case. Would be interesting to see if you see this issue elsewhere with the board.

8

Done! Thank you Matt!

1 Like
9

So a workaround was to set options btusb enable_autosuspend=0 in /etc/modprobe.d/bluetooth.conf, this resolved the issue.

Later on came kernels -15 and -17, I enabled autosuspend again, and the issue didn’t appear.

10

Interesting, this appears to be a regression as this was supposed to have been resolved sometime back.

This gels based on:

As this affected you on your 11th gen board, are you comfortable filing a bug on Lauchpad?

If not, I can file it but I may need to tap you for the log segment where the error is taking place.

11

Reporting this to developers was my original intention actually, I just don’t know which package to report this for

Please advise where to report this issue and for which package?