Bug 104824

Summary: [skl] GPU hang code 9:0:0x85dffffb in Xorg
Product: Mesa Reporter: Peter Chubb <peter.chubb>
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED WORKSFORME 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:
Attachments: copy of /sys/class/drm/card0/error

Description Peter Chubb 2018-01-29 02:56:21 UTC
Created attachment 137012 [details]
copy of /sys/class/drm/card0/error

I'm running the top-of-tree Linux kernel; revision 1f07476ec143bbed7bf0b641749783b1094b4c4f

The X server randomly hangs; I can't work out what triggers the problem.  I'm not doing anything graphics intensive --- just emacs and xterms.  This can happen anywhere from a few minutes after boot to after several hours; but I haven't had a full day's work without a hang for a couple of weeks.

The bug is in a Dell laptop, that uses vga_switcheroo to swap between the i915 and an AMD  R9 M295X.  


dmesg output: 
GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2752], reason: Hang on rcs0, action: reset
[ 1798.822701] [drm] GPU hangs can indicate a bug anywhere in the entire gfx sta
ck, including userspace.
[ 1798.822702] [drm] Please file a _new_ bug report on bugs.freedesktop.org agai
nst DRI -> DRM/Intel
[ 1798.822702] [drm] drm/i915 developers can then reassign to the right componen
t if it's not a kernel issue.
[ 1798.822703] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1798.822704] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1798.822708] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1806.782831] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1814.846833] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1822.846846] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1830.814860] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1833.878873] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
Comment 1 Elizabeth 2018-03-06 19:38:21 UTC
Hi, which mesa version are you using? Thank you.
Comment 2 Peter Chubb 2018-03-06 21:07:25 UTC
The problem seems to have gone away on its own, with regular kernel updates.
Mesa is the Debian unstable packaged version: libegl-mesa0:amd64 17.3.6-1

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.