[Bug 1059302] New: Intel HD 616/kabylake crashes after hibernate, not after suspend-to-ram
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 Bug ID: 1059302 Summary: Intel HD 616/kabylake crashes after hibernate, not after suspend-to-ram Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: steiner-reg@bio.ifi.lmu.de QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Created attachment 741046 --> http://bugzilla.opensuse.org/attachment.cgi?id=741046&action=edit /sys/class/drm/card0/error Hi, our laptop is Lenovo T570 with an i5-7200 CPU with HD 610 graphics: 00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02) It comes back without problems after suspend-to-ram, but fails after suspend-to-disk/hibernate. X comes back but immediately freezes and /var/log/messages shows: 2017-09-19T10:27:48.261833+02:00 helsinki kernel: [ 642.797969] [drm] GPU HANG: ecode 9:0:0xa43ff68b, in X [14823], reason: Hang on render ring, action: reset 2017-09-19T10:27:48.261866+02:00 helsinki kernel: [ 642.797975] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. 2017-09-19T10:27:48.261871+02:00 helsinki kernel: [ 642.797976] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel 2017-09-19T10:27:48.261875+02:00 helsinki kernel: [ 642.797977] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. 2017-09-19T10:27:48.261878+02:00 helsinki kernel: [ 642.797978] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. 2017-09-19T10:27:48.261882+02:00 helsinki kernel: [ 642.797980] [drm] GPU crash dump saved to /sys/class/drm/card0/error 2017-09-19T10:27:48.261885+02:00 helsinki kernel: [ 642.798092] drm/i915: Resetting chip after gpu hang 2017-09-19T10:27:48.261888+02:00 helsinki kernel: [ 642.798199] [drm] RC6 on 2017-09-19T10:27:48.273803+02:00 helsinki kernel: [ 642.811661] [drm] GuC firmware load skipped 2017-09-19T10:27:59.297801+02:00 helsinki kernel: [ 653.833722] drm/i915: Resetting chip after gpu hang 2017-09-19T10:27:59.297832+02:00 helsinki kernel: [ 653.833830] [drm] RC6 on 2017-09-19T10:27:59.309814+02:00 helsinki kernel: [ 653.848065] [drm] GuC firmware load skipped And after about 10 seconds, kdm restarts. dmesg output from boot and the bug situation: [ 3.708133] i915 0000:00:02.0: enabling device (0006 -> 0007) [ 3.722593] [drm] Finished loading i915/kbl_dmc_ver1_01.bin (v1.1) [ 3.742234] [drm] Initialized i915 1.6.0 20160919 for 0000:00:02.0 on minor 0 [ 5.595734] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 629.870249] [drm:gen9_set_dc_state [i915]] *ERROR* DC state mismatch (0x0 -> 0x2) [ 642.797977] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 642.798092] drm/i915: Resetting chip after gpu hang [ 653.833722] drm/i915: Resetting chip after gpu hang It works fine after deinstalling drm-kmp-default, but as far as I've read, the kabylake chips somehow need the newer code? We couldn't see any drawbacks without drm-kmp-default at the first glance. cu, Frank -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c1 --- Comment #1 from Frank Steiner <steiner-reg@bio.ifi.lmu.de> --- Created attachment 741048 --> http://bugzilla.opensuse.org/attachment.cgi?id=741048&action=edit Xorg.0.log -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c2 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> --- With drm-kmp-default uninstalled you fall back to generic framebuffer/fbdev on Leap 42.3, so no 2D/3D acceleration any longer. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c3 --- Comment #3 from Frank Steiner <steiner-reg@bio.ifi.lmu.de> --- Not only that: the hdmi output doesn't work without the drm module either (it's not even there). So, we'd prefer if someone was able to fix that bug in the drm-kmp-default code :-) If any further information would be helpful, let me know! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c5 --- Comment #5 from Frank Steiner <steiner-reg@bio.ifi.lmu.de> --- kernel-default-4.13.1-1.1.gc0b7e1f.x86_64.rpm works great! Not only w.r.t. graphics after hibernation and hdmi ouput, hibernation is also way faster than with the 4.4 kernel. Could we plase make 4.14 the default for 42.3 soon? :-) Seriously: knowing that the code in 4.13 works, is a prediction possible how long it will take to get drm-kmp-default-4.13 rpm? Working with the kotd so far, as it seems to be quite stable. Thanks for that hint! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c6 --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> --- There are no plans to update Leap 42.3 kernel to version 4.13. Neither is to update drm-kmp to this version. We'll try to fix this issue in existing drm-kmp though, *if* we can reproduce the issue. At least we now have a Lenovo Thinkpad T470 available for testing, which may suffer from the same problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com Flags| |needinfo?(tiwai@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tiwai@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c9 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |steiner-reg@bio.ifi.lmu.de Flags| |needinfo?(steiner-reg@bio.i | |fi.lmu.de) --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- Could you check whether the problem persists with the updated drm-kmp available at below? http://download.opensuse.org/repositories/home:/tiwai:/branches:/openSUSE:/L... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c11 --- Comment #11 from Frank Steiner <steiner-reg@bio.ifi.lmu.de> --- Yes, it persists, unfortunately. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(steiner-reg@bio.i | |fi.lmu.de) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c12 Max Staudt <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mstaudt@suse.com --- Comment #12 from Max Staudt <mstaudt@suse.com> --- Unfortunately we don't currently have testing hardware on hand to reproduce this :( Frank, do you still need this solved, or are you happy to use the KOTD until you can switch to Leap 15.0? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c13 --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- You can also try again the latest drm-kmp in Leap 42.3 update repo. It contains some previous regression regarding the PM, as well as a few more 4.9.y stable updates. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c14 --- Comment #14 from Frank Steiner <steiner-reg@bio.ifi.lmu.de> --- We'll try the latest rpm, otherwise I guess we can live with kotd until 15.0! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1059302 http://bugzilla.opensuse.org/show_bug.cgi?id=1059302#c15 Max Staudt <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #15 from Max Staudt <mstaudt@suse.com> --- Thanks Frank! Okay, so this should be fixed with the upcoming Leap 15.0 (kernel 4.12). But since we can't currently fix it for Leap 42.3, and this bug is for that version, let's call it RESOLVED WONTFIX. Thank you for reporting this bug! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com