RE: rtw88: WiFi card is not offloaded properly when suspending the OS
Ping-Ke Shih <[email protected]>
| Newsgroups | dev.linux.lists.regressions,org.kernel.vger.linux-wireless,org.kernel.vger.stable |
|---|---|
| Message-ID | <[email protected]> |
// not top posting. Giovanni Santini <[email protected]> wrote: > On 2026-06-08 03:32, Ping-Ke Shih wrote: > > Giovanni Santini <[email protected]> wrote: > >> Jun 02 17:25:33 archlinux-tug kernel: rtw88_8822ce 0000:03:00.0: failed > >> to send h2c command > >> Jun 02 17:25:33 archlinux-tug kernel: rtw88_8822ce 0000:03:00.0: failed > >> to send h2c command > >> Jun 02 17:25:33 archlinux-tug kernel: rtw88_8822ce 0000:03:00.0: failed > >> to send h2c command > >> Jun 02 17:25:33 archlinux-tug kernel: rtw88_8822ce 0000:03:00.0: failed > >> to send h2c command > >> Jun 02 17:25:36 archlinux-tug kernel: rtw88_8822ce 0000:03:00.0: failed > >> to poll offset=0x5 mask=0x2 value=0x0 > >> Jun 02 17:25:36 archlinux-tug kernel: ------------[ cut here ]------------ > >> Jun 02 17:25:36 archlinux-tug kernel: failed to read DBI register, > >> addr=0x0719 > > Add these below to see if it can help. > > > > sudo nano /etc/modprobe.d/rtw88.conf > > options rtw88_core disable_lps_deep=y > > options rtw88_pci disable_aspm=y > > > > After cold reboot, check /sys/modules/rtw88_*/paramters/* to see if > > the modification takes effect. > > > >> I'm attaching the full boot log, if you need a fresh one I can provide it. > > Before "failed to poll ..." log, I also see > > > > Jun 02 17:25:02 archlinux-tug kernel: rtw88_8822ce 0000:03:00.0: AMD-Vi: > > Event logged [IO_PAGE_FAULT domain=0x000e address=0xae9668bc flags=0x0000] > > > > Please try to turn off IOMMU by editing /etc/default/grub > > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amd_iommu=off iommu=off" > > > > And then update-grub > > > >> I run ArchLinux with KDE Plasma, for networking I use NetworkManager and > >> wpa_supplicant. > >> > >> If you would like me to run tests with e.g. just iwd I can do so, just > >> let me know what setup you would like me to have. > >> > >> I do not have this issue with the LTS kernel 6.18.34. This affects 7.0 > >> and 7.1. > >> I believe this issue was not present in < 7 kernels, but I cannot guarantee. > >> I can however downgrade to previous kernels to understand where the > >> issue was introduced. > > The commits between 6.18.34 ~ 7.0.10 are quite few, and I can't find the > > one that can affect the behavior. Please switch your kernel back to 6.18.34, > > and apply rtw88's patches added until 7.0.10. > > > > Since the last commit of 6.18 is fce6fee0817b8899e0ee38ab6b98f0d7e939ceed > > > > Please use below commands to get the (20) patches: > > drivers/net/wireless/realtek/rtw88$ git format-patch > v7.0.10...fce6fee0817b8899e0ee38ab6b98f0d7e939ceed -- ./ > > > > Then you can add them one by one to see which one is the cause. > > > > The git repository you need is: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git > > > > In short I should build the LTS kernel using the provided source with > all the module patches applied one by one, correct? Yes, you can use LTS kernel or distro release version, and only re-build and replace driver. > > If so, should I also set the modprobe.d options plus disable IOMMU? > > After I know this I can start testing. Two directions: 1. try to fix on (problematic) 7.0.10 Try modprobe.d options and/or disable IOMMU. 2. start from (workable) 6.18 Pick and apply patches from 6.18 to 7.0.10 one by one to find the cause. But as I mentioned, I can't find what can affect the behavior you encountered. > > Small update: the .35 LTS kernel has no issues for me, while 7.0.11 works. Did you mean 7.0.10 doesn't work to you, but 7.0.11 works well? However, the rtw88 driver has no change between 7.0.10 and 7.0.11. I feel the cause might be changes of PCI host, but drivers/pci/ has no changes neither. No obvious idea for now. > > I was able to get my laptop to sleep a few times, but at a certain point > the issue happened. > > It is a bit hard to replicate the issue, so I will try my best. I suggest that you can go back to 7.0.10 and try 10 or 20 times, and then compare the results between 7.0.10 and 7.0.11. Ping-Ke