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

Hello Lovekesh,

I repeated the test using Debian kernel 7.1.3+deb14-amd64 with only the
attached skip-HCI-reset patch applied to btusb.

I started from a complete cold boot. Both Wi-Fi and Bluetooth initialized
normally:

usb 1-10: New USB device found, idVendor=0bda, idProduct=b009
rtw88_8723de 0000:02:00.0: Firmware version 48.0.0, H2C version 0
rtw88_8723de 0000:02:00.0 wlo1: renamed from wlan0

I then performed a normal warm reboot with the existing module-unload
workaround disabled for that reboot.

Skipping HCI_OP_RESET did not prevent the failure.

On the following boot, the Bluetooth USB function again failed to enumerate:

usb 1-10: device descriptor read/64, error -71
usb 1-10: device not accepting address 6, error -71
usb 1-10: device not accepting address 7, error -71

The Wi-Fi function failed in the same way as before:

rtw88_8723de 0000:02:00.0: failed to poll offset=0x5 mask=0x1 value=0x0
rtw88_8723de 0000:02:00.0: mac power on failed
rtw88_8723de 0000:02:00.0: failed to power on mac
rtw88_8723de 0000:02:00.0: probe with driver rtw88_8723de failed with
error -16

No wlo1 interface was created and the Bluetooth device was absent.

As with the previous test, the shutdown-specific diagnostic message was not
preserved in the previous-boot journal. The journal ends when systemd-journald
receives SIGTERM, before the final device shutdown stage.

I had to perform a complete power-off again to recover the device afterward.

The attached archive contains the complete kernel journals from the cold boot
that performed the warm reboot and from the resulting failed boot:

journal-kernel-previous.txt
journal-kernel-current.txt

Archive:

rtl8723de-skip-hci-reset-journals.tar.gz

Regards,
Snake

El jue, 6 ago 2026 a la(s) 4:48 a.m., Lovekesh Solanki
([email protected]) escribió:
>
> On Sun, Aug 02, 2026 at 11:40:51PM -0600, Snake Pilot wrote:
> > Bluetooth: hci0: diag: hci_dev_shtudown: HCI_UP=1 HCI_UNREGISTER=0
> > Bluetooth: hci0: diag: calling vendor shutdown callback
> > Bluetooth: hci0: diag: btrtl_shutdown_realtek: sending HCI_OP_RESET
> > Bluetooth: hci0: diag: btrtl_shutdown_realtek: HCI_OP_RESET completed OK
> > Bluetooth: hci0: diag: vendor shutdown returned 0
> I'm thinking if reset itself is the problem, since it does not run on
> unloading manually but it does on shutdown.
>
> > I did not find the btusb shutdown or rtw_pci_shutdown/D3hot diagnostic
> > messages in the persisted previous-boot journal. The journal appears to end
> > before the final device shutdown stage, so their absence from the journal
> > does not necessarily mean that the callbacks were not invoked.
> Yeah it seems it runs after journal is gone.
>
> I suppose we should test by skipping HCI_OP_RESET if that improves the
> issue.
>
> Could you apply the attached patch only and start with a cold boot then
> do a warm reboot and send the previous and current journal just like you
> did before?
>
> Thanks,
> Lovekesh