Launchpad has imported 23 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=94161.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2016-02-15T16:34:18+00:00 Mikael-w wrote:
Created attachment 121772
GPU crash dump
I have experienced GPU hangs with all kernels after 4.3.
I'm running a MS Surface Pro 4.
Feb 15 17:27:22 hat kernel: [ 478.912402] [drm] stuck on render ring
Feb 15 17:27:22 hat kernel: [ 478.913345] [drm] GPU HANG: ecode
9:0:0x85df9fff, in gnome-shell [1956], reason: Ring hung, action: reset
Feb 15 17:27:22 hat kernel: [ 478.913357] [drm] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Feb 15 17:27:22 hat kernel: [ 478.913361] [drm] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Feb 15 17:27:22 hat kernel: [ 478.913364] [drm] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Feb 15 17:27:22 hat kernel: [ 478.913367] [drm] The gpu crash dump is required
to analyze gpu hangs, so please always attach it.
Feb 15 17:27:22 hat kernel: [ 478.913371] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Feb 15 17:27:22 hat kernel: [ 478.915833] drm/i915: Resetting chip after gpu
hang
Feb 15 17:27:24 hat kernel: [ 480.901312] [drm] RC6 on
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/0
On 2016-02-16T11:10:18+00:00 Christophe Prigent wrote:
Hi Mikael,
Which GPU is it: m3 Intel HD graphics 515 / i5 Intel HD graphics 520 / i7 Intel
Iris graphics?
Which steps are causing the GPU hang?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/1
On 2016-02-16T11:56:42+00:00 Mikael-w wrote:
It's Intel Iris (HD 540).
It's hard to say what exactly is causing it. Once it was caused by a
"tail -f /var/log/syslog" scrolling text in Gnome Terminal. Another time
it was caused by a web page being displayed in Firefox. A third time it
was caused by switching workspace in Gnome Shell.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/2
On 2016-02-16T12:01:27+00:00 Mikael-w wrote:
I should add that these hangs happen every other minute when things
change on the screen.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/3
On 2016-02-20T18:09:12+00:00 Ivan Giuliani wrote:
I seem to be affected by this as well (same GPU, on an XPS 13" (2016)).
Tried any kernel from 4.3 to 4.5 on Ubuntu, including the drm-intel-next
kernel (4.5.0-997-generic).
A workaround is to add i915.enable_rc6=0 to the kernel boot parameters.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/4
On 2016-02-24T21:43:24+00:00 Mikael-w wrote:
I have now tried this with the latest drm-intel kernel and the newest
skl-dcm firmware (1.26). My libdrm is 2.4.67.
The problem still persists.
A deterministic way to provoke the hang is to run glmark2
(github.com/glmark2).
I can confirm that if I give i915.enable_rc6=0 as a kernel option, the
problem disappears.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/5
On 2016-03-01T20:42:51+00:00 Chris Wilson wrote:
*** Bug 94029 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/6
On 2016-03-02T21:04:46+00:00 Chris Wilson wrote:
To attempt to distinguish another source of bugs, does
intel_pstate=disable make any difference?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/7
On 2016-03-02T21:43:13+00:00 Mikael-w wrote:
(In reply to Chris Wilson from comment #7)
> To attempt to distinguish another source of bugs, does intel_pstate=disable
> make any difference?
Replacing i915.enable_rc6=0 with intel_pstate=disable reintroduces the
GPU crashes.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/8
On 2016-03-10T12:50:29+00:00 Chris Wilson wrote:
*** Bug 94462 has been marked as a duplicate of this bug. ***
Reply at:
