Linux wireless drivers development
 help / color / mirror / Atom feed
* Bug report: Realtek RTL8851BE Wi-Fi does not recover from suspend
@ 2026-11-21  5:39 Rik van Westendorp
  2026-11-22  1:37 ` Ping-Ke Shih
  0 siblings, 1 reply; 2+ messages in thread
From: Rik van Westendorp @ 2026-11-21  5:39 UTC (permalink / raw)
  To: linux-wireless

Bug report: Realtek RTL8851BE Wi-Fi does not recover from suspend

Summary

On an ASUS Vivobook 14 X1404MA, the Wi-Fi adapter (Realtek RTL8851BE)
does not come back after resuming from suspend (s2idle). After resume,
the wireless interface (wlp1s0) disappears completely from
NetworkManager (nmcli device shows only lo), no wireless networks are
visible, and a full reboot is required to restore Wi-Fi. Wired
networking is not available on this laptop, so the machine is
effectively offline until reboot.

Hardware

Laptop: ASUS Vivobook 14 X1404MA (Intel Core 5 315 platform, brand new,
2026)

Wi-Fi/Bluetooth combo: Realtek RTL8851BE PCIe 802.11ax (subsystem:
Foxconn International, Inc.)

Kernel driver: rtw89_8851be

Bluetooth part (RTL8851BU over USB/SDIO): also reloads firmware after
resume and appears affected

Software

OS: Ubuntu 26.04 LTS (Resolute), fully updated as of 2026-11-21 (apt
full-upgrade clean, no phasing issues relevant)

Kernel: 6.x/7.0 series - 7.0.0-44-generic (issue also present on 7.0.0-
30-generic before update)

NetworkManager: 1.54.3

Firmware: rtw89/rtw8851b_fw.bin, firmware version reported at boot:
0.29.41.5 (4bd6ebac)

Symptoms and dmesg evidence

Immediately after resume, the kernel logs (dmesg) show the driver
failing to reinitialize the chip:

rtw89_8851be 0000:01:00.0: failed to write DBI register, addr=0xB48
rtw89_8851be 0000:01:00.0: failed to write DBI register, addr=0xB48
rtw89_8851be 0000:01:00.0: failed to read PCI cap, ret=134
rtw89_8851be 0000:01:00.0: loaded firmware rtw89/rtw8851b_fw.bin
rtw89_8851be 0000:01:00.0: xtal si not ready(R): offset=41
rtw89_8851be 0000:01:00.0: xtal si not ready(W): offset=90 val=10
mask=10
rtw89_8851be 0000:01:00.0: failed to power on
rtw89_8851be 0000:01:00.0: failed to setup chip information
rtw89_8851be 0000:01:00.0: probe with driver rtw89_8851be failed with
error -110

Additional recurring warnings while the system is running (before
suspend, sometimes after heavy traffic):

rtw89_8851be 0000:01:00.0: timed out to flush queues

NetworkManager logs meanwhile show the device moving to unmanaged and
the rfkill device for the adapter disappearing (radio killswitch
/sys/devices/.../rfkill3 disappeared), after which the Wi-Fi device is
gone. A cold boot restores everything: firmware loads, chip powers on,
connection succeeds. This is a power-state problem, not a general
driver-failure problem.

Workarounds attempted (all without success)

Full system update (apt full-upgrade), including kernel upgrade from
7.0.0-30 to 7.0.0-44: issue persists.

Disable Wi-Fi power saving in NetworkManager (wifi.powersave = 2): no
effect.

Kill and re-enable Wi-Fi radio via nmcli radio wifi off/on after
resume: device does not return.

Manual driver reload after resume (modprobe -r rtw89_8851be && modprobe
rtw89_8851be): fails with the failed to power on / error -110 messages
above.

Resume hook in /usr/lib/systemd/system-sleep/ unloading and reloading
the module and restarting NetworkManager: no effect (same driver
failure).

Module options rtw89_pci disable_clkreq=y and rtw89_core
disable_lps_deep=y (verified active via sysfs): issue persists.

Kernel parameter pcie_aspm=off (verified active via /proc/cmdline):
issue persists.

Switching suspend mode to deep (mem_sleep_default=deep): made things
worse, system failed to wake at all from suspend and required a 10-15 s
power-button hard shutdown; reverted. Platform apparently only supports
s2idle properly.

Manual PCI remove/rescan after a failed resume (echo 1 >
/sys/bus/pci/devices/0000:01:00.0/remove, then echo 1 >
/sys/bus/pci/rescan) was not yet tested successfully.

Current status

All configuration changes have been reverted to stock. Laptop boots and
works normally, Wi-Fi works normally after a cold boot. Suspend remains
unusable: after resume there is no Wi-Fi at all, and the only recourse
is a full reboot. As a result, suspend cannot be used on this machine.

Request

This appears to be a power-management state bug in the rtw89 driver /
the RTL8851BE firmware suspend path (PCIe device fails to power on
after resume, error -110 = ETIMEDOUT at probe). The chip seems to
remain wedged in a low-power state that the driver cannot recover from,
even after full module reload.

Requested: investigation of the rtw89 suspend/resume path for RTL8851BE
on s2idle, ideally fixed in a future kernel/firmware update. Happy to
provide full logs (dmesg, NetworkManager journal, lspci -vv, uname -a)
on request. Please let me know if additional debugging output would
help (e.g. dynamic debug traces of rtw89 suspend).

Reporter

Rik van Westendorp, ThailandDate: 21 November 2026
-- 
sent from Ubuntu / Evolution

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-11-22  1:37 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-21  5:39 Bug report: Realtek RTL8851BE Wi-Fi does not recover from suspend Rik van Westendorp
2026-11-22  1:37 ` Ping-Ke Shih

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox