Bug 216998
| Summary: | suspend to RAM broken on Fujitsu Lifebook U7512 | ||
|---|---|---|---|
| Product: | Power Management | Reporter: | Christoph Anton Mitterer (calestyo) |
| Component: | Hibernation/Suspend | Assignee: | Rafael J. Wysocki (rjw) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | jarkko, kernel, mario.limonciello |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 6.1.15 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
|
Description
Christoph Anton Mitterer
2023-02-03 17:27:09 UTC
Just for the records: still the case as of kernel 6.1.12 and with a newly released BIOS (2.25) Still in 6.1.15. Also I've noticed the following in my kernel logs: # dmesg | grep -i suspend [ 1.295940] Low-power S0 idle used by default for system suspend [ 1.952309] nvme 0000:01:00.0: platform quirk: setting simple suspend Not sure if the nvme message is about some suspend *just* for the NVMe itself or whether it has to do with s2deep (especially as it comes after the information that the kernel chooses s2idle as default)... ... but I found: https://bugzilla.kernel.org/show_bug.cgi?id=215742 Where the same quirk seems to have caused a broken resume... just like in my case (when I force to use s2deep, the system just hangs at resume). > [ 1.295940] Low-power S0 idle used by default for system suspend The kernel will by default prefer to use s2idle as that's what the firmware indicates in the FADT. In my experience unless the vendor has intentionally spent extra effort to make S3 work you're unlikely to get a functional "deep" mode on modern hardware like this. > Not sure if the nvme message is about some suspend *just* for the NVMe itself > or whether It's just for the NVME disk. > Where the same quirk seems to have caused a broken resume... just like in my > case (when I force to use s2deep, the system just hangs at resume). You're misinterpreting this issue. The problem was the lack of quirk led to problems during resume from s2idle. --- My suggestion for your issue is that you focus on identifying the problems with s2idle for your system and report those to the individual driver and subsystem owners to get fixed rather than work on S3. In the meantime I disabled the NVMe in the BIOS and booted with that. Whil the 2nd message disappears, the kernel still defaults to s2idle and resuming from deep mode still freezes (the screen doesn't even go on).
So that seems to confirm, as you've said, that the two have nothing to do with each other.
> In my experience unless the vendor has intentionally spent extra
> effort to make S3 work you're unlikely to get a functional "deep"
> mode on modern hardware like this.
Sounds unbelievable... I mean (real) suspend is like base technology and they don't make it work... sigh.
|