http://bugzilla.suse.com/show_bug.cgi?id=1087261 http://bugzilla.suse.com/show_bug.cgi?id=1087261#c1 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P5 - None CC| |wbauer@tmo.at Component|KDE Workspace (Plasma) |Kernel Assignee|opensuse-kde-bugs@opensuse. |kernel-maintainers@forge.pr |org |ovo.novell.com --- Comment #1 from Wolfgang Bauer --- (In reply to Dario Savella from comment #0)

The recent kernel upgrade from 4.4.114 to 4.4.120 introduced some regression ... I was able revert back to the previous kernel-default version and the problems disappeared.

Well, then it's rather a problem with the kernel update I would say, not KDE/plasma (which wasn't changed anyway). Btw, you are not supposed to change the Priority, that field is reserved for the developers/maintainers to prioritize the bugs they are working on. Only the "Severity" field is to be set by the reporter. See https://bugzilla.suse.com/page.cgi?id=importance_matrix.html -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1087261 http://bugzilla.suse.com/show_bug.cgi?id=1087261#c3 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dario@growingman.com, | |tiwai@suse.com Flags| |needinfo?(dario@growingman. | |com) --- Comment #3 from Takashi Iwai --- Could you give the output of "rpm -q kernel-default" and "rpm -q drm-kmp-default" ? It might be that drm-kmp-default was used only in a newer kernel (or vice-versa). Usually KMP can be kept, but in the case of recent kernel update, it's refreshed and becomes incompatible due to Spectre/Meltdown fixes. In anyway, please give the hardware details, too. At least, hwinfo output would be helpful. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1087261 http://bugzilla.suse.com/show_bug.cgi?id=1087261#c5 Dario Savella changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dario@growingman. | |com) | --- Comment #5 from Dario Savella --- Created attachment 766360 --> http://bugzilla.suse.com/attachment.cgi?id=766360&action=edit Output of hwinfo on my machine -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1087261 http://bugzilla.suse.com/show_bug.cgi?id=1087261#c7 --- Comment #7 from Dario Savella --- # rpm -q kernel-default kernel-default-4.4.114-42.1.x86_64 # rpm -q drm-kmp-default drm-kmp-default-4.9.33_k4.4.79_4-5.2.x86_64 drm-kmp-default-4.9.33_k4.4.114_42-7.1.x86_64 drm-kmp-default-4.9.33_k4.4.120_45-10.2.x86_64 I assume the last one is installed because I did the upgrade and then reverted back only kernel-default to 4.4.114 Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1087261 http://bugzilla.suse.com/show_bug.cgi?id=1087261#c9 --- Comment #9 from Takashi Iwai --- What the procedure above does is to re-install 4.4.120 kernel with the drm-kmp package with a fix for a known regression of S3. It's interesting to know whether it works for you, too. This drm-kmp fix update was pending for now, unfortunately, due to the conflict of multi-versions. It'll be with the next kernel update together, hopefully starting in the next week. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1087261 http://bugzilla.suse.com/show_bug.cgi?id=1087261#c11 --- Comment #11 from Dario Savella --- I am sorry, but I think I did not check this thoroughly. I just noticed the black screen is only on my primary HDMI display. Upon resume the additional monitor is refreshed and, by changing resolution and forcing a reset, the primary comes back to life. KDE has a bug that looses dual monitor setup. I used to run xrandr at startup, but I recently tried a different solution, setting screens directly in X11. Perhaps the new fix does not filly work with suspend... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1087261 http://bugzilla.suse.com/show_bug.cgi?id=1087261#c13 --- Comment #13 from Dario Savella --- Just a small update: I need the suspend/resume cycle to work, so I reverted back to 4.4.114. Now my system as the following drm-kmp packages installed, but I am not sure how to determine which one is actually used: drm-kmp-default-4.9.33_k4.4.126_48-13.3.x86_64 Fri Apr 20 09:10:03 2018 drm-kmp-default-4.9.33_k4.4.120_45-10.2.x86_64 Tue Apr 17 00:13:42 2018 drm-kmp-default-4.9.33_k4.4.120_45-13.2.x86_64 Sat Apr 7 18:09:49 2018 drm-kmp-default-4.9.33_k4.4.114_42-7.1.x86_64 Tue Mar 20 09:23:18 2018 drm-kmp-default-4.9.33_k4.4.79_4-5.2.x86_64 Sun Dec 10 17:07:52 2017 -- You are receiving this mail because: You are on the CC list for the bug.