RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

I am unsure how to attach multiple log files so here are the contents of the short logs. Attached is the output of "lspci -vvnn" in 5.7.0-rc1

Output of "uname -a" on 5.7.0:

Linux laptop 5.7.0-050700rc1-generic #202004122032 SMP Sun Apr 12 20:36:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

---
"cat /proc/version" on 5.7.0 yields:

Linux version 5.7.0-050700rc1-generic (kernel@sita) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1), GNU ld (GNU Binutils for Ubuntu) 2.34) #202004122032 SMP Sun Apr 12 20:36:25 UTC 2020

---
"cat /proc/version" on 5.4.0-21 yields:

Ubuntu 5.4.0-21.25-generic 5.4.27

---
"uname -a" on 5.4.0 yields:

Linux laptop 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

This change was made by a bot.

Please test kernel here:
https://people.canonical.com/~khfeng/lp1872984/

The crash also occurs in the kernel version 5.6.0-8-generic #8~lp1872984 linked above; however, two distinct behaviors are present depending on whether or not wifi was ON/OFF in NetworkManager. If it was enabled previously, and then the machine is powered off and back on, the driver appears to send an auth to the default network before crashing (explained below, c.f. attached dmesg logs). Regardless, it will crash and fail to power on if it is turned off and back on in NetworkManager.Case 1 (on):   Boot 1: (Was connected to network on kernel 5.4.0-18, powered off device, then powered on and changed kernel to 5.6.0lp in grub) - The network driver successfully authed with the default network and I was even able to ping google.com. After turning wifi off and then back on again, the network driver is unable to scan for networks and shows a crash in dmesg (dmesg-auth1.log)   Boot 2: (Powered off and restarted after previous attempt, no settings changed) The network driver appeared to auth in dmesg with the specified network then immediately crash. Attempts to turn OFF/ON again in networkmanager result in "fail to power on mac" error in dmesg (dmesg-auth2.log)Case 2 (off):   Boot 3: (Turned off wifi in NetworkManager after boot 2, then powered off and restarted machine) Network driver crashes after enabled on boot and fails to power on when turning off/on in networkmanager (c.f. [5.611939] rtw_pci 0000:3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0) (dmesg-lp-crash.log)

Ok. Can you please blacklist rtw_pci and attach `sudo lspci -vv` again?

After adding rtw_pci to /etc/modprobe.d/blacklist.conf , running "sudo depmod -a" and "sudo update-initramfs -u -k '5.6.0-8-generic'" and rebooting, rtw_pci was loaded by the other driver "rtwpci". Adding "rtwpci" to the blacklist and rebooting, "lspci -vvnn" gives a proper output for the network device. However, with disabling these two drivers there is zero internet functionality since the device does not have a driver associated with it and the kernel does not have one available to load, of course.  Attached is both the dmesg and lspci outputs from when both of these modules were blacklisted. I was expecting the kernel to load the old realtek network driver 'rtlwifi' instead, but I guess it is no longer installed.

Please test this kernel:
https://people.canonical.com/~khfeng/lp1872984-2/

Which disables L0s.

Still getting the same errors (with no blacklists in /etc/modprobe.d)

lspci output: https://gist.github.com/ayush--s/46489a2c8ae2a42e58219c4b22fef6ef

# uname -a
Linux box 5.6.0-8-generic #8~lp1872984+2 SMP Fri Apr 17 11:35:19 CST 2020 x86_64 x86_64 x86_64 GNU/Linux

Is the system Lenovo Yoga? Can you please update BIOS and see if the issue goes away?

The system is Asus Vivobook 14. See https://gist.github.com/ayush--s/46489a2c8ae2a42e58219c4b22fef6ef#file-dmesg-log-L781 for full hardware details captured in dmesg.

Hi,

I have same issue here with same Asus laptop.
`kernel: DMI: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FN_S430FN/X430FN, BIOS X430FN.308 05/28/2019`

It seems I have to step back to 19.10.
:-(

by. sTv

I had the same problem with Lenovo Flex 6 14IKB on Focal Fossa (5.4.0-28). I followed Kai-Heng Feng's sugggestion and updated the BIOS. Luckily I had a dual-boot Windows on that machine and was able to do so easily. Now it's working flawlessly.

After a firmware update, I also can confirm that the issue was resolved on a Lenovo Yoga 730.

I am experiencing the same issue on a Lenovo Y530-15ICH. After BIOS update, the issue seemed to no longer occur, however, it has now reappeared.
I am currently running BIOS version 8JCN53WW (Dec 2019), the latest.

I can also vouch that I run into this issue on a Lenovo Y530-15ICH after upgrading to Focal Fossa. I haven't upgraded my BIOS (I'm afraid to until I'm certain I'm doing it correctly).

