Bug 98747 - [HSW] GPU HANG: ecode 7:0:0x87d3ffff, in gnome-shell [443], reason: Hang on render ring, action: reset
Summary: [HSW] GPU HANG: ecode 7:0:0x87d3ffff, in gnome-shell [443], reason: Hang on r...
Status: CLOSED INVALID
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: 2016-11-16 16:19 UTC by Cédric Bellegarde
Modified: 2016-11-18 08:11 UTC (History)
1 user (show)

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

Attachments
Kernel trace (1.04 MB, text/plain)
2016-11-16 16:19 UTC, Cédric Bellegarde 		no flags Details
View All

Description Cédric Bellegarde 2016-11-16 16:19:41 UTC 
Created attachment 128013 [details]
Kernel trace

Here on ArchLinux running last stable Linux kernel and last stable mesa version, I get a GPU Hang when using gdm/gnome-shell.

Linux kernel: 4.8.8
Mesa: 13.0.1
libdrm: 2.4.73

Attachement: kernel trace
Comment 1 yann 2016-11-16 17:32:01 UTC 
Man can notice :
ERROR: 0x00000105
    TLB page fault error (GTT entry not valid)
    Invalid page directory entry error
    Cacheline containing a PD was marked as invalid

Can you try to update your kernel with latest drm-intel-nightly or linux mailine (4.9.rc5) and see if this is still occuring?

Can you attach your kernel log (ie dmesg)? You may add "drm.debug=0x1e log_buf_len=1M" in your boot command line to collect more debug data.
Comment 2 Cédric Bellegarde 2016-11-17 22:00:31 UTC 
Closing, moving Hard Disk in another computer (same model) and it works... So it's a hardware failure.
Comment 3 yann 2016-11-18 08:11:50 UTC 
(In reply to Cédric Bellegarde from comment #2)
> Closing, moving Hard Disk in another computer (same model) and it works...
> So it's a hardware failure.

thanks for your feedback, closing bug then

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.