[Bug 889660] New: nVidia proprietary driver does not consistently resume from sleep/suspend.
https://bugzilla.novell.com/show_bug.cgi?id=889660 https://bugzilla.novell.com/show_bug.cgi?id=889660#c0 Summary: nVidia proprietary driver does not consistently resume from sleep/suspend. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: gordon@dickens.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Resume from sleep/suspend does not work consistently with the nVidia proprietary device drivers. I have experienced this problem with the OpenSUSE packaged G02 and G03 drivers up through G02 version 304.121 and G03 version 331.89 and with several of the stock OpenSUSE kernels. With the OpenSUSE packaged drivers and stock kernels, resume from sleep/suspend will fail 25% to 50% of the time. Most recently, I have installed the latest nVidia driver version 340.24 from the nVidia website and the latest kernel version 3.15.6-2.gedc5ddf-desktop from the kernel-stable repo. With this more recent driver/kernel combo, resume from sleep/suspend fails approximately 10% of the time. So, the problem is not gone but it occurs less often with the latest driver and kernel. Also, the failure rate appears higher if I am running the kcometen4 screen saver and the failure rate appears lower if I am not running a screen saver but am using the simple locker instead. I am running OpenSUSE 13.1, KDE 4.13.3 and a nVidia Quadro FX 3600M graphics card on a Dell Precision 6300 laptop. This problem has been reported in the OpenSUSE and KDE forums here: https://forums.opensuse.org/showthread.php/494706-openSUSE-13-1-KDE-inconsis... https://forum.kde.org/viewtopic.php?f=111&t=121590 A very similar problem was also reported as a Ubuntu bug which has purportedly been fixed here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1... Reproducible: Sometimes Steps to Reproduce: 1. Put the computer in the sleep/suspend state. 2. Bring the computer out of the sleep/suspend state (Resume). Actual Results: 10% to 50% of the time resume from sleep/suspend will fail and the screen will be garbled and frozen. Expected Results: The computer should resume from sleep/suspend without a garbled and frozen display. -- 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#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com Component|Kernel |X11 3rd Party Driver AssignedTo|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com QAContact|qa-bugs@suse.de |sndirsch@suse.com --- Comment #1 from Takashi Iwai <tiwai@suse.com> 2014-07-31 13:21:43 UTC --- The openSUSE 13.1 kernel already contains the framework for VT-switchless resume. The rest is to patch Nvidia binary-only stuff. -- 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#c2 Stefan Dirsch <sndirsch@suse.com> 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 <sndirsch@suse.com> 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#c Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |tiwai@suse.com -- 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 <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|tiwai@suse.com | --- Comment #3 from Takashi Iwai <tiwai@suse.com> 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#c4 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |ddadap@nvidia.com --- Comment #4 from Stefan Dirsch <sndirsch@suse.com> 2014-08-04 09:48:53 UTC --- Thanks, Takashi! Daniel, is this something you're planning to add to the driver? -- 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 <ddadap@nvidia.com> 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#c6 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|ddadap@nvidia.com | --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> 2014-08-05 00:24:21 UTC --- Daniel, you're right. The patch is already included in 331.89. Updating to 340 is on my TODO list anyway. -- 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 <gordon@dickens.com> 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#c8 --- Comment #8 from Gordon Dickens <gordon@dickens.com> 2014-08-05 15:41:39 UTC --- Created an attachment (id=601129) --> (http://bugzilla.novell.com/attachment.cgi?id=601129) nVidia log dump generated immediately after failure to sleep-suspend. -- 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 <gordon@dickens.com> 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#c10 Bazon Bloch <bazonbloch@arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bazonbloch@arcor.de --- Comment #10 from Bazon Bloch <bazonbloch@arcor.de> 2014-08-07 05:19:17 UTC --- Gordon Dickens said: "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 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. Also, I found a more reliable way to reproduce that issue: Start a second X-Server on another vt, and than switch back to the first X-Server --> 100% screen errors (with the recent kernel 3.15.8, not with 3.14.15) See instructions here if needed: https://forums.opensuse.org/showthread.php/494706-openSUSE-13-1-KDE-inconsis... -- 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 <gordon@dickens.com> 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#c12 --- Comment #12 from Gordon Dickens <gordon@dickens.com> 2014-08-09 19:49:57 UTC --- I installed kernel-desktop version 3.16.0-3.1.ga29135e (kernel-desktop-3.16.0-3.1.ga29135e.x86_64.rpm ) from the HEAD repo and recompiled/reinstalled the nvidia 340.24 driver. This new kernel 3.16.0-3.1.ga29135e failed to resume on the 2nd suspend. So, this new kernel is broken as well. I request that the developers test for this problem and patch it. This was first reported in the forums in January and has been going on now for over seven (7) months. Thanks, 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#c13 Oliver Neukum <oneukum@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum@suse.com --- Comment #13 from Oliver Neukum <oneukum@suse.com> 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#c14 --- Comment #14 from Gordon Dickens <gordon@dickens.com> 2014-08-13 19:58:41 UTC --- Just to clarify, the above statement in comment 13 that was attributed to me was actually made by Bazon Bloch regarding using kernel 3.14.15. FWIW, I have not used kernel 3.14.15 since the earlier kernels that I used didn't work either. The kernels that I have personally used and that resume fails with are 3.11.6, 3.11.10, 3.15.6 and 3.16.0. -- 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 <gordon@dickens.com> 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#c16 --- Comment #16 from Bazon Bloch <bazonbloch@arcor.de> 2014-08-13 21:22:35 UTC --- Oh sorry, I forgot to mention: I took a few days more, but then, it happened with 3.14.15, too. (it=not consistently resume) As I had enough of this behaviour, I switched to an ATI card, so I'm out now, sorry again. -- 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 <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #17 from Stefan Dirsch <sndirsch@suse.com> 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.
participants (1)
-
bugzilla_noreply＠novell.com