I have an Ssus vivobook pro 15 with ubuntu 20.04 (dual boot with win10). Wifi driver work very well (wifi, bluetooth, e.t.c.) with kernel 5.15.xxx but after suspend, wifi does not work anymore. I tried various solutions, such as reloading the kernel module (mt7921e), restarting the network service, disable power management for wifi card, disable fastboot on windows, without any result. The system became partially irresponsible and does not reboot from the software, the only solution is to force the laptop to stop by holding down the power button for a longer time. With kernel 5.11.xxx bluetooth and wifi not work, so this is why i try to use another kernel.
Created attachment 300239 [details] dmesg
Created attachment 300240 [details] kernel log
Created attachment 301378 [details] mt7921e crash in suspend mode I have Asus VivoBook pro 15 and confirm it.
(In reply to Charlie from comment #3) > Created attachment 301378 [details] > mt7921e crash in suspend mode > > I have Asus VivoBook pro 15 and confirm it. I checked this on Linux arch 5.19.0-rc5-1-mainline and linux-firmware=20220708.be7798e
Created attachment 303340 [details] dmesg-6.1-rc4 Manjaro Linux, Kernel 6.1-rc4, linux-firmware-20221109.60310c2-1, AMD 5800H Inspite of changes in MT7921 driver https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/net/wireless/mediatek/mt76/mt7921?h=v6.1-rc4, bug still exists.
Arch Linux on a desktop computer with an Aorus B650 elite Ax motherboard with this wireless chipset has the exact same issue. Tested with all 6.2.x kernels and also on the latest 6.3 and 6.3.1 kernels. Not uploading any dmesg because as far as i can see the logs are the same as the guys above (driver own failed, chip reset failed). In my case the chip reset keeps going in a loop and the computer becomes unresponsive after waking up from suspend. Bluetooth won't work aswell.
I have casually tried to disable Wi-Fi from NetworkManager before going to suspend (Bluetooth still left enabled) and successfully resumed without issues. I don't know if it could be related to having both Wi-Fi and Bluetooth enabled after suspend racing somehow (i use both a bluetooth keyboard and mouse).