Nouveau - Nov 2014 - [Bug 86115] New: Suspend to RAM fails when using Nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=86115

            Bug ID: 86115
           Summary: Suspend to RAM fails when using Nouveau
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: lars at samba.org
        QA Contact: xorg-team at lists.x.org

The system in question has a NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1)
graphics card installed.

Triggering suspend to memory works but the resume fails and leads to blinking
shift and scroll lock keyboard leds.

This is a fresh install, no upgrade.

With the same hardware suspend to memory worked with openSUSE 13.1.

I've also tested kernel-vanilla 3.18.rc3.next.20141106-1.1.g2af2e06 and it
shows the same defect as with openSUSE 13.2.

Via netconsole I had been able to capture an even more detailed trace with
no_console_suspend set.  Thanks to Takashi Iwai for his debugging hints.

The same initially was reported at the SUSE bug tracked as it was first seen
with the openSUSE 13.2 kernel-default.
https://bugzilla.suse.com/show_bug.cgi?id=904483

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/38dd226f/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to Lars Müller from comment #0)
> With the same hardware suspend to memory worked with openSUSE 13.1.
What kernel is that?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/9b55fb28/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #2 from Lars Müller <lars at samba.org> ---
(In reply to Ilia Mirkin from comment #1)
> (In reply to Lars Müller from comment #0)
> > With the same hardware suspend to memory worked with openSUSE 13.1.
> 
> What kernel is that?
3.11.10

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/269d8ea5/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #3 from Lars Müller <lars at samba.org> ---
Created attachment 109224
  --> https://bugs.freedesktop.org/attachment.cgi?id=109224&action=edit
kernel ooops trace (3.16.6)

Add lost kernel ooops trace and more detailes kernel RPM details.

kernel-default-3.16.6-2.1.x86_64

Source Timestamp: 2014-10-20 15:47:22 +0200
GIT Revision: feb42eacae8d76252ab69a58d05a0be2cebd8a08
GIT Branch: openSUSE-13.2

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/cd2cb583/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #4 from Takashi Iwai <tiwai at suse.de> ---
In order to make things a bit more straight, could you retest S3 after doing:
  echo 1 > /sys/power/pm_async
?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/08399684/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #5 from Lars Müller <lars at samba.org> ---
Created attachment 109227
  --> https://bugs.freedesktop.org/attachment.cgi?id=109227&action=edit
Retest S3 after calling: echo 1 > /sys/power/pm_async

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/84255ec0/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> ---
There was a change which fixed fbcon acceleration after resume -- before it
effectively switched into software mode on resume, but that got fixed.
Unfortunately if the GPU is unhappy on resume, that means that the console also
hangs.

Specifically it was commit ecf24de071f4f6cea79ecef5d990794df5875ee1. Could you
test a few kernels to see whether it's the same issue you're seeing?

e.g. does 3.14 work while 3.15 fails? If so, can you do a bisect to confirm
(and if not, also do a bisect to figure out what broke it).

git bisect start v3.16 v3.13 -- drivers/gpu/drm/nouveau

should cover the whole range you mentioned (3.13 = good, 3.16 = bad).

Separately, could you attach a full dmesg after boot? That should answer a
number of basic questions about some of your setup's specifics.
Additionally,
how is your monitor(s) connected?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/57315a50/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

Ilia Mirkin <imirkin at alum.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Suspend to RAM fails when   |[NV84] gpu hang on resume
                   |using Nouveau               |from suspend to ram

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/0c0a5374/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #7 from Takashi Iwai <tiwai at suse.de> ---
FYI, there are a few kernel packages available in OBS home:tiwai:kernel:3.13,
home:tiwai:kernel:3.14, and home:tiwai:kernel:3.15 repos.

For 3.12, you can use OBS Kernel:SLE12.  Kernel:stable is for 3.17, and
Kernel:HEAD is for 3.18-rc.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/de1e4c2a/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #8 from Takashi Iwai <tiwai at suse.de> ---
(In reply to Takashi Iwai from comment #4)
> In order to make things a bit more straight, could you retest S3 after
doing:
>   echo 1 > /sys/power/pm_async
> ?
Doh, sorry, I wanted to see the result with *disabled* async  PM.

Lars, please retest with

   echo 0 > /sys/power/pm_async

Certainly there is a GPU hang at PM, but I'd like to know whether it's
the real
culprit of the whole hang.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/60f2d8c3/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

Lars Müller <lars at samba.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #109227|0                           |1
        is obsolete|                            |

--- Comment #9 from Lars Müller <lars at samba.org> ---
Created attachment 109236
  --> https://bugs.freedesktop.org/attachment.cgi?id=109236&action=edit
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/bfa5f38c/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #10 from Lars Müller <lars at samba.org> ---
Created attachment 109237
  --> https://bugs.freedesktop.org/attachment.cgi?id=109237&action=edit
dmesg output as requested with comment #6

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/c1b7d2f3/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #11 from Takashi Iwai <tiwai at suse.de> ---
(In reply to Lars Müller from comment #9)
> Created attachment 109236 [details]
> 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141110/ada40fe4/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #12 from Lars Müller <lars at samba.org> ---
(In reply to Takashi Iwai from comment #7)
> FYI, there are a few kernel packages available in OBS
> home:tiwai:kernel:3.13, home:tiwai:kernel:3.14, and home:tiwai:kernel:3.15
> repos.
                                        s2disk                 s2ram

kernel-default-3.12.33-2.1.g26c7845     suspend yes            resume works
                                        resume => fresh boot   display is
dead

kernel-default-3.13.7-4.1.ga68bc7c      suspend yes            ooops
                                        resume fresh boot

kernel-default-3.14.6-1.1               suspend yes            ooops
                                        resume fresh boot

kernel-default-3.15.8-1.1               suspend yes            ooops
                                        resume fresh boot

kernel-default-3.16.6-2.1               suspend yes            ooops
                                        resume fresh boot

kernel-default-3.17.4-1.1.gd50009e      ok                     ooops

kernel-default-3.18.rc4-3.1.g0521fb3    suspend yes            ooops
                                        resume fails
                                        not net; no X

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141125/3fa6ff43/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #13 from Lars Müller <lars at samba.org> ---
(In reply to Takashi Iwai from comment #11)
> 
> 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.
It crashes even without nouveau when booted with nomodeset set.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141125/38fb77c0/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #14 from Lars Müller <lars at samba.org> ---
Is more testing or additional feedback required from my side to move this bug
forward?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141212/9564773f/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

--- Comment #15 from Tobias Klausmann <tobias.klausmann at mni.thm.de> ---
(In reply to Lars Müller from comment #14)
> Is more testing or additional feedback required from my side to move this
> bug forward?
You could try to boot and test with

modprobe.blacklist=nouveau to make sure the module isn't loaded.

If you really have time on your hands, try to bisect the problem: 3.11 as a
good starting point and 3.13 or 3.14 as bad, but that will really eat time :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141212/20308fbb/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=86115

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |MOVED

--- Comment #16 from Martin Peres <martin.peres at free.fr> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/149.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20191204/ddfec762/attachment.html>