Bug 99719 - GPU HANG: ecode 9:0:0xe3cfbccb, in Xorg [1196], reason: Hang on render ring, action: reset
Summary: GPU HANG: ecode 9:0:0xe3cfbccb, in Xorg [1196], reason: Hang on render ring, ...
Status: CLOSED DUPLICATE of bug 96526
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-09 07:13 UTC by leonard
Modified: 2017-07-24 22:39 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
GPU crash dump (608.46 KB, text/plain)
2017-02-09 07:13 UTC, leonard
no flags Details
lswh (12.35 KB, text/plain)
2017-02-09 07:18 UTC, leonard
no flags Details
lshw (12.35 KB, text/plain)
2017-02-09 07:18 UTC, leonard
no flags Details
lsusb (235 bytes, text/plain)
2017-02-09 07:20 UTC, leonard
no flags Details
lspci (1.41 KB, text/plain)
2017-02-09 07:20 UTC, leonard
no flags Details

Description leonard 2017-02-09 07:13:23 UTC
Created attachment 129418 [details]
GPU crash dump

DMESG output requested me to file a _new_ bug here.

Please let me know if you need any additional information. The system is a Xiaomi MiBook Air ( http://www.mi.com/mibookair/ ) where the intel onboard graphics is configured to run the X server and the nvidia graphics card is only used for CUDA stuff (i.e. does not interfere with X at all). The crash occurred after a wake up from hibernation.
Comment 1 leonard 2017-02-09 07:18:28 UTC
Created attachment 129419 [details]
lswh
Comment 2 leonard 2017-02-09 07:18:57 UTC
Created attachment 129420 [details]
lshw
Comment 3 leonard 2017-02-09 07:20:01 UTC
Created attachment 129421 [details]
lsusb
Comment 4 leonard 2017-02-09 07:20:18 UTC
Created attachment 129422 [details]
lspci
Comment 5 Chris Wilson 2017-02-09 07:59:32 UTC

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


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.