Bug 103870 - [ILK] GPU HANG: ecode 5:0:0xfdffffff, in Xwayland [4803], reason: Hang on rcs0, action: reset
Summary: [ILK] GPU HANG: ecode 5:0:0xfdffffff, in Xwayland [4803], reason: Hang on rcs...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard: ReadyForDev
Keywords:
: 104901 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-11-23 19:20 UTC by Christian Stadelmann
Modified: 2018-05-21 21:19 UTC (History)
5 users (show)

See Also:
i915 platform: ILK
i915 features: GPU hang


Attachments
Contents of /sys/class/drm/card0/error (5.65 KB, application/x-xz)
2017-11-23 19:20 UTC, Christian Stadelmann
Details
relevant syslog span (26.35 KB, text/plain)
2017-11-23 19:21 UTC, Christian Stadelmann
Details
dmesg output (144.99 KB, text/plain)
2017-11-23 19:21 UTC, Christian Stadelmann
Details
/sys/class/drm/card0/error (98.90 KB, text/plain)
2018-02-02 15:13 UTC, Clemens Eisserer
Details
syslog (787.77 KB, application/x-bzip)
2018-02-02 15:14 UTC, Clemens Eisserer
Details

Description Christian Stadelmann 2017-11-23 19:20:34 UTC
Created attachment 135684 [details]
Contents of /sys/class/drm/card0/error

I was playing a Video inside a GNOME/Wayland session using vlc (as XWayland client, not with wayland Qt backend). The video did stutter very much and gnome-shell was nearly frozen, i.e. input was delayed by several seconds. Finally, VLC crashed and gnome-shell and XWayland were back to normal. I had a look in the logs (will attach syslog later) and there I found the GPU HANG.

Additional information:
$ uname -a
Linux hostname 4.13.13-200.fc26.x86_64 #1 SMP Wed Nov 15 15:46:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Distribution: Fedora 26

Reproducible? unclear.

Hardware: Intel Core i5 650 with integrated GPU ("Intel HD Graphics"). No separate ("discrete") GPU.

Installed software versions:
xorg-x11-server-Xwayland-1.19.3-4.fc26.x86_64
libwayland-client-1.13.0-1.fc26.x86_64
libdrm-2.4.88-1.fc26.x86_64
mesa-dri-drivers-17.2.4-2.fc26.x86_64
xorg-x11-drv-intel-2.99.917-28.20160929.fc26.x86_64
kernel-4.13.14-200.fc26.x86_64
gnome-shell-3.24.3-2.fc26.x86_64
mutter-3.24.4-2.fc26.x86_64
mesa-libGL-17.2.4-2.fc26.x86_64
Comment 1 Christian Stadelmann 2017-11-23 19:21:19 UTC
Created attachment 135685 [details]
relevant syslog span
Comment 2 Christian Stadelmann 2017-11-23 19:21:52 UTC
Created attachment 135686 [details]
dmesg output
Comment 3 Christian Stadelmann 2017-11-23 19:25:04 UTC
Maybe a duplicate of bug #103502?
Comment 4 Chris Wilson 2017-11-23 21:24:16 UTC
That error state appears incomplete. Please attach the original?
Comment 5 Christian Stadelmann 2017-11-24 00:13:57 UTC
(In reply to Chris Wilson from comment #4)
> That error state appears incomplete. Please attach the original?

Sorry, that is the original. I got it from "cat /sys/class/drm/card0/error".
Comment 6 Chris Wilson 2017-12-22 21:02:02 UTC
The problem is that error state is missing the batch contents, contexts, rings, status pages, without which we cannot triage the hang.
Comment 7 Elizabeth 2018-02-01 17:24:52 UTC
*** Bug 104901 has been marked as a duplicate of this bug. ***
Comment 8 Clemens Eisserer 2018-02-01 17:58:41 UTC
I can reproduce this also with VLC, is there something I can do to get this fixed?
Comment 9 Elizabeth 2018-02-01 22:35:36 UTC
I looks like the error state is not retrieving the ring's batchs. A dmesg with debug information may help, parameters drm.debug=0x1e log_bug_len=2M(or bigger if needed) in grub.
Comment 10 Clemens Eisserer 2018-02-02 15:13:46 UTC
Created attachment 137132 [details]
/sys/class/drm/card0/error
Comment 11 Clemens Eisserer 2018-02-02 15:14:12 UTC
Created attachment 137133 [details]
syslog
Comment 12 Chris Wilson 2018-02-07 21:56:09 UTC
Reasonable presumption that the error states are for the same bug.
Comment 13 Elizabeth 2018-02-14 22:26:20 UTC
Hello everyone, could you try mesa 18 and share results? Thank you.
Comment 14 Christian Stadelmann 2018-05-21 21:19:40 UTC
Works fine now, I cannot reproduce the issue any more.

xorg-x11-server-Xwayland-1.19.6-8.fc28.x86_64
libwayland-client-1.15.0-1.fc28.x86_64
libdrm-2.4.92-1.fc28.x86_64
mesa-dri-drivers-18.0.2-1.fc28.x86_64
xorg-x11-drv-intel-2.99.917-32.20171025.fc28.x86_64
kernel-4.16.9-300.fc28.x86_64
gnome-shell-3.28.2-1.fc28.x86_64
mutter-3.28.2-1.fc28.x86_64
mesa-libGL-18.0.2-1.fc28.x86_64


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.