[SOLVED] ASUS Vivobook freezes after SUSPEND (mt7921e driver problem)

[bicicleto]

Hello:

I recently bought an ASUS Vivobook PRO Oled, and I'm having several issues with it when installing Linux Mint. All of those resolved (wifi, sound, backlight problems) after upgrading the kernel (using 5.15.0-33-generic right now) but ONE REMAINS:

After suspending the computer, either closing the lid or clicking the suspend option in the mint menu, when the computer recovers this happens:
- Wifi is gone (doesn't detect any access points).
- Computer is VERY slow.
- When I reboot/shotdown in that state it takes a LOOOONG time, many processes take too much time closing.

I have read many posts about similar problems but I'm unable to solve it.

More info:

inxi -nn

Code: Select all

System:    Kernel: 5.15.0-33-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
           base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: ASUSTeK product: Vivobook_ASUSLaptop X3500PCB_K3500PC v: 1.0 serial: <filter> 
           Mobo: ASUSTeK model: X3500PCB v: 1.0 serial: <filter> UEFI: American Megatrends LLC. v: X3500PCB.301 
           date: 03/30/2022 
Battery:   ID-1: BAT0 charge: 34.0 Wh condition: 64.3/63.0 Wh (102%) model: ASUSTeK ASUS Battery status: Discharging 
CPU:       Topology: Quad Core model: 11th Gen Intel Core i5-11300H bits: 64 type: MT MCP arch: Tiger Lake rev: 1 
           L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 49766 
           Speed: 588 MHz min/max: 400/4400 MHz Core speeds (MHz): 1: 973 2: 1130 3: 1098 4: 834 5: 1072 6: 1072 7: 1160 
           8: 1148 
Graphics:  Device-1: Intel vendor: ASUSTeK driver: i915 v: kernel bus ID: 0000:00:02.0 
           Device-2: NVIDIA vendor: ASUSTeK driver: nvidia v: 510.73.05 bus ID: 0000:01:00.0 
           Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 21.2.6 direct render: Yes 
Audio:     Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 0000:00:1f.3 
           Sound Server: ALSA v: k5.15.0-33-generic 
Network:   Device-1: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel port: 3000 bus ID: 0000:2e:00.0 
           IF: wlo1 state: up mac: <filter> 
Drives:    Local Storage: total: 484.44 GiB used: 32.37 GiB (6.7%) 
           ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNU512GZ size: 476.94 GiB 
           ID-2: /dev/sda type: USB vendor: Generic model: SD MMC size: 7.50 GiB 
RAID:      Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd v: 0.6 bus ID: 0000:00:0e.0 
Partition: ID-1: / size: 118.38 GiB used: 32.32 GiB (27.3%) fs: ext4 dev: /dev/nvme0n1p6 
Sensors:   System Temperatures: cpu: 42.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 1900 
Info:      Processes: 278 Uptime: 35m Memory: 15.33 GiB used: 2.11 GiB (13.8%) Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 
           Shell: bash v: 5.0.17 inxi: 3.0.38 

lsusb

Code: Select all

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 003 Device 002: ID 13d3:5458 IMC Networks USB2.0 HD UVC WebCam
Bus 003 Device 004: ID 13d3:3563 IMC Networks Wireless_Device
Bus 003 Device 005: ID 0bda:0119 Realtek Semiconductor Corp. Storage Device (SD card reader)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lspci

Code: Select all

0000:00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01)
0000:00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01)
0000:00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
0000:00:06.0 PCI bridge: Intel Corporation Device 9a09 (rev 01)
0000:00:07.0 PCI bridge: Intel Corporation Device 9a23 (rev 01)
0000:00:08.0 System peripheral: Intel Corporation Device 9a11 (rev 01)
0000:00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01)
0000:00:0d.0 USB controller: Intel Corporation Device 9a13 (rev 01)
0000:00:0d.2 USB controller: Intel Corporation Device 9a1b (rev 01)
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller
0000:00:14.0 USB controller: Intel Corporation Device a0ed (rev 20)
0000:00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20)
0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20)
0000:00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20)
0000:00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20)
0000:00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
0000:00:1c.3 PCI bridge: Intel Corporation Device a0bb (rev 20)
0000:00:1d.0 System peripheral: Intel Corporation Device 09ab
0000:00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20)
0000:00:1f.3 Audio device: Intel Corporation Device a0c8 (rev 20)
0000:00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20)
0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20)
0000:01:00.0 3D controller: NVIDIA Corporation Device 25a2 (rev a1)
0000:2e:00.0 Network controller: MEDIATEK Corp. Device 7961
10000:e0:1d.0 PCI bridge: Intel Corporation Device a0b0 (rev 20)
10000:e1:00.0 Non-Volatile memory controller: Intel Corporation Device f1aa (rev 03)

