zenbook q407iq (r5 4500U, MX350) not waking up from sleep(s2idle)

wyj1017146866wyj1017146866 Level 1
edited November 2020 in ZenBook
  1. System: linux 5.7.7, and windows 10 2004
  2. Battery or AC: both
  3. Model: q407iq
  4. Frequency of occurrence: nearly always
  5. Reset OS: tried several times
  6. Screenshot or video: not possible to make it a screenshot

========================

Detailed description:

System cannot weak up from sleep on keyboard or mouse interruption. Opening the lid may weak it up, but it does not always work.

«1

Comments

  • log when trying to suspend (and resume)


    Jul 11 04:36:47 user systemd[1]: Reached target Sleep.

    Jul 11 04:36:47 user systemd[1]: Starting Suspend...

    Jul 11 04:36:47 user systemd-sleep[1302]: Suspending system...

    Jul 11 04:36:47 user kernel: PM: suspend entry (s2idle)

    Jul 11 04:38:26 user kernel: Filesystems sync: 0.005 seconds

    Jul 11 04:38:26 user kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.

    Jul 11 04:38:26 user kernel: OOM killer disabled.

    Jul 11 04:38:26 user kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.

    Jul 11 04:38:26 user kernel: printk: Suspending console(s) (use no_console_suspend to debug)

    Jul 11 04:38:26 user kernel: wlp2s0: deauthenticating from 6c:ae:f6:0e:ba:08 by local choice (Reason: 3=DEAUTH_LEAVING)

    Jul 11 04:38:26 user kernel: [drm] [Link 0] WARNING MOD_HDCP_STATUS_DISPLAY_NOT_FOUND IN STATE HDCP_UNINITIALIZED STAY COUNT 0

    Jul 11 04:38:26 user kernel: ACPI: EC: interrupt blocked

    Jul 11 04:38:26 user kernel: xhci_hcd 0000:04:00.4: refused to change power state from D0 to D3hot

    Jul 11 04:38:26 user kernel: ACPI: EC: interrupt unblocked

    Jul 11 04:38:26 user kernel: ------------[ cut here ]------------

    Jul 11 04:38:26 user kernel: WARNING: CPU: 3 PID: 1302 at kernel/irq/chip.c:210 irq_startup+0xe1/0xf0

    Jul 11 04:38:26 user kernel: Modules linked in: cmac ccm joydev rtsx_usb_sdmmc rtsx_usb_ms mousedev mmc_core memstick asus_nb_wmi edac_mce_amd hid_multitouch asus_wmi hid_generic sparse_keymap kvm_amd wmi_bmof kvm rtsx_usb irqbypass crct10dif_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper input_leds amdgpu snd_hda_codec_realtek iwlmvm snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi mac80211 k10temp sp5100_tco snd_hda_intel libarc4 i2c_piix4 snd_intel_dspcfg snd_hda_codec snd_hda_core gpu_sched i2c_algo_bit snd_hwdep uvcvideo ttm iwlwifi snd_pcm videobuf2_vmalloc btusb drm_kms_helper btrtl videobuf2_memops videobuf2_v4l2 btbcm btintel videobuf2_common bluetooth cec snd_timer videodev rc_core syscopyarea snd cfg80211 sysfillrect mc sysimgblt ecdh_generic ecc snd_pci_acp3x tpm_crb crc16 soundcore ccp fb_sys_fops tpm_tis rfkill wmi ac tpm_tis_core evdev tpm i2c_hid hid battery mac_hid rng_core acpi_cpufreq pinctrl_amd nls_iso8859_1 nls_cp437 vfat fat drm agpgart

    Jul 11 04:38:26 user kernel: ip_tables x_tables serio_raw atkbd libps2 crc32_pclmul xhci_pci xhci_hcd i8042 serio f2fs

    Jul 11 04:38:26 user kernel: CPU: 3 PID: 1302 Comm: systemd-sleep Not tainted 5.7.7-arch1-1 #1

    Jul 11 04:38:26 user kernel: Hardware name: ASUSTeK COMPUTER INC. ZenBook UX434IQ_Q407IQ/UX434IQ, BIOS UX434IQ_Q407IQ.300 04/14/2020

    Jul 11 04:38:26 user kernel: RIP: 0010:irq_startup+0xe1/0xf0

    Jul 11 04:38:26 user kernel: Code: f6 4c 89 e7 e8 00 45 00 00 85 c0 75 21 4c 89 e7 31 d2 4c 89 ee e8 bf c8 ff ff 48 89 ef e8 b7 fe ff ff 41 89 c4 e9 51 ff ff ff <0f> 0b eb b6 0f 0b eb b2 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48

    Jul 11 04:38:26 user kernel: RSP: 0018:ffffa52586a4fd90 EFLAGS: 00010002

    Jul 11 04:38:26 user kernel: RAX: 0000000000000140 RBX: 0000000000000001 RCX: 0000000000000140

    Jul 11 04:38:26 user kernel: RDX: 0000000000000004 RSI: ffffffffad364b60 RDI: ffff8e87a5800418

    Jul 11 04:38:26 user kernel: RBP: ffff8e87a5800400 R08: 0000000000000000 R09: 0000000000000140

    Jul 11 04:38:26 user kernel: R10: 0000000000000000 R11: ffffffffad2546c8 R12: 0000000000000001

    Jul 11 04:38:26 user kernel: R13: ffff8e87a5800418 R14: ffff8e87a58004e4 R15: 0000000000000000

    Jul 11 04:38:26 user kernel: FS: 00007f82a36e1a80(0000) GS:ffff8e87a76c0000(0000) knlGS:0000000000000000

    Jul 11 04:38:26 user kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

    Jul 11 04:38:26 user kernel: CR2: 0000558867693f88 CR3: 00000001caf58000 CR4: 0000000000340ee0

    Jul 11 04:38:26 user kernel: Call Trace:

    Jul 11 04:38:26 user kernel: resume_irqs+0xb6/0xf0

    Jul 11 04:38:26 user kernel: dpm_resume_noirq+0xf/0x20

    Jul 11 04:38:26 user kernel: suspend_devices_and_enter+0x338/0x8a0

    Jul 11 04:38:26 user kernel: pm_suspend.cold+0x333/0x387

    Jul 11 04:38:26 user kernel: state_store+x42/0x90

    Jul 11 04:38:26 user kernel: kernfs_fop_write+0xce/0x1b0

    Jul 11 04:38:26 user kernel: vfs_write+0xb6/0x1a0

    Jul 11 04:38:26 user kernel: ksys_write+0x67/0xe0

    Jul 11 04:38:26 user kernel: do_syscall_64+0x49/0x90

    Jul 11 04:38:26 user kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9

    Jul 11 04:38:26 user kernel: RIP: 0033:0x7f82a4647b57

    Jul 11 04:38:26 user kernel: Code: 0c 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24

    Jul 11 04:38:26 user kernel: RSP: 002b:00007ffe8870b658 EFLAGS: 00000246 ORIG_RAX: 0000000000000001

    Jul 11 04:38:26 user kernel: RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f82a4647b57

    Jul 11 04:38:26 user kernel: RDX: 0000000000000004 RSI: 00007ffe8870b740 RDI: 0000000000000004

    Jul 11 04:38:26 user kernel: RBP: 00007ffe8870b740 R08: 000055886768da90 R09: 000000000000000d

    Jul 11 04:38:26 user kernel: R10: 0000558867689c00 R11: 0000000000000246 R12: 0000000000000004

    Jul 11 04:38:26 user kernel: R13: 00005588676893c0 R14: 0000000000000004 R15: 00007f82a4718700

    Jul 11 04:38:26 user kernel: ---[ end trace 61adf69b75a7cc3f ]---

    Jul 11 04:38:26 user kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).

    Jul 11 04:38:26 user kernel: [drm] PSP is resuming...

    Jul 11 04:38:26 user kernel: sos fw version = 0x11003f.

    Jul 11 04:38:26 user kernel: [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR

    Jul 11 04:38:26 user kernel: SMU is resuming...

    Jul 11 04:38:26 user kernel: dpm has been disabled

    Jul 11 04:38:26 user kernel: SMU is resumed successfully!

    Jul 11 04:38:26 user kernel: ata2: SATA link down (SStatus 0 SControl 300)

    Jul 11 04:38:26 user kernel: ata1: SATA link down (SStatus 0 SControl 300)

    Jul 11 04:38:26 user kernel: [drm] kiq ring mec 2 pipe 1 q 0

    Jul 11 04:38:26 user kernel: [drm] DMUB hardware initialized: version=0x01000000

    Jul 11 04:38:26 user kernel: [drm] [Link 0] WARNING MOD_HDCP_STATUS_DISPLAY_NOT_FOUND IN STATE HDCP_UNINITIALIZED STAY COUNT 0

    Jul 11 04:38:26 user kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).

    Jul 11 04:38:26 user kernel: [drm] JPEG decode initialized successfully.

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring gfx uses VM inv eng 0 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring sdma0 uses VM inv eng 0 on hub 1

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring vcn_dec uses VM inv eng 1 on hub 1

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring vcn_enc0 uses VM inv eng 4 on hub 1

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring vcn_enc1 uses VM inv eng 5 on hub 1

    Jul 11 04:38:26 user kernel: amdgpu 0000:04:00.0: ring jpeg_dec uses VM inv eng 6 on hub 1

    Jul 11 04:38:26 user kernel: OOM killer enabled.

    Jul 11 04:38:26 user kernel: Restarting tasks ... done.

    Jul 11 04:38:26 user systemd-logind[320]: Power key pressed.

  • I have the same problem with Windows 10, Version 2004 (OS Build 19041.329). I have tried bios version 300 and 301, neither work. Powercfg -a shows that S0 is being used and that the computer does not support S3 sleep mode.

    If I wasn't past by 2 week return period from bestbuy, I would return this. Searching, this seems to be a common Asus problem that dates back a while.

    I have disabled sleep inside Windows 10, but during the night it still sleeps and I have to hard cycle the power to get it back on. Very annoying.

  • Dear both,

    May I know if the issue happen in Windows 1909?

    Was there any external device connected to it?

    Thank you.

  • wyj1017146866wyj1017146866 Level 1
    edited July 2020

    For me there is no extra device connected. I can also confirm that ACPI s3 is not supported.


    I didn't test windows 1909 thoroughly, but I did notice that the windows preistalled by asus seem to have the same problem. Just "seem to", since I didn't really use it.


    Actually the bug "ACPI s3 is not supported" should raise official attention somehow as well, since there will be users worrying about extra battery usage during sleep. However what bother me most is still that it cannot be waken up from sleep to idle.


    And to make it clear, I enabled every wakeup options under linux, even including wake-on-lan, but it still cannot be waken.


    Another thing I find strange is that I can hear the noise and feel the heat when it is supposed to be sleeping. This may indicate that kernel actually failed to make it sleep instead of failed to wake it up.


    The dmesg I put shows that sth may happen when calling resume_irqs, I am not sure whether it is related or not though. I hope that dmesg may help you debugging both on linux and windows.

  • Hello wyj1017146866,

    Please kindly rollback to 1909 and you are using BIOS 301 now?

    Thank you.

  • Not sure what happened to my previous comment. I still cannot see it.


    I mean it is still excellent for me with sleep disabled. So I am not rolling back to windows 1909.


    The bug appears with both bios 300 and 301, so for me bios 301 doesn't fix it.


    Since it is highly likely to be a bug on asus or amd, I am just reporting it so that you guys may be able to fix it one day. I don't care that much about sleeping.

  • To be honest, I would rather completely disable sleep than roll back to 1909. It is still excellent for me with sleep diabled.


    It appears on both bios 300 and bios 301. So 301 doesn't fix the problem.


    Anyway it is highly likely to be a bug either on asus or on AMD. I am just reporting that.

  • Hello wyj1017146866,

    Thank you for the feedback.

  • I came here to say I've returned like a few of these to best buy because they were all doing the same thing: keyboard not working sometimes when resuming from standby. Trackpad works. I think its a driver issue? I hope this can be fixed one day. I'm on windows 10 pro. For now, I have to restart.

  • I'm also experiencing this issue. Same exact model: zenbook 14 q407iq. After standby for a few minutes, the keyboard won't work so I need to reboot my device for the keyboard to work again. I used the Myasus app to update everything as well as the Windows update. I'm currently in version 2004. I just bought the laptop last week. So there's almost no other apps installed aside from chrome and microsoft office that may cause glitch in the system. I'm only using Windows Security as my antivirus. I think this is a bug issue. I hope Asus will release an update very soon or I'll return this unit and get a Lenovo or HP instead.

  • Exact same problem. Bought and open box and had keyboard stop working when computer went to sleep. Tried a new computer at the store. Exact same problem. PLEASE FIX THIS ASUS!

  • FWIW: The only way I've found to resolve this:

    1. Completely disable sleep & enable hibernation. That seems to work fine, just takes a bit longer to startup (thankfully not too much longer with with SSD). I think it's the best solution for now.
    2. Alternatively, enable both sleep & hibernation, then when the keyboard stops working after sleep use the trackpad to enter hibernation (I typically do this with Face login & then from Windows start menu). The keyboard will work again after hibernation.

    I hope this helps other and ASUS fixes this bug quickly.

  • Just adding that I've experience this exact same behavior. BIOS 300 & 301 don't resolve the problem.

  • wyj1017146866wyj1017146866 Level 1
    edited August 2020

    I rechecked the log I posted and, for me, I am still not sure what happened when suspending, but for resuming, it is highly likely that the display is not properly resumed.

    Besides, from @joshdmalone's solution 2, it is also highly likely to be display related: the system is actually on, however the display is still off.

    So there is probably a bug in display related part, which might be possible to fix by a bios update.

    So ASUS please do sth.

  • fireboyprfireboypr Level 1
    edited September 2020

    Hi, I've been having the exact same issues, almost every time I wake up the computer from sleep the keyboard doesn't work and about 10% of the time the screen back light also doesn't work but the computer does wakes up (I can see the camera lights blinking identifying me and logging me but screen completely dark) in this case I have to force shut down by pressing the power button for about 15 seconds. I have the latest BIOS upgrade 301 and all the latest drivers from the Asus website to date (9/1/20). Also I want to tray the solutions/workaround provided above but can't find how to enable hibernate (or any hibernate setting) anywhere. How do I enable Hibernation? thanks in advance.

    --Update-- I was able to enable hibernation. will be testing this workaround until the keyboard driver issue gets resolved.

  • Data mau update asus ke Android 9 gimama cara ya

  • I have this same error with zenbook um433iq with bios version 301. It wont suspend because something is blocking.

    Is there any information that I could provide for ASUS to solve this issue?

  • ux331un here. I see a lot of other zenbook users are facing the same issue.. Multiple thread are open everywhere.

    it looks like an issue with windows-BIOS-intel MEI-intel Graphic driver.

    My machine is basically unreliable and useless for a working environment since probably a year

    Asus is just ignoring the problem.. latest driver update is more than a year old. In the meanwhile windows version has been updated at least 4 times

  • according to Intel numbering :

    V26 drivers are for Windows® 10 May 2019 Update - WDDM 2.6.

    V27 drivers are for Windows® 10 May 2020 Update - WDDM 2.7 .

    Technically Asus as not yet released after 5 month a single V27 driver compatible with actual windows version

  • I installed Intel V27 drivers directly from their website, the drivers work fine but they don't solve the waking up problem.

This discussion has been closed.