Bug 106214 - [skl] GPU HANG: ecode 9:0:0x86dffffd, in X (libreoffice)
Summary: [skl] GPU HANG: ecode 9:0:0x86dffffd, in X (libreoffice)
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-24 14:36 UTC by adrian.hospodar@gmail.com
Modified: 2019-09-25 19:10 UTC (History)
2 users (show)

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


Attachments
dmesg (92.50 KB, text/plain)
2018-04-24 15:38 UTC, adrian.hospodar@gmail.com
Details
GPU crash dump (114.93 KB, application/gzip)
2018-04-24 15:39 UTC, adrian.hospodar@gmail.com
Details

Description adrian.hospodar@gmail.com 2018-04-24 14:36:11 UTC
Frequently X crashes when using LibreOffice Impress.

Apr 24 17:14:12 linux-bub9 org.a11y.atspi.Registry[4327]:       after 429 requests (429 known processed) with 0 events remaining.
Apr 24 17:14:12 linux-bub9 org.a11y.atspi.Registry[4327]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Apr 24 17:14:12 linux-bub9 polkitd[1103]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.58, object path /org/kde/PolicyKit1/Authent
Apr 24 17:14:12 linux-bub9 org.kde.kglobalaccel[3692]: The X11 connection broke (error 1). Did the X11 server die?
Apr 24 17:14:12 linux-bub9 org.kde.KScreen[3692]: The X11 connection broke (error 1). Did the X11 server die?
Apr 24 17:14:12 linux-bub9 org.kde.kwalletd5[3692]: The X11 connection broke (error 1). Did the X11 server die?
Apr 24 17:14:12 linux-bub9 org.kde.kuiserver[3692]: kuiserver: Fatal IO error: client killed
Apr 24 17:14:12 linux-bub9 bluetoothd[1029]: Endpoint unregistered: sender=:1.65 path=/MediaEndpoint/A2DPSink
Apr 24 17:14:12 linux-bub9 bluetoothd[1029]: Endpoint unregistered: sender=:1.65 path=/MediaEndpoint/A2DPSource
Apr 24 17:14:12 linux-bub9 kernel: [drm] GuC firmware load skipped
Apr 24 17:14:12 linux-bub9 kernel: [drm] RC6 on
Apr 24 17:14:12 linux-bub9 kernel: drm/i915: Resetting chip after gpu hang
Apr 24 17:14:02 linux-bub9 kernel: [drm] GuC firmware load skipped
Apr 24 17:14:02 linux-bub9 kernel: [drm] RC6 on
Apr 24 17:14:02 linux-bub9 kernel: drm/i915: Resetting chip after gpu hang
Apr 24 17:14:02 linux-bub9 kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Apr 24 17:14:02 linux-bub9 kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Apr 24 17:14:02 linux-bub9 kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Apr 24 17:14:02 linux-bub9 kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Apr 24 17:14:02 linux-bub9 kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Apr 24 17:14:02 linux-bub9 kernel: [drm] GPU HANG: ecode 9:0:0x86dffffd, in X [3600], reason: Hang on render ring, action: reset

GPU crash dump is supposedly saved to /sys/class/drm/card0/error, but the file is empty.
Comment 1 Jani Saarinen 2018-04-24 15:27:40 UTC
What kernel, what system.
Have you tried latest drm-tip? https://cgit.freedesktop.org/drm-tip.
Also attach the “dmesg” output taken with “drm.debug=0xe” and “log-buf-len=2M”
Also attach dmesg from the boot.
Comment 2 adrian.hospodar@gmail.com 2018-04-24 15:38:29 UTC
Created attachment 139060 [details]
dmesg
Comment 3 adrian.hospodar@gmail.com 2018-04-24 15:39:44 UTC
Created attachment 139061 [details]
GPU crash dump
Comment 4 adrian.hospodar@gmail.com 2018-04-24 15:43:10 UTC
System
linux-bub9:~ # cat /etc/os-release
NAME="openSUSE Leap"
VERSION="42.3"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.3"
PRETTY_NAME="openSUSE Leap 42.3"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.3"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"

Kernel
linux-bub9:~ # uname -a
Linux linux-bub9 4.4.126-48-default #1 SMP Sat Apr 7 05:22:50 UTC 2018 (f24992c) x86_64 x86_64 x86_64 GNU/Linux

dmesg attached in dmesg.18_32_30
GPU crash in error.gz

Rest of info requested on the next crash.
Comment 5 Jani Saarinen 2018-04-24 15:45:48 UTC
Document system: 
CPU0: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (family: 0x6, model: 0x5e, stepping: 0x3)
Comment 6 Jani Saarinen 2018-04-24 15:46:17 UTC
Mika, Chris can you have a look.
Comment 7 GitLab Migration User 2019-09-25 19:10:57 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1719.


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.