Bug 100649

Summary:	Xserver crashes
Product:	Mesa	Reporter:	freedesktop_2017
Component:	Drivers/DRI/i965	Assignee:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Status:	RESOLVED MOVED	QA Contact:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:	GPU hang
Attachments:	gpu crash dump

Description freedesktop_2017 2017-04-11 04:01:28 UTC

Hello,

On a up to date Debian Testing machine I am having issues with the xserver freezing then crashing.

Here are hopefully all the relevant versions:
ii  x11-xserver-utils                     7.7+7+b1                              amd64        X server utilities
ii  xserver-common                        2:1.19.2-1                            all          common files used by various X servers
ii  xserver-xephyr                        2:1.19.2-1                            amd64        nested X server
ii  xserver-xorg                          1:7.7+18                              amd64        X.Org X server
ii  xserver-xorg-core                     2:1.19.2-1                            amd64        Xorg X server - core server
ii  xserver-xorg-input-all                1:7.7+18                              amd64        X.Org X server -- input driver metapackage
ii  xserver-xorg-input-evdev              1:2.10.5-1                            amd64        X.Org X server -- evdev input driver
ii  xserver-xorg-input-libinput           0.23.0-2                              amd64        X.Org X server -- libinput input driver
ii  xserver-xorg-input-mouse              1:1.9.2-1+b1                          amd64        X.Org X server -- mouse input driver
ii  xserver-xorg-input-synaptics          1.9.0-1+b1                            amd64        Synaptics TouchPad driver for X.Org server
ii  xserver-xorg-input-wacom              0.34.0-1                              amd64        X.Org X server -- Wacom input driver
ii  xserver-xorg-legacy                   2:1.19.2-1                            amd64        setuid root Xorg server wrapper
ii  xserver-xorg-video-all                1:7.7+18                              amd64        X.Org X server -- output driver metapackage
ii  xserver-xorg-video-amdgpu             1.2.0-1+b1                            amd64        X.Org X server -- AMDGPU display driver
ii  xserver-xorg-video-ati                1:7.8.0-1+b1                          amd64        X.Org X server -- AMD/ATI display driver wrapper
ii  xserver-xorg-video-cirrus             1:1.5.3-1+b2                          amd64        X.Org X server -- Cirrus display driver
ii  xserver-xorg-video-fbdev              1:0.4.4-1+b5                          amd64        X.Org X server -- fbdev display driver
ii  xserver-xorg-video-intel              2:2.99.917+git20161206-1              amd64        X.Org X server -- Intel i8xx, i9xx display driver
ii  xserver-xorg-video-mach64             6.9.5-1+b2                            amd64        X.Org X server -- ATI Mach64 display driver
ii  xserver-xorg-video-mga                1:1.6.5-1                             amd64        X.Org X server -- MGA display driver
ii  xserver-xorg-video-neomagic           1:1.2.9-1+b2                          amd64        X.Org X server -- Neomagic display driver
ii  xserver-xorg-video-nouveau            1:1.0.13-2                            amd64        X.Org X server -- Nouveau display driver
ii  xserver-xorg-video-openchrome         1:0.5.0-3                             amd64        X.Org X server -- VIA display driver
ii  xserver-xorg-video-qxl                0.1.4+20161126git4d7160c-1            amd64        X.Org X server -- QXL display driver
ii  xserver-xorg-video-r128               6.10.2-1                              amd64        X.Org X server -- ATI r128 display driver
ii  xserver-xorg-video-radeon             1:7.8.0-1+b1                          amd64        X.Org X server -- AMD/ATI Radeon display driver
ii  xserver-xorg-video-savage             1:2.3.9-1                             amd64        X.Org X server -- Savage display driver
ii  xserver-xorg-video-siliconmotion      1:1.7.9-2                             amd64        X.Org X server -- SiliconMotion display driver
ii  xserver-xorg-video-sisusb             1:0.9.7-1                             amd64        X.Org X server -- SiS USB display driver
ii  xserver-xorg-video-tdfx               1:1.4.7-1                             amd64        X.Org X server -- tdfx display driver
ii  xserver-xorg-video-trident            1:1.3.8-1                             amd64        X.Org X server -- Trident display driver
ii  xserver-xorg-video-vesa               1:2.3.4-1+b2                          amd64        X.Org X server -- VESA display driver
ii  xserver-xorg-video-vmware             1:13.2.1-1+b1                         amd64        X.Org X server -- VMware display driver


The messages log tells me to make a bug report here so I am doing so.

Apr 10 12:32:14 bluesky kernel: [179113.599612] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2253], reason: Hang on render ring, action: reset
Apr 10 12:32:14 bluesky kernel: [179113.599615] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Apr 10 12:32:14 bluesky kernel: [179113.599616] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Apr 10 12:32:14 bluesky kernel: [179113.599617] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Apr 10 12:32:14 bluesky kernel: [179113.599618] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Apr 10 12:32:14 bluesky kernel: [179113.599620] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Apr 10 12:32:14 bluesky kernel: [179113.599665] drm/i915: Resetting chip after gpu hang
Apr 10 12:32:14 bluesky kernel: [179113.599729] [drm] RC6 on
Apr 10 12:32:14 bluesky kernel: [179113.613306] [drm] GuC firmware load skipped
Apr 10 12:32:25 bluesky kernel: [179124.607082] drm/i915: Resetting chip after gpu hang
Apr 10 12:32:25 bluesky kernel: [179124.607146] [drm] RC6 on
Apr 10 12:32:25 bluesky kernel: [179124.621291] [drm] GuC firmware load skipped

Unfortunately the box in question has gotten rebooted since the issue so now the crash dump is missing.  I will try and capture one next time this happens.  Anything else I can do in the meantime to debug this?

Comment 1 Jari Tahvanainen 2017-04-11 11:56:47 UTC

Similar Bug 100642. Waiting for crash dump ...

Comment 2 freedesktop_2017 2017-04-11 22:33:24 UTC

Created attachment 130808 [details]
gpu crash dump

Comment 3 freedesktop_2017 2017-04-11 22:34:32 UTC

Crashed again, I was able to get the crashdump this time which I have attached.

Messages looks about the same as last time:
Apr 11 14:52:27 bluesky kernel: [79075.686491] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2275], reason: Hang on render ring, action: reset
Apr 11 14:52:27 bluesky kernel: [79075.686494] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Apr 11 14:52:27 bluesky kernel: [79075.686496] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Apr 11 14:52:27 bluesky kernel: [79075.686497] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Apr 11 14:52:27 bluesky kernel: [79075.686498] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Apr 11 14:52:27 bluesky kernel: [79075.686500] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Apr 11 14:52:27 bluesky kernel: [79075.686550] drm/i915: Resetting chip after gpu hang
Apr 11 14:52:27 bluesky kernel: [79075.686615] [drm] RC6 on
Apr 11 14:52:27 bluesky kernel: [79075.700196] [drm] GuC firmware load skipped
Apr 11 14:52:37 bluesky kernel: [79085.701950] drm/i915: Resetting chip after gpu hang
Apr 11 14:52:37 bluesky kernel: [79085.702021] [drm] RC6 on
Apr 11 14:52:37 bluesky kernel: [79085.718141] [drm] GuC firmware load skipped

Comment 4 freedesktop_2017 2017-04-13 20:03:55 UTC

Is there anything else I can provide?

Comment 5 GitLab Migration User 2019-09-25 19:01:22 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/1587.

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.