Lastly: DMESG output when I
- boot Linux Mint
- suspend computer
- return from that suspension

https://drive.google.com/file/d/1YHk3Jz ... sp=sharing


Thank you for helping,

bicicleto

[SMG]

I recently bought an ASUS Vivobook PRO Oled, and I'm having several issues with it when installing Linux Mint. All of those resolved (wifi, sound, backlight problems) after upgrading the kernel (using 5.15.0-33-generic right now) but ONE REMAINS:

Welcome to the forum, bicicleto.

There are Wifi related errors in the dmesg you posted, so I'm not sure Wifi is working as well as it can. There were two call traces

Code: Select all

[    5.728371] UBSAN: invalid-load in /build/linux-hwe-5.15-scdIe0/linux-hwe-5.15-5.15.0/drivers/net/wireless/mediatek/mt76/dma.c:162:13
[    5.728373] load of value 34 is not a valid value for type '_Bool'

I do not know if that invalid load is part of the reason for the failure of the Wifi device to be able to switch from D3 (sleep) to D0 (working), but it is not changing according to the data you posted. Wifi is not working after suspend because it is not waking up.

Code: Select all

[   91.756602] mt7921e 0000:2e:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[   91.837951] mt7921e 0000:2e:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[   91.837952] PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -5
[   91.837957] mt7921e 0000:2e:00.0: PM: failed to resume async: error -5

If the Wifi keeps having [Trace] problems then that might be why your system seems slow.

I am not familiar with the specific Wifi card in your computer to know what options there are for fixing the issue.

[bicicleto]

Hi SMG, thank you for your help.

Reading other people with similar problems I did suspect something is wrong with the mt7921e driver.
I did try this:

1

Code: Select all

modprobe -r mt7921e

2

suspend the computer

3

Code: Select all

modprobe mt7921e

To see if that fixed the problem. It did not.

Any more ideas?

[SMG]

Any more ideas?

I will move your topic to the Networking section of the forum and add in the title "mt7921e driver problem". It is possible because your system is so new that you might need to use a newer kernel, but I do not normally help with network driver issues so maybe those who do will have better ideas.

[bicicleto]

Ok, thanks. I did try the 5.18 kernel, but everything remained the same. That one is the newest available kernel, is it?

[SMG]

Ok, thanks. I did try the 5.18 kernel, but everything remained the same. That one is the newest available kernel, is it?

I believe so.

[tankredus]

Original thread: viewtopic.php?t=376331

I'd changed wifi card to intel ax210 and then ax200, but the problem persisted. Bios update, 6.11 kernel...etc.
It is a PCI/suspend problem.
A workaround is to add a line to root crontab and reboot:
sudo crontab -e

Code: Select all

@reboot echo 0|tee /sys/bus/pci/devices/0000\:2e\:00.0/d3cold_allowed

It works with my intel ax200 so should also with the original mt7921.

Regards,

[Moem]

Mod note:
Post with solution was merged into the thread it belongs with.