Bug 2280288

Summary: bluez crash on F39/F40 on Intel AX210 hardware
Product: [Fedora] Fedora Reporter: Maxim Therrien <acerspyro>
Component: bluezAssignee: Gopal krishna tiwari <gopalkrishna.tiwari>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 40CC: dwmw2, gopalkrishna.tiwari, pbrobinson, spacewar
Target Milestone: ---Keywords: Desktop, Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: bluez-5.76-1.fc40 bluez-5.76-1.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-23 01:08:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Maxim Therrien 2024-05-14 00:44:04 UTC
Hello!

I'm having constant crashing issues with Bluez on my AX210 since upgrading to Fedora 40. Allegedly, other people on up to date F39 are also affected.

Bluez crashes on resume or when connecting a device (typing to wake up a keyboard, moving the mouse to wake it up or turning on a paired headset), and will sometimes slug and crash for no reason when Bluetooth is overloaded (e.g.: taking a call and typing a lot).
The sluggishness also makes little sense given the hardware, but that could be a wholly different issue.

Here are my Bluez abrt reports, which may or may not be complete:

https://bugzilla.redhat.com/show_bug.cgi?id=2278051
https://bugzilla.redhat.com/show_bug.cgi?id=2277661
https://bugzilla.redhat.com/show_bug.cgi?id=2277322
https://bugzilla.redhat.com/show_bug.cgi?id=2278801
https://bugzilla.redhat.com/show_bug.cgi?id=2278052
https://bugzilla.redhat.com/show_bug.cgi?id=2278802
https://bugzilla.redhat.com/show_bug.cgi?id=2278053

Given that Bluez seems to be crashing in relatively random functions, it's possible this may be a kernel / driver bug.

Reproducible: Always

Steps to Reproduce:
--First Scenario--
1. Put computer to sleep with Bluetooth enabled
2. Wake computer
3. Find that bluez has crashed and Bluetooth stays disabled

--Second scenario--
1. Connect Keychron K14 (or similar) keyboard via Bluetooth
2. Wait for keyboard to go to sleep
3. Wake keyboard up
4. Find that the bluetooth stack restarts, killing all active connections
Actual Results:  
Bluetooth stack crashes, Bluetooth stays off on wake and restarts on keyboard reconnect

Expected Results:  
Bluetooth stack stays up, and stays on after wake

Hardware:
Archer TX55E (AX210) Wi-Fi / Bluetooth via PCIe
GIGABYTE AORUS X470 ULTRA GAMING
Ryzen 7 5700x
32 GB DDR4
Disk has 400GB free

Software:
Fedora 40 (upgraded from 39 during the F40 beta)
bluetooth.conf reset to default
Paired Bluetooth devices have been deleted manually by deleting the file structure at /var/lib/bluetooth

bluez 5.75-1.fc40 x86_64
linux-firmware 20240410-1.fc40
Linux 6.8.7-300.fc40.x86_64

Comment 1 Peter Robinson 2024-05-20 12:35:38 UTC
> I'm having constant crashing issues with Bluez on my AX210 since upgrading
> to Fedora 40. Allegedly, other people on up to date F39 are also affected.

Probably not specific to the AX210 else we'd see other reports.
 
> Bluez crashes on resume or when connecting a device (typing to wake up a
> keyboard, moving the mouse to wake it up or turning on a paired headset),

Suspect it's HID related, and I suspect the new update may fix it.

Comment 2 Fedora Update System 2024-05-20 12:36:01 UTC
FEDORA-2024-e34c8cbb70 (bluez-5.76-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-e34c8cbb70

Comment 3 Fedora Update System 2024-05-20 12:36:30 UTC
FEDORA-2024-9f7bb41811 (bluez-5.76-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-9f7bb41811

Comment 4 Maxim Therrien 2024-05-20 18:58:07 UTC
Thanks Peter for the update! I've installed the 5.76-1 package candidate, will report back in a few days :)

Comment 5 Fedora Update System 2024-05-21 02:21:45 UTC
FEDORA-2024-9f7bb41811 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-9f7bb41811`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-9f7bb41811

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-05-21 03:04:56 UTC
FEDORA-2024-e34c8cbb70 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-e34c8cbb70`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-e34c8cbb70

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-05-23 01:08:57 UTC
FEDORA-2024-9f7bb41811 (bluez-5.76-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2024-06-05 08:34:14 UTC
FEDORA-2024-e34c8cbb70 (bluez-5.76-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Maxim Therrien 2024-08-31 17:05:20 UTC
This specific problem is resolved, but I do have stability issues that I'll try to troubleshoot and address in another bug report. Thanks for your help :)