No, unfortunately this patch does not work for ASUS Vivobook 16X
K3605ZU.

Even worse, the full reboot takes just a bit more than 20 seconds,
while waking up from suspend before everything dark starts to give any sign of 
activity
(except of a tiny LED on the side that responds immediately after key press)
takes 75 seconds. :(

it uses the following HW:

Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network 
Adapter
VGA compatible controller: NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / 
Mobile] (rev a1)
VGA compatible controller: Intel Corporation Alder Lake-P GT2 [Iris Xe 
Graphics] (rev 0c)

a message in syslog which talks about problem with network device:

2024-09-06T11:47:08.538866+02:00 buchlovice kernel: printk: Suspending 
console(s) (use no_console_suspend to debug)
2024-09-06T11:47:08.538869+02:00 buchlovice kernel: ACPI: EC: interrupt blocked
2024-09-06T11:47:08.538870+02:00 buchlovice kernel: ACPI: EC: interrupt 
unblocked
2024-09-06T11:47:08.538922+02:00 buchlovice kernel: pcieport 0000:00:1c.0: 
broken device, retraining non-functional downstream link at 2.5GT/s
2024-09-06T11:47:08.538923+02:00 buchlovice kernel: pcieport 0000:00:1c.0: 
retraining failed
2024-09-06T11:47:08.538925+02:00 buchlovice kernel: pcieport 0000:00:1c.0: 
broken device, retraining non-functional downstream link at 2.5GT/s
2024-09-06T11:47:08.538926+02:00 buchlovice kernel: pcieport 0000:00:1c.0: 
retraining failed
2024-09-06T11:47:08.538927+02:00 buchlovice kernel: pci 0000:2c:00.0: not ready 
1023ms after resume; waiting
2024-09-06T11:47:08.538928+02:00 buchlovice kernel: pci 0000:2c:00.0: not ready 
2047ms after resume; waiting
2024-09-06T11:47:08.538929+02:00 buchlovice kernel: pci 0000:2c:00.0: not ready 
4095ms after resume; waiting
2024-09-06T11:47:08.538930+02:00 buchlovice kernel: pci 0000:2c:00.0: not ready 
8191ms after resume; waiting
2024-09-06T11:47:08.538931+02:00 buchlovice kernel: pci 0000:2c:00.0: not ready 
16383ms after resume; waiting
2024-09-06T11:47:08.538932+02:00 buchlovice kernel: nvme nvme0: I/O tag 896 
(9380) QID 5 timeout, completion polled
2024-09-06T11:47:08.538933+02:00 buchlovice kernel: pci 0000:2c:00.0: not ready 
32767ms after resume; waiting
2024-09-06T11:47:08.538935+02:00 buchlovice kernel: pci 0000:2c:00.0: not ready 
65535ms after resume; giving up
2024-09-06T11:47:08.538936+02:00 buchlovice kernel: pci 0000:2c:00.0: Unable to 
change power state from D3cold to D0, device inaccessible
2024-09-06T11:47:08.538937+02:00 buchlovice kernel: i915 0000:00:02.0: [drm] 
GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
2024-09-06T11:47:08.538938+02:00 buchlovice kernel: i915 0000:00:02.0: [drm] 
GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
2024-09-06T11:47:08.538939+02:00 buchlovice kernel: i915 0000:00:02.0: [drm] 
GT0: HuC: authenticated for all workloads
2024-09-06T11:47:08.538939+02:00 buchlovice kernel: i915 0000:00:02.0: [drm] 
GT0: GUC: submission enabled
2024-09-06T11:47:08.538940+02:00 buchlovice kernel: i915 0000:00:02.0: [drm] 
GT0: GUC: SLPC enabled
2024-09-06T11:47:08.538941+02:00 buchlovice kernel: i915 0000:00:02.0: [drm] 
GT0: GUC: RC enabled
2024-09-06T11:47:08.538943+02:00 buchlovice kernel: fbcon: Taking over console
2024-09-06T11:47:08.538944+02:00 buchlovice kernel: mei_hdcp 
0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops 
i915_hdcp_ops [i915])
2024-09-06T11:47:08.538945+02:00 buchlovice kernel: mei_pxp 
0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops 
i915_pxp_tee_component_ops [i915])
2024-09-06T11:47:08.538947+02:00 buchlovice kernel: Console: switching to 
colour frame buffer device 240x75
2024-09-06T11:47:08.538948+02:00 buchlovice kernel: OOM killer enabled.
2024-09-06T11:47:08.542329+02:00 buchlovice kernel: Restarting tasks ... done.
2024-09-06T11:47:08.542356+02:00 buchlovice kernel: random: crng reseeded on 
system resumption
2024-09-06T11:47:08.547301+02:00 buchlovice rtkit-daemon[1983]: The canary 
thread is apparently starving. Taking action.
2024-09-06T11:47:08.547649+02:00 buchlovice systemd-resolved[1037]: Clock 
change detected. Flushing caches.
2024-09-06T11:47:08.547759+02:00 buchlovice rtkit-daemon[1983]: Demoting known 
real-time threads.
2024-09-06T11:47:08.547895+02:00 buchlovice [2452]: Service not used for 60 
seconds. Shutting down..
2024-09-06T11:47:08.548037+02:00 buchlovice rtkit-daemon[1983]: Successfully 
demoted thread 3956 of process 3704.
2024-09-06T11:47:08.548204+02:00 buchlovice systemd[1]: geoclue.service: 
Deactivated successfully.
2024-09-06T11:47:08.548682+02:00 buchlovice rtkit-daemon[1983]: Successfully 
demoted thread 2603 of process 2558.
2024-09-06T11:47:08.548880+02:00 buchlovice rtkit-daemon[1983]: Successfully 
demoted thread 2558 of process 2558.
2024-09-06T11:47:08.549079+02:00 buchlovice rtkit-daemon[1983]: Successfully 
demoted thread 2594 of process 2552.
2024-09-06T11:47:08.549285+02:00 buchlovice rtkit-daemon[1983]: Successfully 
demoted thread 2595 of process 2556.
2024-09-06T11:47:08.549467+02:00 buchlovice rtkit-daemon[1983]: Successfully 
demoted thread 2556 of process 2556.
2024-09-06T11:47:08.549563+02:00 buchlovice systemd[1]: 
NetworkManager-dispatcher.service: Deactivated successfully.
2024-09-06T11:47:08.549643+02:00 buchlovice rtkit-daemon[1983]: Successfully 
demoted thread 2599 of process 2551.
2024-09-06T11:47:08.549715+02:00 buchlovice rtkit-daemon[1983]: Successfully 
demoted thread 2551 of process 2551.
2024-09-06T11:47:08.549787+02:00 buchlovice rtkit-daemon[1983]: Demoted 8 
threads.
2024-09-06T11:47:08.550877+02:00 buchlovice systemd-sleep[4730]: System 
returned from sleep operation 'suspend'.
2024-09-06T11:47:08.551304+02:00 buchlovice kernel: PM: suspend exit
2024-09-06T11:47:08.558294+02:00 buchlovice kernel: mt7921e 0000:2c:00.0: 
Unable to change power state from D3cold to D0, device inaccessible