Does cold boot help?

I'm on Lenovo Legion Y530-15ICH and I have the same issue.
It's been too long without this fixed.

I am currently running BIOS version 8JCN50WW and I suspect that upgrading the BIOS is not going to be the solution.

Does anyone know what this message mean??

07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter (rev ff) (prog-if ff)
        !!! Unknown header type 7f <------------------------------ ???
        Kernel driver in use: rtw_pci
        Kernel modules: rtwpci

hoku,

Does a cold boot resolve the issue?

Cold boot does not help.
WiFi has a very strange behavior:
If I cold boot the WiFi crashes after a random period of time.
Also, I've noticed that using torrent clients or accessing speed-test pages like fast.com tend to trigger the error (might be high WiFi load ???? )
If I reboot after a crash the WiFi will crash again.
If I reboot into windows after a crash and then reboot into Linux the WiFi works fine.
And then, I discovered that if i cold boot into windows and then reboot to Linux the WiFi also works fine. (last time I used it for three hours without any crash)

I've installed focal now on the laptop and I use it as a primary OS. The only catch is that I have to boot cycle through windows in order to have a functional WiFi.

I cannot thing of a reasonable explanation for this bug!!!!

campus, can you please attach full dmesg?

I have posted all the information in here
https://answers.launchpad.net/ubuntu/+question/691415

If you need anything else please let me know.

I can't believe that this issue is still going on..

@pe83 As of today, I am still experiencing these issues with a fresh install of Ubuntu 20 on a Lenovo Legion Y530-15ICH.
The only solution I see fit at this time is a downgrade to 19.

https://bugzilla.kernel.org/show_bug.cgi?id=206411

https://bugzilla.kernel.org/show_bug.cgi?id=206411#c9 stated it may relate to the power sequence of a specific platform. I have also RTL8822BE installed, but it works on every Focal/Groovy + 5.4.0-42/5.7-rc1/5.8.0-16/5.9-rc1 combination.

Can you guys please test this kernel:
https://people.canonical.com/~khfeng/lp1872984-d3/

Set to INCOMPLETE for comment #28. Please reset it back to CONFIRMED or other appropriate state with comments for the result of the test kernel in comment #28.

The problem persists in the tested 5.9 kernel (tried with cold boot and reboot).
Also, if I boot cycle through windows the wifi works.
I attached the dmesg.

Hi, please test the kernel via several reboots.

i.e. something like Windows -> Linux -> Linux -> Linux

Without testing the new kernel (I have 5.4.0-42-generic), I have tried https://bugzilla.kernel.org/show_bug.cgi?id=206411#c11, and then booted to Windows, connected to a network, and powered off windows with the "Fast Boot" option disabled in Power Options.

So far, with several reboots, the wifi works correctly. I will be updating you if the issue reappears, but so far this seems to be a good fix for me.

George, possible to test https://people.canonical.com/~khfeng/lp1872984-d3/ ?

Hello Kai.
After several reboots this morning I was convinced the issue would no longer reproduce. A couple minutes ago I have rebooted the system and the issue reproduced, and I was unable to get the wifi card working even though I have rebooted into Windows and back into Linux several times.

I have installed 5.9.0-rc1+ and tried rebooting again into Windows and then Linux, this time successfully connecting to Wifi.

I will be updating you if the issue reproduces. Let me know if you need any kind of logs that could help debug this issue.

I was on kernel version 5.4.0.47-generic and was using the rtl8822be repo of mid-kid on github. I didn't even need to boot on windoes first to get wifi working, it was all fine, however when I updated to 5.4.0.48-generic that one stopped working, therefore I tried installing the kernel above (5.9.0-rc1+) and I couldn't even boot to ubuntu. Now I've returned to my working 5.4.0.47-generic and I'll stay so, here is the reason why I couldn't boot into ubuntu

Lenovo Y530-15ICH, dual boot Windows 10 and fresh Ubuntu 20.04 install, seperate drives,UEFI. Kernel version 5.4.0-52-generic. Wifi card: RTL8822BE. Worked on the first day, stopped on the second one. Mostly shows "no networks" although sometimes when I reboot I get "Wifi adapter not found". Tried rtw88 drivers, as well as r8822be. Secure boot off, bios Version: 8JCN52WW (06/14/2019).

I can confirm this problem exists on Lenovo Flex 6 14IKB, on both Ubuntu 20.04 (using 5.4.0-26-generic and above) and on 20.10 (using 5.8.0-25-generic).

