Re: [BUG] rtw88_8723de: Wi-Fi and Bluetooth fail after warm reboot

From: Snake Pilot

Date: Fri Jul 31 2026 - 06:06:15 EST


Thank you for the test suggestions. I ran the requested matrix with the
packaged Debian kernel 7.1.3+deb14-amd64 (Debian 7.1.3-1), the in-tree
drivers, and kernel taint 0.

For each module test I unloaded only the named module, added the requested
explicit delay, and rebooted. The normal system shutdown took approximately
four seconds in addition to the explicit delay.

Results:

Module unloaded Extra delay Wi-Fi Bluetooth
------------------------------------------------------------------------
rtw88_8723de 0 seconds failed (-16) failed (-71)
rtw88_8723de 1 second failed (-16) failed (-71)
rtw88_8723de 3 seconds failed (-16) failed (-71)
rtw88_8723de 5 seconds failed (-16) failed (-71)

btusb 0 seconds worked worked
btusb 1 second worked worked
btusb 3 seconds worked worked
btusb 5 seconds worked worked

Therefore, unloading only rtw88_8723de does not prevent either failure.
Unloading only btusb prevents both failures, even with no explicit delay.

The btusb tests used BlueZ 5.87-1, which was installed before that complete
set of tests. The kernel, btusb module, firmware-realtek package, and Wi-Fi
firmware did not change. The original Bluetooth failure is USB enumeration
error -71 and occurs before btusb or BlueZ can bind.

I also tested the PCI reset attribute after reproducing the failed warm boot.
Before the reset, Wi-Fi had failed with the MAC power-on error and probe error
-16, while Bluetooth had failed to enumerate with error -71. The device was
present at 0000:02:00.0 in D0, reset_method reported "bus", and no Wi-Fi
driver was bound.

Writing 1 to:

/sys/bus/pci/devices/0000:02:00.0/reset

succeeded. I then requested a reprobe through /sys/bus/pci/drivers_probe.
The reprobe failed again with the same messages:

rtw88_8723de 0000:02:00.0: mac power on failed
rtw88_8723de 0000:02:00.0: probe with driver rtw88_8723de failed
with error -16

No Wi-Fi interface appeared, and Bluetooth remained absent. Thus, the PCI bus
reset did not recover the device after the failure had occurred.

The attached archive contains:

MATRIX.txt
Complete module/delay test matrix and overall conclusions.

cold-boot-dmesg.txt
Complete dmesg after at least 30 seconds powered off, using the same
Debian kernel.

cold-boot-lspci-vv.txt
cold-boot-lsusb-t.txt
PCI and USB topology from the successful controlled cold boot.

failing-warm-boot-dmesg.txt
failing-warm-boot-journal-kernel.txt
Complete dmesg and journalctl -k output captured during the failing warm
boot, before attempting the PCI reset.

previous-boot-journal-kernel.txt
Complete journalctl -k -b -1 output captured from the failing boot.

failing-warm-boot-lspci-vv.txt
failing-warm-boot-lsusb-t.txt
PCI and USB state during the failure, before the reset.

pci-reset-result.txt
Timestamped result of writing 1 to the PCI reset attribute.

post-pci-reset-dmesg.txt
post-pci-reset-lspci-vv.txt
Complete dmesg and PCI state after the reset and failed reprobe.

package-versions.txt
Exact BlueZ, firmware-realtek, and Debian kernel package versions.

In the controlled cold-boot capture, USB 0bda:b009 enumerated normally, btusb
bound, rtw88_8723de initialized firmware 48.0.0, and wlo1 appeared. No error
-71, MAC power-on failure, or probe error -16 was logged.

The results suggest that shutdown of the USB Bluetooth function changes the
retained state of the whole combo device, while shutdown of the PCIe Wi-Fi
function alone does not.

Please let me know if you would like a trace around btusb disconnect, USB
power management state, or a test of a specific reset sequence.

Kind regards,
Snake.

Attachment: rtl8723de-warm-reboot-evidence-20260730.tar.gz
Description: application/gzip