Comment 32 for bug 2033327
Revision history for this message
| Mario Limonciello (superm1) wrote Re: Desktop cannot resume after suspend: screen not detected | #32 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
You're totally right that there is a problem when memory pressure is high that the suspend sequence can't evict the RAM.
This is upstream https:/
A bunch of changes are going into 6.7 that will move the parts that allocate memory into the prepare() pmops sequence. This will "fix" the immediate problem in that the suspend itself will "return" an error code.
There is a secondary problem though that the PM core disables swap "too soon", so if memory is low it can't be moved into swap.
This secondary problem can either be fixed by PM core either moving the timing of the swap disable or evicting some other usage (userspace?) into swap before letting the prepare()/suspend() sequence start.