Suspend-to-ram does not work in loop-installations
Bug #176112 reported by
Agostino Russo
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wubi |
Fix Released
|
Medium
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In loopinstallations such as the ones used by the Windows Installer (https:/
In such scenario suspend-to-ram fails, Matthew Garrett had a preliminary look at the issue some time ago', my understanding is that the issue is due to the oredering with which processes are stopped/resumed.
Changed in wubi: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
To post a comment you must log in.
Hi Agostino,
Is it the actual suspend that doesn't work or is it the resume which fails? Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.
* uname -a > uname-a.log signature > version.log
* cat /proc/version_
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
If you are able to, it would be more useful to capture the dmesg output after you attempt to suspend/resume. For more information regarding the kernel team bug policy, please refer to https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies . The following might also help: https:/ /wiki.ubuntu. com/DebuggingKe rnelSuspend . Thanks.