Out of the box, Qubes OS 4.2 RC3 works well but doesn’t suspend. I tried upgrading dom0 to kernel-latest but the problem persists. Screen turns off, fans stop spinning, then screen flashes on once or twice, fans start spinning again, and the lock screen appears.
Kernel logs show that the suspend was cancelled due to a hardware issue:
intel_pmc_core INT33A1:00: PM: failed to suspend late: error -5
But I don’t know what device this could be that’s failing to suspend. I tried disabling all optional devices in BIOS(webcam, fingerprint reader, WiFi, etc.) without success.
Does anyone have ideas on how I could troubleshoot this further?
Hmm, according to kernel docs s2idle maps to ACPI state S0. Does this mean your comment still applies and I should expect s2idle is fully unsupported for now?
Yes, it seems to be the same thing, just different names (Intel calls it S0ix).
Unfortunately it is unsupported in Qubes OS, nothing can be done at this point by usual user.
Sad to hear this is not supported, because the newer ThinkPad machines like mine don’t have any option for S3 suspend so the only option we have on these devices is a full shutdown.
Actually they do have S3, e.g. Thinkpad T16 Gen1 and many others. The available BIOS/EFI settings (including S3 support) can be check on the Lenovo web site, they have BIOS/EFI emulator available in the browser.
Most of our platforms (with the exception of a couple of workstations) are now S0ix only.
We did dual sleep support with both S3 and S0ix as an option in the BIOS (with S3 as ‘best effort’ for users who didn’t want to switch) on our Linux certified Intel platforms for a few years - and it was a nightmare.
…
We found many S3 issues would creep in with FW updates - devices would stop working on resume, system wouldn’t sleep properly and battery drain in a few cases were horrible. Getting fixes done took forever and we couldn’t delay FW updates for a sleep mode that was supposed to be ‘best effort’. Users were frustrated (understandably) and it was not a good experience for anybody. We were honestly trying to do the right thing - but it wasn’t working.
We made the decision to stop doing S3 support last year and to remove the option.
So it looks like issue #6411 that you shared will be increasingly important for Lenovo laptop users in future.
I think, it is already through the roof for laptop users.
As far as I know, Intel said something similar to “Intel CPUs of 11-12 Gen will not support S3”, but it was a lie, as we see S3 on some Thinkpads with Intel 12 Gen CPUs, including T16. But those Thinkpads are exceptions nowadays, most of laptop manufactures decided to drop S3 support as Intel advised.
Not obvious what/whom he blames, their own firmware developers of their own laptop’s hardware and devices they choose? I mean S3 existed for years, working perfectly well on many devices (but not all). Why would one blame S3 instead of firmware of devices they choose and use for being too unreliable and full of bugs within deep sleep? Looks a bit strange to me.
