| Summary: | [BDW] GPU HANG: ecode 8:0:0x8ed9fff2, in RenderThread 1 [16790], reason: Hang on render ring, action: reset (StellarOverload) | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Chris O <christia.n.ouellet> |
| Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | anuj.phogat, intel-gfx-bugs |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
/sys/class/drm/card0/error
syslog find GPU HANG apitrace apitrace, 2 of 5 apitrace, 3 of 5 apitrace, 4 of 5 apitrace, 5 of 5 |
||
Created attachment 127398 [details]
syslog find GPU HANG
Mesa version OpenGL version string: 3.0 Mesa 12.1.0-devel libdrm-intel1 version 2.4.71+git1610170956.a44c9c~gd~y libgl1-mesa-dri 12.1~git1610181930.21af69~gd~y Could you please capture and upload an apitrace (https://github.com/apitrace/apitrace) for a developer to use to reproduce the hang? Then please reset the bug's state to REOPENED. Created attachment 127933 [details]
apitrace
apitrace, file 1 of 5
Created attachment 127934 [details]
apitrace, 2 of 5
Created attachment 127935 [details]
apitrace, 3 of 5
Created attachment 127936 [details]
apitrace, 4 of 5
Created attachment 127937 [details]
apitrace, 5 of 5
Join the 5 apitrace files parts first to reconstitute the full apitrace.
Reproduced this hang with mesa master commit 3ff9f8c on SKL, kernel 4.7.10-100.fc23.x86_64. I couldn't reproduce the issue on SKL with Mesa master commit abcaba4, kernel 4.8.15-300.fc25.x86_64. So, something has fixed it between commit 3ff9f8c and abcaba4. Can you test it on BDW too? Based on the results of my testing on SKL, I'm closing this bug. |
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.
Created attachment 127397 [details] /sys/class/drm/card0/error 1- Launch game executable .steam/steam/steamapps/common/Stellar\ Overload/StellarOverloadEA1/Binaries/Linux/StellarOverload 2- Start a new game 3- Select histoy mode 4- Click Play on avatar screen 5- Game display a load progess bar, at 75%, display freeze, mouse also, then in the terminal I see the message : intel_do_flush_locked failed: Input/output error pure virtual method called In dmesg out I see : [11040.531420] [drm] GPU HANG: ecode 8:0:0x8ed9fff2, in RenderThread 1 [16790], reason: Hang on render ring, action: reset [11040.531423] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [11040.531424] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [11040.531425] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [11040.531426] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [11040.531428] [drm] GPU crash dump saved to /sys/class/drm/card0/error [11040.531512] drm/i915: Resetting chip after gpu hang [11050.544688] drm/i915: Resetting chip after gpu hang [14222.447331] drm/i915: Resetting chip after gpu hang [14232.462464] drm/i915: Resetting chip after gpu hang -- system architecture: x86_64 -- kernel version: 4.8.0-25-generic -- Linux distribution: Ubuntu 16.10 -- Machine or mother board model: NUC5i5RYB, i5-5250U CPU, HD Graphics 6000 -- Display connector: HDMI