Realtek RTL8822BE Wifi interface disappears randomly

Hi! I have a problem with disappearing wifi interface, it happens once per few hours. Only reboot helps.

Here is my system:

inxi --admin --verbosity=7 --filter --width
System:
  Kernel: 6.0.6-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.0-x86_64
    root=UUID=10456b6e-a634-4609-ab49-e9dd374942c0 rw quiet
    resume=UUID=46b9a338-1113-4df8-b0a9-3c82db3b07ca
    usbcore.usbfs_memory_mb=128
  Desktop: KDE Plasma v: 5.26.2 tk: Qt v: 5.15.6 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: X411UN v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X411UN v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: X411UN.310 date: 04/17/2019
Battery:
  ID-1: BAT0 charge: 41.4 Wh (98.3%) condition: 42.1/42.1 Wh (100.0%)
    volts: 11.5 min: 11.5 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: not charging cycles: 1
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M185/M225
    serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  RAM: total: 15.51 GiB used: 5.22 GiB (33.6%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-8250U bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 8 level: v3 note: check built: 2017 process: Intel 14nm family: 6
    model-id: 0x8E (142) stepping: 0xA (10) microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 400/3400 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 bogomips: 28808
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor
    movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm
    pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp
    rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
    syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi
    vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5917
    class-ID: 0300
  Device-2: NVIDIA GP108M [GeForce MX150] vendor: ASUSTeK driver: nvidia
    v: 520.56.06 alternate: nouveau,nvidia_drm non-free: 520.xx+
    status: current (as of 2022-10) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 4
    link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1d10
    class-ID: 0302
  Device-3: IMC Networks VGA UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-6:3 chip-ID: 13d3:5a07 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.4
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: BOE Display 0x06f3 built: 2016 res: 1920x1080
    hz: 57 dpi: 158 gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9")
    ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 22.2.1 renderer: Mesa Intel UHD Graphics 620 (KBL
    GT2) direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_soc_avs
    bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
  Sound API: ALSA v: k6.0.6-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.21 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.59 running: yes
Network:
  Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: AzureWave
    driver: rtw_8822be v: N/A modules: rtw88_8822be pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 10ec:b822 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 1-8:4 chip-ID: 13d3:3526 class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 238.47 GiB used: 114.9 GiB (48.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Micron model: 1100 MTFDDAV256TBN
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: A020 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 39.06 GiB size: 38.15 GiB (97.67%) used: 27.52 GiB (72.1%)
    fs: ext4 dev: /dev/sda5 maj-min: 8:5 label: N/A
    uuid: 10456b6e-a634-4609-ab49-e9dd374942c0
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
    used: 26.5 MiB (10.4%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: SYSTEM
    uuid: 7ADF-0389
  ID-3: /home raw-size: 135.74 GiB size: 132.55 GiB (97.65%)
    used: 87.36 GiB (65.9%) fs: ext4 dev: /dev/sda6 maj-min: 8:6 label: N/A
    uuid: 0aaf16cb-135c-445a-a626-a51615827b09
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 3.91 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda7 maj-min: 8:7 label: N/A
    uuid: 46b9a338-1113-4df8-b0a9-3c82db3b07ca
Unmounted:
  ID-1: /dev/sda2 maj-min: 8:2 size: 16 MiB fs: <superuser required> label: N/A
    uuid: N/A
  ID-2: /dev/sda3 maj-min: 8:3 size: 58.71 GiB fs: ntfs label: OS
    uuid: 7660E24560E20C25
  ID-3: /dev/sda4 maj-min: 8:4 size: 800 MiB fs: ntfs label: RECOVERY
    uuid: E838B5DB38B5A8C8
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-4:2 info: Logitech Unifying Receiver type: Mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s
    power: 98mA chip-ID: 046d:c52f class-ID: 0300
  Device-2: 1-6:3 info: IMC Networks VGA UVC WebCam type: Video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 13d3:5a07 class-ID: 0e02 serial: <filter>
  Device-3: 1-8:4 info: IMC Networks Bluetooth Radio type: Bluetooth
    driver: btusb interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 500mA
    chip-ID: 13d3:3526 class-ID: e001 serial: <filter>
  Hub-2: 2-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 52.0 C pch: 44.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 3600
Info:
  Processes: 251 Uptime: 21m wakeups: 3 Init: systemd v: 251 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 1809
  pm: pacman pkgs: 1791 libs: 465 tools: pamac pm: flatpak pkgs: 0 pm: snap
  pkgs: 18 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.23

and sudo dmesg | grep rtw_8822be

[    6.152012] rtw_8822be 0000:02:00.0: Firmware version 27.2.0, H2C version 13
[    6.152047] rtw_8822be 0000:02:00.0: enabling device (0000 -> 0003)
[    6.222268] rtw_8822be 0000:02:00.0 wlp2s0: renamed from wlan0
[    6.295430] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[    6.295436] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[    6.295444] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[    7.536031] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[    7.536037] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[    7.536043] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[    7.660274] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[    7.660278] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[    7.660284] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[   33.419576] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   33.419582] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[   33.419589] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[   33.585088] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   33.585097] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[   33.585107] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[   34.029454] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   34.029464] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[   34.029476] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[   34.648562] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   34.648573] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[   34.648585] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[   35.119720] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   35.119732] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[   35.119744] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[   35.397799] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   35.397811] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[   35.397826] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[  216.293554] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  216.293561] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[  216.293570] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[  431.282369] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  431.282376] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[  431.282385] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[  820.262315] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  820.262323] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[  820.262331] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[  835.999128] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  835.999130] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[  835.999133] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[  903.223749] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  903.223756] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[  903.223765] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1002.735376] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1002.735383] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1002.735391] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1041.525489] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1041.525498] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1041.525506] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1080.231358] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1080.231366] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1080.231374] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1082.557259] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1082.557263] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1082.557268] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1222.468103] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1222.468113] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1222.468125] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1225.018627] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1225.018629] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1225.018632] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1242.985202] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1242.985212] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1242.985223] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1271.806606] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1271.806610] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1271.806614] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1343.562798] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1343.562806] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1343.562815] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1356.242576] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1356.242584] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1356.242593] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1437.043619] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1437.043626] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1437.043635] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)
[ 1460.527454] rtw_8822be 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 1460.527457] rtw_8822be 0000:02:00.0:   device [10ec:b822] error status/mask=00000001/00006000
[ 1460.527459] rtw_8822be 0000:02:00.0:    [ 0] RxErr                  (First)