Upgrading BIOS to latest did NOT solve this issue for me.

As others have reported, wifi appears to work normally for a while, but in my case it stops working after I ask NetworkManager to connect to a network.

Update:

Based on comments here: https://bugzilla.kernel.org/show_bug.cgi?id=206411#c12

I tried adding "options rtw88_pci disable_aspm=1" to /etc/modprobe.d/rtw88_pci.conf , which appears to solve the issue in Groovy Gorilla under 5.8.0-25-generic.

I will update if this workaround is not permanent.

Please remove "options rtw88_pci disable_aspm=1", install latest mainline kernel, and reboot twice:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10-rc1/amd64/

Particularly, to test "rtw88: pci: Power cycle device during shutdown".

Hi Feng, I was unable to try the suggested kernel as it is unsigned (and I could not find instructions on how to get an unsigned kernel to boot).

Please disable secure boot from BIOS.

Hi, I booted by disabling secure boot as suggested and it seems to fix the wifi issue.

After disabling secure boot, I had to reboot into Windows once to get wifi working again, and then I tried rebooting into Linux a couple of times. So far wifi has worked everytime.

Unfortunately, kernel 5.10 rc1 doesn't fix the bug for me (Lenovo Y530-15ICH with bios version 8JCN54WW released 06/15/2020). After several reboots the network keeps disconnecting,
However the solution presented by Pablo "options rtw88_pci disable_aspm=1" works with the ubuntu stock kernel (currently 5.8.0-26)

campus, does it work but flaky? Then it sounds like a different bug.

Can you please attach dmesg under v5.10?

Hi, Feng
Unfortunately, in my case, wifi crashes each time (at a random period of time from boot) with kernel 5.10 rc1 and rc2 and disable_aspm removed.
The good thing is that I can use the disable_aspm workaround which makes wifi stable.
I attached the error parts from dmesg.

campus,

Can you please attach full dmesg and `sudo lspci -vvnn`?

Hi, Feng
I've attached full dmesg and lspci -vvnn
The bug seems to manifest when the laptop is on battery power. I've made several boot cycles this evening with kernel 5.10 rc2. When the laptop is plugged in the network works fine. when the laptop is on battery power wifi crashes.

Does cold boot help when it's on battery power?

No. cold boot does not help. I tried it several times.

Campus, can you please try this patch series:
https://patchwork.kernel.org/project/linux-pci/list/?series=369933

Hi, Feng
Can you, please, give me some instructions on how to download and run the code from these patches?
Thank you!

Hi, please test this kernel:
https://people.canonical.com/~khfeng/aspm-l1-fix/

Hi, Feng
Tested and the error still appears. I'm starting to think it has something to do with my laptop in particular. Dmesg attached.

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed-groovy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Campus,

You might need some other series like this:
https://<email address hidden>/

This bug was fixed in the package linux - 5.8.0-31.33

---------------
linux (5.8.0-31.33) groovy; urgency=medium

  * groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)

  * Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
    - drm/i915: Mark ininitial fb obj as WT on eLLC machines to avoid rcu lockup
      during fbdev init

  * CVE-2020-4788
    - selftests/powerpc: rfi_flush: disable entry flush if present
    - powerpc/64s: flush L1D on kernel entry
    - powerpc/64s: flush L1D after user accesses
    - selftests/powerpc: entry flush test

