Created attachment 137180 [details]
Kernel: 4.15.0 (openSUSE's build 1)
Platform: Dell XPS 13 9350, Intel(R) Core(TM) i7-6560U CPU
Dell BIOS: 1.5.1
[drm] GPU HANG: ecode 9:-1:0x00000000, reason: Kicking stuck wait on bcs0, action: continue
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
card0/error file attached.
Similar to bug #101991, but not the same. That bug has as a defining characteristic the use of hibernation. This problem now happened without hibernating, though I did suspend twice and connected to a Dell dock and to an external monitor via USB-C.
Uptime was about 24 hours. That was my first boot using kernel 4.15. This problem was not observed when using 4.14 and earlier kernels.
That's not the right DERRMR, someone (fw? dmc probably) has been fiddling.
(In reply to Chris Wilson from comment #1)
> DERRMR: 0x2077efef
> That's not the right DERRMR, someone (fw? dmc probably) has been fiddling.
Yes, it saves/restores it's value across DC5/6 state transitions. It could be the corruption issue:
(In reply to Thiago Macieira from comment #0)
> DMC: 1.26
so could you try version 1.27 where that's fixed?
Author: Anusha Srivatsa <firstname.lastname@example.org>
Date: Thu Nov 9 17:18:32 2017 -0800
drm/i915/skl: DMC firmware for skylake v1.27
Yes, we need to start backporting these:/
(In reply to Imre Deak from comment #2)
> > DMC: 1.26
> so could you try version 1.27 where that's fixed?
I asked Anusha and the reply I got is that 1.27 is loaded only by the kernel that has been tested with 1.27. The file is sitting there in /lib/firmware, but doesn't get loaded by the kernel.
I'm told that won't happen until kernel 4.16.
Also please note that 4.14 and earlier have been using 1.26 without this particular problem. I'm reporting it in case it's a new regression.
$ ls -l /lib/firmware/i915/skl_dmc_ver1*
-rw-r--r-- 1 root root 8824 jan 4 07:06 /lib/firmware/i915/skl_dmc_ver1_23.bin
-rw-r--r-- 1 root root 8928 jan 4 07:06 /lib/firmware/i915/skl_dmc_ver1_26.bin
-rw-r--r-- 1 root root 8928 jan 4 07:06 /lib/firmware/i915/skl_dmc_ver1_27.bin
lrwxrwxrwx 1 root root 19 jan 4 07:06 /lib/firmware/i915/skl_dmc_ver1.bin -> skl_dmc_ver1_26.bin
> commit 39ccc9852e2b46964c9c44eba52db57413ba6d27
> Author: Anusha Srivatsa <email@example.com>
> Date: Thu Nov 9 17:18:32 2017 -0800
> drm/i915/skl: DMC firmware for skylake v1.27
> Yes, we need to start backporting these:/
That would be appreciated. I can't build my own kernels (secure boot).
First of all. Sorry about spam.
This is mass update for our bugs.
Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!
If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Closing, please re-open is issue still exists.