Red Hat Bugzilla – Bug 355201
Suspend-to-ram no longer resumes
Last modified: 2015-03-04 20:19:26 EST
Description of problem:
I have a Dell Lattitude D620 with an Nvidia card. I'm running Fc8t3 updated to
latest development. First of all suspend has disappeared from the power applet.
There is still pm-suspend which seems to suspend the machine fine. However,
upon resume the machine is active but the screen is blank. I can ssh into the
machine, but cannot get the screen active. When I kill the X session the system
hangs. I can't find anything relevant in the logs.
I'm using the "nv" driver.
Suspend used to work fine up until about 5 days ago. So much has been changing
I can't tell if it was a kernel, pm-utils, or X change.
Version-Release number of selected component (if applicable):
every attempt at resume
Steps to Reproduce:
Created attachment 240421 [details]
output of /var/log/pm-suspend.log
I tried "setenforce 0" and I tried stopping X first. Still blank screen. Also
when I stopped X and suspend/resume then I couldn't ssh into the system either.
Did suspend/resume *ever* work on your system in rawhide? We've disabled suspend
on machines with nvidia video because of bugs in the nv driver that prevent it
from resuming properly.
For details, see here: http://katzj.livejournal.com/407566.html
Actually, suspend/resume is very reliable on my D620 using the NV driver. It
was the nvidia driver that always gave me problems. I have recently found out
that I need to add ALLOW_NV_SUSPEND="yes" to a file in /etc/pm/config.d to
reenable suspend for nv graphics. I've done this and suspend/resume works again.
The confusing thing is that without this special kung-fu move, pm-suspend does
do a suspend, but doesn't resume properly. Shouldn't pm-suspend be disabled too
with some kind of warning message?
(In reply to comment #4)
> The confusing thing is that without this special kung-fu move, pm-suspend does
> do a suspend, but doesn't resume properly. Shouldn't pm-suspend be disabled too
> with some kind of warning message?
Afaik pm-suspend is not intended to be run directly except for testing purposes.
echo 'ALLOW_NV_SUSPEND="yes"' >> /etc/pm/config.d/00-allow-nv-suspend
Oh, my comment #5 was incomplete. The "help you?" should read "Does this help you?".
This bug cannot be fixed without having more information (see comment #5).