From: Ping-Ke Shih <pkshih@realtek.com>
To: Dev Narayan <devnarayan08807@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: rtw89_8852be (RTL8852BE): PCIe device not ready after s2idle resume, probe fails with -110
Date: Thu, 29 Oct 2026 00:31:48 +0000 [thread overview]
Message-ID: <b1111942b19d46f88ac7392e58ee2ca0@realtek.com> (raw)
In-Reply-To: <CADD=N5x9JCh+jaf50Tr13+m3541gqM4iCLSF+KVLOnf7_rW1cA@mail.gmail.com>
// in plain text format please.
Dev Narayan <devnarayan08807@gmail.com> wrote:
> Hello,
>
> I am reporting a Wi-Fi failure after suspend/resume with the rtw89_8852be
> driver. After resume the card never responds, and only a full reboot brings
> Wi-Fi back.
>
> HARDWARE AND SOFTWARE
> - Laptop: ASUS TUF Gaming F16 FX607VJB (Intel Core 5 210H)
> - BIOS: American Megatrends FX607VJB.338, 2025-08-27 <FILL IN: "latest
> available from ASUS as of DATE" or "updated to VERSION and retested"
>
> - Wi-Fi: Realtek RTL8852BE PCIe 802.11ax [10ec:b852], subsystem AzureWave
> [1a3b:5471], at 0000:04:00.0
> - Bluetooth: USB, IMC Networks [13d3:3571] (btusb, Realtek firmware
> rtl8852bu)
> - Distro: Kali Linux (rolling)
> - Kernel: 7.1.5+kali-amd64
> - Firmware: rtw89/rtw8852b_fw-2.bin
It'd better to point out the firmware version you are using.
> - Sleep mode: s2idle (cat /sys/power/mem_sleep shows "[s2idle] deep")
>
> STEPS TO REPRODUCE
> 1. Boot with default settings. Wi-Fi works.
> 2. Run: systemctl suspend
> 3. Wait about 10 seconds and wake the laptop.
>
> EXPECTED RESULT
> Wi-Fi resumes and reconnects.
>
> ACTUAL RESULT
> The Wi-Fi device is gone from NetworkManager (nmcli device lists only lo
> and eth0). lspci still shows the card at 04:00.0, but with no "Kernel
> driver in use". Bluetooth recovers fine after resume; only the Wi-Fi card
> is affected.
>
> KEY KERNEL LOG LINES
> rtw89_8852be 0000:04:00.0: not ready 1023ms after resume; waiting
> ...
> rtw89_8852be 0000:04:00.0: not ready 65535ms after resume; giving up
> rtw89_8852be 0000:04:00.0: failed to write DBI register, addr=0xB48
> rtw89_8852be 0000:04:00.0: failed to read PCI cap, ret=134
> rtw89_8852be 0000:04:00.0: xtal si not ready(W): offset=90 val=10 mask=10
> rtw89_8852be 0000:04:00.0: mac preinit fail, ret: -110
>
> Manually reloading the module afterwards also fails every time:
> rtw89_8852be 0000:04:00.0: loaded firmware rtw89/rtw8852b_fw-2.bin
> rtw89_8852be 0000:04:00.0: xtal si not ready(R): offset=41
> rtw89_8852be 0000:04:00.0: failed to power on
> rtw89_8852be 0000:04:00.0: failed to setup chip information
> rtw89_8852be 0000:04:00.0: probe with driver rtw89_8852be failed with error
> -110
>
> WORKAROUNDS TRIED (none restored Wi-Fi after resume)
> - rtw89_pci disable_aspm_l1=y disable_aspm_l1ss=y disable_clkreq=y
These workarounds take effect after you cold reboot. Please confirm this.
> - rtw89_core disable_ps_mode=y
> - NetworkManager wifi.powersave = 2
> - btusb.enable_autosuspend=n (Bluetooth only)
> - modprobe -r / modprobe of rtw89_8852be
> - PCI remove and rescan of 0000:04:00.0 (echo 1 > /sys/bus/pci/devices/
> 0000:04:00.0/remove, then echo 1 > /sys/bus/pci/rescan)
>
> OTHER NOTES
> - The same symptom occurred on NixOS on this laptop before I moved to Kali,
> so it does not appear to be distro-specific.
> - mem_sleep_default=deep result: <FILL IN: fixed it / did not fix it /
> laptop failed to wake / not tested
>
> - pcie_aspm=off result: <FILL IN or delete this line
>
>
> LOGS
> Full logs are linked below (plain text):
> - dmesg on default settings after the failure: <LINK>
> - dmesg with the workarounds above applied: <LINK>
> - lspci -nnvv -s 04:00.0: <LINK>
> - Kernel, cmdline, DMI and BIOS info: <LINK>
>
> I can test patches or provide more debug output (for example with rtw89
> debug_mask set, or additional kernel parameters) if that helps.
Please try patch [1], but unconditionally do pci_d3cold_disable() no matter
dmi match or not.
[1] https://lore.kernel.org/all/20260911065358.34375-1-pkshih@realtek.com/
parent reply other threads:[~2026-10-29 0:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CADD=N5x9JCh+jaf50Tr13+m3541gqM4iCLSF+KVLOnf7_rW1cA@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1111942b19d46f88ac7392e58ee2ca0@realtek.com \
--to=pkshih@realtek.com \
--cc=devnarayan08807@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox