[Bug 963374] New: Blank display after screensaver activation
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=963374 Bug ID: 963374 Summary: Blank display after screensaver activation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: darren@freemaninstruments.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Possibly related to other bugs posted on the nuveau driver. Hardware is a brand new Gigabyte P17 v3 laptop. CPU is a i7-4710MQ which has integrated Intel 3D graphics. Also present is a Nvidia GTX 950M GPU. I was unable to install openSUSE Leap 42.1 until I realised I had to disable the Nvidia GPU in firmware. It kept giving lots of kernel messages from nuveau and then ultimately it would randomly freeze and that's it, system is locked, no capslock light toggle nothing. I got all the way to a working system with the Nvidia chip disabled. Pain in the butt though as I paid extra for it and I need it later. I was not successful with the proprietary drivers either. X detects the drivers in a certain order, and picks up intel before nvidia, and I think from memory it then dies. So I left it using the intel driver. I had to turn off compositing in KDE because of horrible graphics bugs. Windows not rendering at all, etc. So now I have a usable system. I am now running the latest 4.4.0 kernel from obs:stable. But I think recently it was 4.3.3. Sadly I pulled in a stack of updates maybe yesterday, and now the following happens. When I suspend and resume, I get a blank screen. When the screen saver kicks in after a few min of activity and locks the screen, I get a blank screen. I can't ctrl-F1 out to a virtual console. I can't ctrl-alt-backspace to kill the X server. It's well and truly permanent and I end up powering off. So I'm posting this as a fresh bug because I think my system is sufficiently different, and because I can pin it down to whichever kernel or X updates were posted in the last day or two. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=963374 http://bugzilla.suse.com/show_bug.cgi?id=963374#c1 --- Comment #1 from Darren Freeman <darren@freemaninstruments.com> --- Created attachment 663102 --> http://bugzilla.suse.com/attachment.cgi?id=663102&action=edit X.Org log, normal operation -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=963374 http://bugzilla.suse.com/show_bug.cgi?id=963374#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |darren@freemaninstruments.c | |om, tiwai@suse.com Flags| |needinfo?(darren@freemanins | |truments.com) --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- So, this happens with 4.4 kernel, but it didn't in the past? Do you still have 4.3.x kernel on your system? If yes, try to boot with it (you can choose it from GRUB advanced menu). Once when confirmed that it's a regression in 4.4, we should report to upstream. In that case, try to boot with drm.debug=0x0e option and get the wrong backlight state. Save the kernel log (e.g. the output of dmesg), and attach it to Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=963374 http://bugzilla.suse.com/show_bug.cgi?id=963374#c3 --- Comment #3 from Darren Freeman <darren@freemaninstruments.com> --- I'm afraid I only have 4.4.0-1-default and 4.4.0-6.g9b438ee, from Tumbleweed and from OBS Kernel:Stable respectively. Fortunately I have another machine with 4.3.3-2.gdb72752-default still installed, and I'll manually copy it over if I can. But this highlights a problem with OBS Kernel:Stable. Would it be possible to keep a few older versions in the repo? Perhaps just the newest in the 4.0.x, 4.3.x, 4.2.x, etc series. I will try to get you the info as requested but it will take a few cycles of deliberately locking up a machine that I use all the time. BTW I may have seen a new aspect to this bug yesterday: I had a process running in a virtual console, i.e. alt-F1. It was rsync --progress I believe, so it scrolled a huge amount of text. At some point the display froze. It wouldn't generate any more text. I couldn't type. I could still switch back and forth to the desktop using alt-F7, and the desktop was working. Only the virtual console was frozen. And as far as I could tell, rsync completed successfully. It was only a display issue. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=963374 http://bugzilla.suse.com/show_bug.cgi?id=963374#c4 --- Comment #4 from Darren Freeman <darren@freemaninstruments.com> --- I'm actually having trouble getting the screen to blank. I've turned it off in the KDE system settings, I think it was only under Power Management that I turned it off. I may have found a bug in KDE where you can't turn it back on again, perhaps until the session is restarted. But suspend to RAM is now working again. I'm using 4.4.0-6.g9b438ee-default at the moment, and it may not be the one that had the problem. Were there any very recent changes made that might have been reverted upstream? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=963374 http://bugzilla.suse.com/show_bug.cgi?id=963374#c5 --- Comment #5 from Darren Freeman <darren@freemaninstruments.com> --- Oh and in the meantime I've also done a zypper dup from Leap to Tumbleweed so it may not be so easy to diagnose. I did this because the Evolution team have decided to only compile against Gnome libraries that are newer than what Leap has. And Evo has a lot of bugs in it right now that I couldn't live with. The version that ships with Leap is pretty well unusable for me, so that makes the whole distro unusable. I will see if I can confirm the kernel regression over the next day or two. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=963374 http://bugzilla.suse.com/show_bug.cgi?id=963374#c6 --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- You can try 4.3 kernel packages in OBS home:tiwai:kernel:4.3 repo, too. BTW, it's also interesting whether you can have a remote access when the blank screen happens. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=963374 http://bugzilla.suse.com/show_bug.cgi?id=963374#c7 Darren Freeman <darren@freemaninstruments.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(darren@freemanins | |truments.com) | --- Comment #7 from Darren Freeman <darren@freemaninstruments.com> --- I can't make the display blank any more, and I don't know why. I thought I'd restored all the settings in the KDE control center. Is it possible that someone has disabled it in the kernel? Currently running 4.4.0-8.g9f68b90-default -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com