linux (5.8.0-30.32) groovy; urgency=medium

  * groovy/linux: 5.8.0-30.32 -proposed tracker (LP: #1903194)

  * Update kernel packaging to support forward porting kernels (LP: #1902957)
    - [Debian] Update for leader included in BACKPORT_SUFFIX

  * Avoid double newline when running insertchanges (LP: #1903293)
    - [Packaging] insertchanges: avoid double newline

  * EFI: Fails when BootCurrent entry does not exist (LP: #1899993)
    - efivarfs: Replace invalid slashes with exclamation marks in dentries.

  * raid10: Block discard is very slow, causing severe delays for mkfs and
    fstrim operations (LP: #1896578)
    - md: add md_submit_discard_bio() for submitting discard bio
    - md/raid10: extend r10bio devs to raid disks
    - md/raid10: pull codes that wait for blocked dev into one function
    - md/raid10: improve raid10 discard request
    - md/raid10: improve discard request for far layout
    - dm raid: fix discard limits for raid1 and raid10
    - dm raid: remove unnecessary discard limits for raid10

  * Bionic: btrfs: kernel BUG at /build/linux-
    eTBZpZ/linux-4.15.0/fs/btrfs/ctree.c:3233! (LP: #1902254)
    - btrfs: extent_io: do extra check for extent buffer read write functions
    - btrfs: extent-tree: kill BUG_ON() in __btrfs_free_extent()
    - btrfs: extent-tree: kill the BUG_ON() in insert_inline_extent_backref()
    - btrfs: ctree: check key order before merging tree blocks

  * Tiger Lake PMC core driver fixes (LP: #1899883)
    - platform/x86: intel_pmc_core: update TGL's LPM0 reg bit map name
    - platform/x86: intel_pmc_core: fix bound check in pmc_core_mphy_pg_show()
    - platform/x86: pmc_core: Use descriptive names for LPM registers
    - platform/x86: intel_pmc_core: Fix TigerLake power gating status map
    - platform/x86: intel_pmc_core: Fix the slp_s0 counter displayed value

  * drm/i915/dp_mst - System would hang during the boot up. (LP: #1902469)
    - Revert "UBUNTU: SAUCE: drm/i915/display: Fix null deref in
      intel_psr_atomic_check()"
    - drm/i915: Fix encoder lookup during PSR atomic check

  * Undetected Data corruption in MPI workloads that use VSX for reductions on
    POWER9 DD2.1 systems (LP: #1902694)
    - powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load emulation
    - selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
      workaround

  * [20.04 FEAT] Support/enhancement of NVMe IPL (LP: #1902179)
    - s390/ipl: support NVMe IPL kernel parameters

  * uvcvideo: add mapping for HEVC payloads (LP: #1895803)
    - media: uvcvideo: Add mapping for HEVC payloads

  * risc-v 5.8 ...

This bug is also on ASUS FX505DT TUF GAMING LAPTOP , kernel is 5.8.0-50-generic
The error is mostly
"rtw_8822be pci bus timeout,check dma status"
Wifi disconnects if connected sometimes
Or many times no Wi-Fi in settings
No adapter found
Its a dual booted system with Win10 and Ubuntu 20.04.2 LTS

This is present on ASUS K570U-ES76

OS:Ubuntu 20.04.4
Kernel: 5.13.0-35-generic

- Device will drop wifi and then spam "rtw_8822be pci bus timeout,check dma status" in the logs
- Rebooting fixes issue

This is a fairly old laptop and with the wifi 6 modules being >$20 I'll probably just go for the upgrade.

This is present on ASUS TUF A15 FA506 nn

OS:Ubuntu 20.04.4
Kernel: 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Wifi drops after a few minutes, sometimes longer, depending on inactivity.
dmesg error was: ...... failed to read ASPM, ret=-5

It seems that this fixes it for me:

echo "options rtw88_pci disable_aspm=1" | sudo tee /etc/modprobe.d/rtw88_pci.conf

check:
cat /etc/modprobe.d/rtw88_pci.conf
options rtw88_pci disable_aspm=1

Additionally one could try to change powersave mode in NetworkManager:

cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
[connection]
wifi.powersave = 2

#A setting of "0" will totally disable power saving features in the WiFi adapter.
#A setting of "2" or "1" will be less aggressive, but still leave power saving enabled.
### oroginally 3
#wifi.powersave = 3

The above is sadly false, a bit better, wifi lasts a bit longer but still fails after a while.

I experienced the bug on my Lenovo IdeaPad L340-17IWL with Ubuntu 20.04 up to date and a Realtech rtw_8821ce.
I spend hours to try to find a setting, practicing the Computer Assisted Waste of Time.
I bought an external wifi dongle with another Realtech 81... chip (I've not it at hand now) and experienced also the failure of the wifi after some times.
As said by delfi above. I still experience the bug after a while after a fresh install of Ubuntu 22.04.
More than 2 years that the bug is known...

And still no joy with the latest 20.04.x kernel
5.13.0-44-generic #49~20.04.1-Ubuntu SMP Wed May 18 18:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

586125.765621] rtw_8822ce 0000:03:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[586183.004088] rtw_8822ce 0000:03:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[586183.004105] rtw_8822ce 0000:03:00.0: mac power on failed
[586183.004109] rtw_8822ce 0000:03:00.0: failed to power on mac
[586183.004112] rtw_8822ce 0000:03:00.0: leave idle state failed
[586183.004375] rtw_8822ce 0000:03:00.0: failed to leave ips state
[586183.004383] rtw_8822ce 0000:03:00.0: failed to leave idle state

I'm kinda ok with writing LKMs, but opted for an USB stick as well. Defeat. Sad.

Please file a new bug, thanks!