...

2024-09-06T11:47:09.621420+02:00 buchlovice kernel: mt7921e 0000:2c:00.0: 
driver own failed
2024-09-06T11:47:09.621457+02:00 buchlovice kernel: mt7921e: probe of 
0000:2c:00.0 failed with error -5
2024-09-06T11:47:09.625014+02:00 buchlovice (udev-worker)[4801]: mt7921e: 
/etc/udev/rules.d/99-rz608.rules:1 Failed to write 
ATTR{/sys/bus/pci/drivers/mt7921e/new_id}, ignoring: File exists

//this last udev-worker message appears also in regular restart, which
normally contains:

2024-09-06T11:50:43.832317+02:00 buchlovice kernel: mt7921e 0000:2c:00.0: 
enabling device (0000 -> 0002)
2024-09-06T11:50:43.832317+02:00 buchlovice kernel: mt7921e 0000:2c:00.0: ASIC 
revision: 79220010 
...
2024-09-06T11:50:43.832327+02:00 buchlovice kernel: mt7921e 0000:2c:00.0: HW/SW 
Version: 0x8a108a10, Build Time: 20240219103244a
...
2024-09-06T11:50:43.832331+02:00 buchlovice kernel: mt7921e 0000:2c:00.0: WM 
Firmware Version: ____000000, Build Time: 20240219103337
...
2024-09-06T11:50:44.519913+02:00 buchlovice NetworkManager[1232]: <info>  
[1725616244.5198] rfkill3: found Wi-Fi radio killswitch (at 
/sys/devices/pci0000:00/0000:00:1c.0/0000:2c:00.0/ieee80211/phy0/rfkill3) 
(driver mt7921e)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2059744

Title:
  kernel bug 6.8.0-11 Ubuntu 24.04 with MT7921

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Noble Numbat (development branch) x86_64 
  The problem is this: there is an error with the Wi-Fi driver MT7921
  [  825.412953] mt7921e 0000:04:00.0: Message 00020007 (seq 8) timeout
  [  825.413273] mt7921e 0000:04:00.0: PM: dpm_run_callback(): 
pci_pm_resume+0x0/0x110 returns -110
  [  825.413296] mt7921e 0000:04:00.0: PM: failed to resume async: error -110

  And I found a ready-made patch for it that solves the problem
  https://github.com/ShadowBlip/rz608-fix

  And after this simple script the problem disappears
  I'll attach the logs before and after I made this patch.
  Add this solution to your distribution. Better yet, contact the people who 
are responsible for the kernel and add it there so that it is global and 
applies to all distributions, because I noticed the same thing in Fedora.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059744/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to