I think it’s been happening since last few kernels, but I don’t remember which exactly kernel version it was. Could you help me with fixing it, so I can use the newest kernel version?

Hi @mskr,

Is there any specific reason you want to use the latest kernel and not, for example, version 5.15, the latest LTS?

Not really, I just think that newest kernel will bring me the best performance.

Well, actually it’s recommended (at least by me) to stick to an LTS kernel. There’s a reason non-LTS kernels were originally called experimental. :wink:

OK, switched back to 5.15, checking if the problem exists on this version.

1 Like

After few days got the same problem (using kernel 5.15), some more logs from dmesg:

[81313.860312] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0  
[81313.861318] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5  
[81316.863655] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5  
[81318.863683] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0  
[81318.863696] rtw_8822be 0000:02:00.0: mac power on failed  
[81318.863697] rtw_8822be 0000:02:00.0: failed to power on mac  
[81318.863698] rtw_8822be 0000:02:00.0: leave idle state failed  
[81318.863873] rtw_8822be 0000:02:00.0: failed to leave ips state  
[81318.863874] rtw_8822be 0000:02:00.0: failed to leave idle state  
[81318.864097] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[0]  
[81318.864305] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[1]  
[81318.864508] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[2]  
[81318.864712] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[3]  
[81318.864915] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[5]  
[81318.865110] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[6]  
[81318.865320] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[0]  
[81318.865515] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[1]  
[81318.865718] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[2]  
[81318.865921] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[3]  
[81318.866111] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[5]  
[81318.866310] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[6]  
[81320.815075] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[0]  
[81320.815319] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[1]  
[81320.815534] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[2]  
[81320.815748] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[3]  
[81320.815961] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[5]  
[81320.816175] rtw_8822be 0000:02:00.0: timed out to flush pci tx ring[6]  
[81322.816250] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0  
[81322.817030] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5  
[81322.817048] rtw_8822be 0000:02:00.0: stop vif 80:c5:f2:12:06:6d on port 0  
[81324.817043] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0  
[81326.818433] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0  
[81326.818446] rtw_8822be 0000:02:00.0: mac power on failed  
[81326.818448] rtw_8822be 0000:02:00.0: failed to power on mac

Testing kernel 5.10 now…

Solved the issue. It turned out that it had nothing with kernel version. It was a hardware issue. I had a problem with turning off wifi or even whole laptop while pressing harder CTRL key :upside_down_face: I’ve realized this recently. My solution was to use some isolation tape in between mother board and CTRL key. If you’re interested, I created a tweet with pictures: https://twitter.com/mskrzypkows/status/1591545246336405504?s=20&t=oDr1UKhysxhvr5OkEVvnKw
My laptop works fine now, even with 6.0.x kernel.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.