Qubes 4.0 will not wake after sleep on ThinkPad W530

[JamesRBrown]

Qubes OS version: 4.0-rc3

Affected TemplateVMs:

---

Steps to reproduce the behavior:

1. Obtain a ThinkPad W530
2. Install Qubes 4.0-rc3 on it.
3. Boot the system into Qubes 4.0-rc3.
4. Close laptop lid to sleep system.
5. Open the laptop's lid and attempt to wake system.

Expected behavior:

The expected behavior is that the system will resume after sleep.

Actual behavior:

There are two behaviors.

1. The system will not wake from sleep, and hard power off is required.

2. The system reboots on wake.

General notes:

I'm running Qubes OS on 4.0-rc3 on a ThinkPad W530 and sleep does not work (or perhaps more accurately wake does not work). When I close the lid, the laptop indicates that it goes to sleep. Fans turn off, and the sleep light comes on. However, when I open the lid one of two behaviors occur...

Behavior 1: The laptop will not wake up. No amount of pressing keys or tapping the power button will wake the machine. Everything indicates the system is still in sleep mode, including a pulsing power ring light around the power button. In order to get the system to respond I have to hold the power button until the system powers down, then power back on.

Behavior 2: I open the lid, the indicator lights flash, and then go dark. As soon as I press the power button the system POSTs and begins booting.

NOTE 1: I have attempt to sleep the system about 15 times, and the above is the behavior every time. I haven't actually witnessed 4.0-rc3 successfully recover from sleep yet.

NOTE 2: I have a second W530 system, which I have also attempt this on, and witnessed the same behavior.

NOTE 3: As a point of comparison, when I replace the system drive with another drive (on the same system) containing Qubes release 3.2 R3.2 the system sleeps and wakes just fine. So this is a problem that's been introduced in the new 4.0 code. Of the 4.0 releases I have only used 4.0-rc3, so I can't comment on whether this issue has been present through the entire 4.0 release cycle. Also, between this observation and the one made in NOTE 2 we know this isn't a hardware issue.

---

Related issues:

[mcspadden]

I too have Behavior 1 on a Dell XPS 15 9560. Running 4.0 RC3 and everytime I close the lid or place it into Suspend mode via my username in the top right, the issue arises. Only a hard reboot will get Qubes running again. Should I submit a new issue because of the difference in devices or can the both exist in this open issue?

[mcspadden]

I too have Behavior 1 on a Dell XPS 15 9560. Running 4.0 RC3 and everytime I close the lid or place it into Suspend mode via my username in the top right, the issue arises. Only a hard reboot will get Qubes running again. Should I submit a new issue because of the difference in devices or can the both exist in this open issue?

[andrewdavidwong]

I too have Behavior 1 on a Dell XPS 15 9560. Running 4.0 RC3 and everytime I close the lid or place it into Suspend mode via my username in the top right, the issue arises. Only a hard reboot will get Qubes running again. Should I submit a new issue because of the difference in devices or can the both exist in this open issue?

Until we know more about the cause, it's fine to use the same issue as long as your reproduction steps and observed behavior are otherwise the same (i.e., same except for the hardware difference).

[andrewdavidwong]

I too have Behavior 1 on a Dell XPS 15 9560. Running 4.0 RC3 and everytime I close the lid or place it into Suspend mode via my username in the top right, the issue arises. Only a hard reboot will get Qubes running again. Should I submit a new issue because of the difference in devices or can the both exist in this open issue?

Until we know more about the cause, it's fine to use the same issue as long as your reproduction steps and observed behavior are otherwise the same (i.e., same except for the hardware difference).

[molnara]

I am having the exact issue after applying updates from the test repo. It was working fine before the updates. My laptop is an Asus Zenbook UX430U

Update: I did experience the reboot on opening the lid once after updating dom0, but it seems to always just stay suspended for me.

Update 2: Also, the updates from test repo did have a kernel update. I am guessing this is a kernel issue, but I'm not knowledgeable enough.

[molnara]

I am having the exact issue after applying updates from the test repo. It was working fine before the updates. My laptop is an Asus Zenbook UX430U

Update: I did experience the reboot on opening the lid once after updating dom0, but it seems to always just stay suspended for me.

Update 2: Also, the updates from test repo did have a kernel update. I am guessing this is a kernel issue, but I'm not knowledgeable enough.

[marmarek]

I had similar problems on Thinkpad X1 Carbon 5th gen. Adding iwlmvm (generally: the wifi driver) to /rw/config/suspend-module-blacklist in sys-net solved the problem for me.
What kernel version do you have in dom0? There is 4.14.13 in testing repository, it may help too.

[marmarek]

I had similar problems on Thinkpad X1 Carbon 5th gen. Adding iwlmvm (generally: the wifi driver) to /rw/config/suspend-module-blacklist in sys-net solved the problem for me.
What kernel version do you have in dom0? There is 4.14.13 in testing repository, it may help too.

[molnara]

I had iwlmvm and iwlwifi already blacklisted and I am using 4.14.13. Not sure what to do now, is it possible to downgrade a kernel?

[molnara]

I had iwlmvm and iwlwifi already blacklisted and I am using 4.14.13. Not sure what to do now, is it possible to downgrade a kernel?

[marmarek]

If you installed 4.0-rc3, you probably have 4.9 kernel still installed, just need to select it in bootloader (in grub there is a menu, for UEFI - edit /boot/efi/EFI/qubes/xen.cfg - default setting).
If you don't have it anymore, you can install it this way:

