https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c2 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED CC| |ddadap@nvidia.com AssignedTo|bnc-team-screening@forge.pr |sndirsch@suse.com |ovo.novell.com | --- Comment #2 from Stefan Dirsch 2014-08-04 09:05:13 UTC --- (In reply to comment #1)

The openSUSE 13.1 kernel already contains the framework for VT-switchless resume. The rest is to patch Nvidia binary-only stuff.

Not sure which patches you mean, Takashi. Adding NVIDIA here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c3 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|tiwai@suse.com | --- Comment #3 from Takashi Iwai 2014-08-04 09:34:37 UTC --- See the launchpad thread mentioned in the bug description. https://launchpadlibrarian.net/168889296/pm_vt_switch_required.patch -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c5 --- Comment #5 from Daniel Dadap 2014-08-04 17:37:19 UTC ---

Daniel, is this something you're planning to add to the driver?

In fact, I provided that very patch to Canonical when I made that change to the NVIDIA driver, so that they could patch their packages for existing releases while waiting for the next release which contained the change that I made. :) 331.67, and all subsequent versions of the NVIDIA Linux driver, including the 340.24 driver mentioned in the bug description, already include this change. To clarify the issue tracked in that launchpad bug: the problem was that the kernel was skipping VT switches on PRIME configurations; the NVIDIA driver relies on VT switches for proper restoration of X after suspend/resume, which was causing corrupted/frozen displays on PRIME configurations. The reason this was happening on PRIME configurations was because the new code in the kernel to optionally skip VT switches will preserve the old behavior of always VT switching if no driver explicitly indicates to the kernel, via pm_vt_switch_required(), that either does or does not require VT switches. If *any* driver calls pm_vt_switch_required(), and all drivers which do this indicate that no VT switch is required, the kernel will skip VT switches. This was the case under PRIME with older NVIDIA drivers, since the NVIDIA driver did not register with pm_vt_switch_required(), and the Intel driver registered that VT switches were not required. Anyway, based on a skim of the openSUSE forum thread, I doubt this is related to the launchpad bug, since it doesn't seem like those users are using PRIME, and they're still reporting problems with drivers that contain the fix for the pm_vt_switch_required() issue. Unfortunately, the class of "failure to properly resume from suspend" issues is a somewhat broad one, so although the symptom reported on the openSUSE forums is quite similar to the one in the launchpad bug, their root causes appear to be disjoint. Based on the description of the symptoms in the forum threads, it is possible that this is due to improper FBO reuse after a modeswitch: the contents of FBOs are not guaranteed to be preserved across modeswitch events, which are incurred on suspend/resume, among other situations. This has resulted in similar bugs in other composite managers and GL applications, where screen contents were corrupted after suspend/resume. However, it's also possible that it's due to a bug in the NVIDIA driver. I've filed NVIDIA bug number 1540794 to track this issue: we'll attempt to reproduce the problem internally, and determine whether or not it appears to be a driver bug. There is a recently fixed NVIDIA driver bug (the fix is not yet in any released driver, but some soon-to-be-released drivers will include it) involving FBO refreshes in some situations, but I do not believe it is related to this issue, since that bug was a regression in the 337 driver series: this bug is being reported on 304 and 331. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c7 --- Comment #7 from Gordon Dickens 2014-08-05 15:40:08 UTC --- Created an attachment (id=601127) --> (http://bugzilla.novell.com/attachment.cgi?id=601127) Email from nVidia support -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c9 --- Comment #9 from Gordon Dickens 2014-08-05 15:46:06 UTC --- I filed a bug report with nVidia via email to: linux-bugs@nvidia.com which included a log dump named nvidia-bug-report.log and which is generated by a script located at /usr/bin/nvidia-bug-report.sh. I generated the log dump immediately following a failure to sleep-suspend. Today, Sandip Thorat (nVidia Unix OEMQA Support) replied and said that the issue is not with the nVidia driver but is with the kernel or some other software component. I have attached the email from Sandip Thorat and the nVidia log dump generated immediately after failure to sleep-suspend. FYI, Gordon -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c11 --- Comment #11 from Gordon Dickens 2014-08-07 18:37:36 UTC --- I can confirm that "kwin --replace" (assigned to a hot key) will successfully fix the corrupted screen that occurs after resume from sleep-suspend. However, if you are also locking the screen upon suspend-sleep then you have to figure out how to blindly log back in before issuing "kwin --replace". I've been having lots of resume from sleep-suspend failures today. Ugh. Resume is failing 25% to 50% of the time again with a corrupted display no matter whether I suspend with systemctl or the KDE Power Manager. I am currently running the 3.15.6-2.1 kernel, however, I had this problem with the stock 3.11.10 and 3.11.6 kernels as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c13 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum@suse.com --- Comment #13 from Oliver Neukum 2014-08-13 18:18:26 UTC --- (In reply to comment #10)

Gordon Dickens said:

I had this issue, too (on arch linux with 3.15.8 kernel and Nvidia binary driver), and moving to the older lts-kernel 3.14.15 worked: No more screen errors after resume or the other method (see below). So for me, it seems really to be an kernel issue.

In this case please bisect the kernel. Somebody who can reproduce the issue needs to do that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c15 --- Comment #15 from Gordon Dickens 2014-08-13 20:03:43 UTC --- Also, I don't have any experience in kernel developement and/or bisecting the kernel although I would be happy to test anything that you send to me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c17 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #17 from Stefan Dirsch 2014-08-18 15:20:49 UTC --- Packages have been updated to 340.24 in NVIDIA's repository. Nothing more I can do here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.