Bug 198763
Summary: | Suspend2ram broken on 4.16-rcX (32-bit non-PAE) | ||
---|---|---|---|
Product: | Power Management | Reporter: | Woody Suwalski (terraluna977) |
Component: | Hibernation/Suspend | Assignee: | Rafael J. Wysocki (rjw) |
Status: | RESOLVED CODE_FIX | ||
Severity: | high | CC: | regressions |
Priority: | P1 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 4.15.2 4.16-rcX 4.14.21 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: |
Kernel .config file
PAE config with working s2ram non-PAE config resulting in broken s2ram |
Description
Woody Suwalski
2018-02-12 14:28:59 UTC
The same problem is seen on 4.16-rc1 After more investigation I have isolated the issue to be happening only on non-pae builds. Kernels configured to use pae can wake from suspend2ram without problems. The way to trigger the problem is to switch the config from CONFIG_X86_PAE to CONFIG_HIGHMEM4G (and "automatic" dependencies, like state of PHYS_ADDR_T_64BIT, PGTABLE_LEVELS..). Tested with and without PAE on 4.15.4 and 4.16-rc1 Created attachment 274231 [details]
PAE config with working s2ram
Created attachment 274233 [details]
non-PAE config resulting in broken s2ram
Updated the config file(s) with 4.15.4 version I see that the same problem is now present in 4.14.21 Woddy, can you close this please, as this afaics was fixed by https://git.kernel.org/torvalds/c/945fd17ab6bab8a4d05da6c3170519fbcfe62ddb Or did I get something wrong? The issue is fixed now in 4.16-rc4 by Thomas Gleixner's patch. Marking resolved trusting that the patch will appear in the stable 4.15 and 4.14 releases. |