1. sudo qubes-dom0-update 'kernel-4.9*' (it will fail at the end, but package will be downloaded)
2. sudo dnf downgrade 'kernel-4.9*'

[marmarek]

If you installed 4.0-rc3, you probably have 4.9 kernel still installed, just need to select it in bootloader (in grub there is a menu, for UEFI - edit /boot/efi/EFI/qubes/xen.cfg - default setting).
If you don't have it anymore, you can install it this way:

1. sudo qubes-dom0-update 'kernel-4.9*' (it will fail at the end, but package will be downloaded)
2. sudo dnf downgrade 'kernel-4.9*'

[molnara]

I can confirm reverting back to kernel 4.9.56-21 now allows me to wake my laptop by opening the lid again. Is there somewhere I should be reporting this?

[molnara]

I can confirm reverting back to kernel 4.9.56-21 now allows me to wake my laptop by opening the lid again. Is there somewhere I should be reporting this?

[JamesRBrown]

I have confirmed that this issue is still present in the Qubes-R4.0-x86_64 release.

I also performed the steps Marmarek discribed on 1.19.18.

Booting into the 4.9 kernel didn't resolve the issue on my W530.

[JamesRBrown]

I have confirmed that this issue is still present in the Qubes-R4.0-x86_64 release.

I also performed the steps Marmarek discribed on 1.19.18.

Booting into the 4.9 kernel didn't resolve the issue on my W530.

[andrewdavidwong]

I can confirm reverting back to kernel 4.9.56-21 now allows me to wake my laptop by opening the lid again. Is there somewhere I should be reporting this?

Reporting it here as you did is fine. Thanks!

I have confirmed that this issue is still present in the Qubes-R4.0-x86_64 release.

I also performed the steps Marmarek discribed on 1.19.18.

Booting into the 4.9 kernel didn't resolve the issue on my W530.

Thanks for checking!

[andrewdavidwong]

I can confirm reverting back to kernel 4.9.56-21 now allows me to wake my laptop by opening the lid again. Is there somewhere I should be reporting this?

Reporting it here as you did is fine. Thanks!

I have confirmed that this issue is still present in the Qubes-R4.0-x86_64 release.

I also performed the steps Marmarek discribed on 1.19.18.

Booting into the 4.9 kernel didn't resolve the issue on my W530.

Thanks for checking!

[tweidinger]

Having the issue on my end aswell with a T460p and the current 4.0 release.
Is there any more info needed for this issue?
I got it to work by disabling the Security Chip in the BIOS, but this is just a workaround to make Qubes usable at least.

[tweidinger]

Having the issue on my end aswell with a T460p and the current 4.0 release.
Is there any more info needed for this issue?
I got it to work by disabling the Security Chip in the BIOS, but this is just a workaround to make Qubes usable at least.

[SenorFusion]

+1 same here.

I have the most update to date Qubes-stable as of today, but Suspend or Sleep has never worked on any version of 4.0. Thinkpad P70 with Skylake.

• Kernel Flags: i915.alpha_support=1 rd.blacklist.drivers=nouveau nouveau.modeset=0
• Bios:
• --USB UEFI BIOS Support: Enabled
• --UEFI/Legacy Boot: UEFI Only
• --Secure Boot: Disabled

After suspend a hard-reset reboot (hold down physical power button) is require to get Qubes back.

[SenorFusion]

+1 same here.

I have the most update to date Qubes-stable as of today, but Suspend or Sleep has never worked on any version of 4.0. Thinkpad P70 with Skylake.

• Kernel Flags: i915.alpha_support=1 rd.blacklist.drivers=nouveau nouveau.modeset=0
• Bios:
• --USB UEFI BIOS Support: Enabled
• --UEFI/Legacy Boot: UEFI Only
• --Secure Boot: Disabled

After suspend a hard-reset reboot (hold down physical power button) is require to get Qubes back.

[Marcosmos747]

I too and experiencing the same thing. i'm using
ROG Strix GL502VS-WS71 15.6" Gaming Laptop Computer; Intel Core i7-7700HQ Processor 2.8GHz; NVIDIA GeForce GTX 1070 8GB GDDR5; 16GB DDR4 RAM; 1TB HDD + 256GB SSD; Microsoft Windows 10 64-bit; Media Card Reader; 10/100/100 Network; 2x2 802.11ac Wireless+Bluetooth 4.1; 15.6" Full HD G-Sync Display.
after a few minutes AFK screen goes black and unresponsive. Idk what to do lol.

[Marcosmos747]

I too and experiencing the same thing. i'm using
ROG Strix GL502VS-WS71 15.6" Gaming Laptop Computer; Intel Core i7-7700HQ Processor 2.8GHz; NVIDIA GeForce GTX 1070 8GB GDDR5; 16GB DDR4 RAM; 1TB HDD + 256GB SSD; Microsoft Windows 10 64-bit; Media Card Reader; 10/100/100 Network; 2x2 802.11ac Wireless+Bluetooth 4.1; 15.6" Full HD G-Sync Display.
after a few minutes AFK screen goes black and unresponsive. Idk what to do lol.

[tweidinger]

Just deactivate the TPM module if you have one, if you can live with this.
(Worked for me)

[tweidinger]

Just deactivate the TPM module if you have one, if you can live with this.
(Worked for me)