New: MT7902 Bluetooth USB 0e8d:1ede firmware crashes during use; reset fails and controller becomes unresponsive
https://bugzilla.kernel.org/show_bug.cgi?id=221878
Bug ID: 221878
Summary: MT7902 Bluetooth USB 0e8d:1ede firmware crashes during
use; reset fails and controller becomes unresponsive
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: No
Created attachment 310636
--> https://bugzilla.kernel.org/attachment.cgi?id=310636&action=edit
Complete MT7902 reproduction report and logs
## Summary
The MediaTek MT7902 Bluetooth adapter (0e8d:1ede) initializes and works, but its firmware crashes during normal use. The subsequent subsystem reset fails, hci0 disappears, and USB descriptor requests time out. Recovery requires a full laptop EC/power reset.
## Hardware
* Laptop: HP Laptop 15-fd0xxx
* BIOS: AMI F.14, 2024-12-05
* Wi-Fi PCI ID: 14c3:7902 (MediaTek MT7902 / Filogic 310)
* Bluetooth USB ID: 0e8d:1ede
* Bluetooth drivers: btusb, btmtk
## Software
* Distribution: Arch Linux
* Kernel: 7.1.8-arch1-3
* BlueZ: 5.87-2
* linux-firmware: 20260810-1
* linux-firmware-mediatek: 20260810-1
The same failure was previously reproduced on Linux 7.1.6 and with linux-firmware 20260622.
## Steps to reproduce
1. Shut down the laptop, disconnect AC, and hold the power button for 40–60 seconds to recover the controller.
2. Boot Linux and verify that hci0 initializes.
3. Connect and use Bluetooth normally.
4. Wait several minutes for the controller failure.
## Latest reproduction timeline
* 15:32:23 — USB device 0e8d:1ede enumerated.
* 15:32:27 — hci0 setup completed.
* 15:33:08 — Sony WH-1000XM5 connected.
* 15:41:54 — MediaTek coredump completed.
* 15:42:04 — MediaTek subsystem reset failed.
* After 15:42 — USB descriptor requests failed with -110, followed by address failures with -62 and USB disconnect.
## Key kernel messages
``` Bluetooth: hci0: Mediatek coredump end Bluetooth: hci0: Can't get device id, subsys reset fail. usb 1-10: device descriptor read/64, error -110 usb 1-10: device not accepting address 3, error -62 usb 1-10: USB disconnect, device number 3 ```
## State after failure
bluetoothctl show reports:
``` No default controller available ```
BlueZ remains running, but hci0 is gone. Reloading btusb cannot recover the hardware because it no longer responds. An ordinary reboot may preserve the failed state; a full EC/power reset is required.
## Additional observations
* The failure has occurred with Sony WH-1000XM5 connected.
* It has also occurred on another boot without the XM5, while a Bluetooth keyboard was used.
* Restricting WirePlumber to A2DP and excluding HSP/HFP did not prevent failure.
* Updating both the kernel and MediaTek firmware did not prevent failure.
* A devcoredump entry existed immediately after this reproduction. Its data file was deliberately not read/consumed pending maintainer instructions.
## Expected result
The controller remains operational, or successfully recovers after the driver initiates a subsystem/USB reset.
## Actual result
The firmware crashes, reset fails, the USB device becomes unresponsive, and physical power recovery is required.
## Related reports
* https://bugzilla.kernel.org/show_bug.cgi?id=221380 — same MT7902 USB ID. That report concerns unsupported hardware; my controller initializes and works before crashing at runtime, so this does not appear to be a duplicate.
* https://bugzilla.kernel.org/show_bug.cgi?id=220986 — related MT7902 initialization report for a different USB product ID.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 221878] MT7902 Bluetooth USB 0e8d:1ede firmware crashes during use; reset fails and controller becomes unresponsive
https://bugzilla.kernel.org/show_bug.cgi?id=221878
The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) ---
Quoted 1 line
The same failure was previously reproduced on Linux 7.1.6
So did this ever work? e.g. with earlier versions from the same or an older kernel series Or an older firmware?
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 221878] MT7902 Bluetooth USB 0e8d:1ede firmware crashes during use; reset fails and controller becomes unresponsive
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221878
--- Comment #2 from [email protected] ([email protected]) --- (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #1)
Quoted 4 lines
Quoted 1 line
The same failure was previously reproduced on Linux 7.1.6
So did this ever work? e.g. with earlier versions from the same or an older kernel series Or an older firmware?
I do not have a kernel/firmware combination. The laptop was installed with a recent kernel. I did not test prior versions.
I have had issues with Linux 7.1.6 linux-firmware 20260622 and Linux 7.1.8 firmware 20260810. I cannot classify this as a regression.
I will try to test earlier versions of the MT7902 Bluetooth firmware and report the results
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 221878] MT7902 Bluetooth USB 0e8d:1ede firmware crashes during use; reset fails and controller becomes unresponsive
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221878
--- Comment #3 from [email protected] ([email protected]) --- I tested an older MT7902 Bluetooth firmware continuously for approximately one week (2026-08-18 through 2026-08-25) under normal use, including my usual Bluetooth devices, without
reproducing the firmware coredump, subsystem-reset failure, USB timeouts, or controller disappearance.
Working firmware:
- Build time/version: 20220107141051
- SHA-256: b720c3883aeaa926fe16930f3f4cddd29a3ecfd0a7c519f0a18efd42423b591e
- Source: historical community MT7902 firmware blob
- Current kernel: 7.1.9-arch1-2
- BlueZ: 5.87-2
Failing official firmware:
- Build time/version: 20250826211444
- SHA-256: 4f53b5e02fbd933172e18caf952bda410a877eaad00561781528cb4aff58dc38
The official blob is identical in Arch linux-firmware-mediatek releases 20260309 through 20260810; older official packages do not contain MT7902 Bluetooth firmware. With the official
blob, failure typically occurred within minutes, whereas the 2022 blob has remained stable for about one week. This strongly suggests a regression or hardware-variant incompatibility in the
current official MT7902 Bluetooth firmware rather than a general BlueZ failure.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 221878] MT7902 Bluetooth USB 0e8d:1ede firmware crashes during use; reset fails and controller becomes unresponsive
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221878
--- Comment #4 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) --- Then this bug tracker is unlikely to help. You want to report this to mediatek.
You could try reaching out to the their Linux developers; better report this my
mail to Sean Wang <[email protected]>, CCed to
[email protected] ; if this turns out to be a kernel
regressions, please bring me in the loop again.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.