Bug 101836 - [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1936], reason: Engine(s) hung,
Summary: [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1936], reason: Engine(s) hung,
Status: CLOSED DUPLICATE of bug 98999
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-19 06:09 UTC by Matthias
Modified: 2017-10-06 21:17 UTC (History)
1 user (show)

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


Attachments
error log file (457.13 KB, text/plain)
2017-07-19 09:26 UTC, Matthias
no flags Details
Xorg Log (51.70 KB, text/x-log)
2017-07-20 04:27 UTC, Matthias
no flags Details
Output lspci (29.51 KB, text/plain)
2017-07-20 04:28 UTC, Matthias
no flags Details

Description Matthias 2017-07-19 06:09:54 UTC
[ 6899.102492] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 6899.102493] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 6899.102494] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 6899.102495] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 6899.102497] [drm] GPU crash dump saved to /sys/class/drm/card1/error
[ 6899.104487] drm/i915: Resetting chip after gpu hang


Error File ist empty
Comment 1 Chris Wilson 2017-07-19 09:09:44 UTC
Oh no it is not. That file is never empty, at the minimum it says "No error state collected".
Comment 2 Matthias 2017-07-19 09:26:39 UTC
Created attachment 132753 [details]
error log file
Comment 3 Matthias 2017-07-19 09:27:26 UTC
Sorry, had to become root to read it.
Comment 4 Elizabeth 2017-07-19 14:37:11 UTC
(In reply to Matthias from comment #2)
> Created attachment 132753 [details]
> error log file

Hello Matthias, 
Could you please add HW and SW information and attach dmesg with drm.debug=0xe parameter on grub from boot, also is there any steps to reproduce it?
Thanks
Comment 5 Matthias 2017-07-20 04:27:36 UTC
Created attachment 132781 [details]
Xorg Log
Comment 6 Matthias 2017-07-20 04:28:00 UTC
Created attachment 132782 [details]
Output lspci
Comment 7 Matthias 2017-07-20 04:30:25 UTC
Hello Elizabeth,

Hardware ist Dell Precision 3510, see Xorg-Log and output of lspci attached.
Error ist not reproduceable, Everything is frozen for a few seconds, afterwards I can continue. It happens 3-5 times a day. Laptop is in docking station with two Full HD monitors connected.

Thanks

Matthias
Comment 8 Elizabeth 2017-07-20 14:33:40 UTC
(In reply to Matthias from comment #7)
> Hello Elizabeth,
> 
> Hardware ist Dell Precision 3510, see Xorg-Log and output of lspci attached.
> Error ist not reproduceable, Everything is frozen for a few seconds,
> afterwards I can continue. It happens 3-5 times a day. Laptop is in docking
> station with two Full HD monitors connected.
> 
> Thanks
> 
> Matthias

Hello again,
I noticed your using a docking station. It seems that some features for this devices had been included on 4.12 and up, https://www.kernel.org/, could you please try with the latest kernel or drm-tip, https://cgit.freedesktop.org/drm-tip, thanks.
Comment 9 Matt Spraggs 2017-10-06 15:19:26 UTC
+1 for encountering this bug whilst using 2 HD monitors with a Dell docking station.
Comment 10 Chris Wilson 2017-10-06 17:08:38 UTC
commit 4acd4a7d3d2f41227022fa7581cfb85a0b124eae
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Dec 5 15:13:24 2016 +0000

    sna/gen9: Emit a dummy primitive between VertexElements
    
    References: https://bugs.freedesktop.org/show_bug.cgi?id=98999
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

*** This bug has been marked as a duplicate of bug 98999 ***


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.