This was a fresh install and therefore has no previous kernels in that list.
This was a fresh install and therefore has no previous kernels in that list.
Excuse my ignorance, but is it more effective to do anything other than send the report from within Ubuntu's Launchpad (or whatever it is) dialog? Thanks for trying to help me with this. I really hope it can get resolved in the future as I want to save power when I'm not using my computer. I'm a little surprised a complete Intel setup has issues, but it is what it is.
As seems to be indicated by the error dialog above, you appear to be suffering a kernel crash during suspend. This is out of the ordinary, hence the suggestion to create a launchpad bug report. The other suggestion, one which will probably be repeated by the bug triage team, will be to try a different kernel to see if it solves the problem.
You could try booting from the live CD/USB and trying to suspend to see if the problem persists. Compare the kernel versions. Though I believe they will be the same.
You could also try the mainline kernel to help troubleshoot/resolve the issue. More information about mainline kernels can be found here.
Unfortunately, we cannot find any messages in any of the log files to help give us a hint as to what is happening.
Having the exact same issue here.
Should I post here or start a new (duplicate?) thread?
Probably best to create a new thread. Be sure to include the following information:
- detailed explanation of problem
- make/model of computer
- results of the following command line queries:
- contents of the two following log files:Code:cat /proc/cmdline lsmod
Also, have a look a the "Kernel Suspend" link in my signature for more troubleshooting steps.Code:pastebinit /var/log/pm-suspend.log pastebinit /var/log/dmesg
@shanepardue,
One more suggestion. Can you try the acpi_sleep=nonvs kernel parameter?
Reference: https://www.kernel.org/doc/Documenta...parameters.txtnonvs - prevents the kernel from saving/restoring the
ACPI NVS memory during suspend/hibernation and resume.
I unplugged an IR Receiver that was plugged into the USB3 port and suspend is working now. Should've tried this earlier when you mentioned that port being a possible culprit, but oh well. Does this mean the machine can't sleep when USB3 devices are plugged in?
Does the ir receiver load a module? If so, we can automatically unload it. Compare the results of "lsmod" before and after inserting the receiver.
Also, run the following command:
...insert the receiver, and post back any messages that appear.Code:tail -f /var/log/syslog
Bookmarks