<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [NV84] gpu hang on resume from suspend to ram" href="https://bugs.freedesktop.org/show_bug.cgi?id=86115#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [NV84] gpu hang on resume from suspend to ram" href="https://bugs.freedesktop.org/show_bug.cgi?id=86115">bug 86115</a> from <a class="email" href="mailto:tiwai@suse.de" title="Takashi Iwai <tiwai@suse.de>"> Takashi Iwai</a> <pre>(In reply to Lars Müller from <a href="show_bug.cgi?id=86115#c9">comment #9</a>) > Created <a href="attachment.cgi?id=109236" name="attach_109236" title="Retest S3 after calling: echo 0 > /sys/power/pm_async">attachment 109236</a> <a href="attachment.cgi?id=109236&action=edit" title="Retest S3 after calling: echo 0 > /sys/power/pm_async">[details]</a> > Retest S3 after calling: echo 0 > /sys/power/pm_async > > With /sys/power/pm_async set to 0 the system no longer crashes while resume. > > I'm able to ssh into the system but x.org doesn't come back. The two > screens stay black. OK, then I guess you're seeing two distinct issues. One is the broken graphics by S3, and another is the kernel panic due to the stall of disk PM. Disabling async PM seems curing the latter while the graphics remains broken. Could you try to boot with nomodeset boot option in runlevel 3, and try S3, but without pm_async adjustment? The graphics can be broken in this case after S3, but if the system alives, you should be able to remote-login. If S3 crashes even without nouveau, we can check the two issues above completely separately. If S3 crash happens only with nouveau, it implies that the disk problem is somehow related with nouveau problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>