Created attachment 125657 [details] gpu crash dump I got saw the following error message in my logs: Aug 9 15:10:54 akranes kernel: [61815.338088] [drm] stuck on render ring Aug 9 15:10:54 akranes kernel: [61815.339390] [drm] GPU HANG: ecode 6:0:0x85fffffc, in Xorg [6025], reason: Ring hung, action: reset Aug 9 15:10:54 akranes kernel: [61815.339396] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Aug 9 15:10:54 akranes kernel: [61815.339398] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Aug 9 15:10:54 akranes kernel: [61815.339399] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Aug 9 15:10:54 akranes kernel: [61815.339401] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Aug 9 15:10:54 akranes kernel: [61815.339403] [drm] GPU crash dump saved to /sys/class/drm/card0/error Aug 9 15:10:54 akranes kernel: [61815.342233] drm/i915: Resetting chip after gpu hang Attached is the GPU crash dump. This is on the same laptop as bug 97247 and bug 93505. 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) -- system architecture: amd64 -- xserver-xorg-video-intel 2:2.99.917+git20160706-1 -- xserver-xorg-core 2:1.18.4-1 -- libdrm-intel1 2.4.70-1 -- mesa: libegl1-mesa:amd64 11.2.2-1 -- kernel: 4.6.4-1+grsec201607242014+1 -- Linux distribution: Debian Sid -- Machine or mobo model: Lenovo ThinkPad T420 -- Display connector: internal
Created attachment 125658 [details] Xorg log Looks like it's using the modesetting driver: [ 78.646] (==) Matched modesetting as autoconfigured driver 0 [ 78.646] (==) Matched fbdev as autoconfigured driver 1 [ 78.646] (==) Matched vesa as autoconfigured driver 2 [ 78.646] (==) Assigned the driver to the xf86ConfigLayout [ 78.646] (II) LoadModule: "modesetting" [ 78.647] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 78.647] (II) Module modesetting: vendor="X.Org Foundation" [ 78.647] compiled for 1.18.4, module version = 1.18.4 [ 78.647] Module class: X.Org Video Driver [ 78.647] ABI class: X.Org Video Driver, version 20.0 Attached is the full ~/.local/share/xorg/Xorg.1.log file.
Also, it might be worth noting (as per bug 93505) that I've got ppgtt disabled: $ cat /sys/module/i915/parameters/enable_ppgtt 0 $ cat /etc/modprobe.d/i915.conf # https://wiki.archlinux.org/index.php/Intel#Module-based_Powersaving_Options options i915 enable_rc6=1 enable_ppgtt=0
The HANG occurred 3 more times in the last couple of hours: Aug 9 22:38:48 akranes kernel: [88689.588305] [drm] stuck on render ring Aug 9 22:38:48 akranes kernel: [88689.589489] [drm] GPU HANG: ecode 6:0:0x94eeffb8, in Xorg [6025], reason: Ring hung, action: reset Aug 9 22:38:48 akranes kernel: [88689.592062] drm/i915: Resetting chip after gpu hang Aug 10 00:30:18 akranes kernel: [95380.003563] [drm:ffffffffc02489e7] *ERROR* Atomic update failure on pipe A (start=3049292 end=3049293) time 215 us, min 894, max 899, scanline start 889, end 901 Aug 10 00:51:33 akranes kernel: [96654.613677] [drm] stuck on render ring Aug 10 00:51:33 akranes kernel: [96654.614899] [drm] GPU HANG: ecode 6:0:0x86fafffa, in Xorg [6025], reason: Ring hung, action: reset Aug 10 00:51:33 akranes kernel: [96654.617189] drm/i915: Resetting chip after gpu hang Aug 10 01:01:17 akranes kernel: [97238.653662] [drm] stuck on render ring Aug 10 01:01:17 akranes kernel: [97238.655145] [drm] GPU HANG: ecode 6:0:0x86fafffa, in Xorg [6025], reason: Ring hung, action: reset Aug 10 01:01:17 akranes kernel: [97238.657011] drm/i915: Resetting chip after gpu hang
Hello, the bugs mentioned on the description are closed now, and it seems that the software used were too old. Is this still valid with the latest versions released? Thank you.
I've not run into this problem in a while.
-- 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/1533.
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.