| Summary: | [gen4] GPU HANG ecode 0:0x9f47f9fd, in chromium [28997], reason: Ring hung, action: reset | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Daniel Kahn Gillmor <dkg> |
| Component: | Drivers/DRI/i965 | Assignee: | Ian Romanick <idr> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
error output
dmesg from crashing machine |
||
|
Description
Daniel Kahn Gillmor
2014-12-02 16:30:50 UTC
Created attachment 110363 [details]
dmesg from crashing machine
I suspect this may be another duplicate of the bug 80568, fixed (worked-around) by this commit: commit c4fd0c9052dd391d6f2e9bb8e6da209dfc7ef35b Author: Kenneth Graunke <kenneth@whitecape.org> Date: Sat Jan 17 23:21:15 2015 -0800 i965: Work around mysterious Gen4 GPU hangs with minimal state changes. Gen4 hardware appears to GPU hang frequently when using Chromium, and also when running 'glmark2 -b ideas'. Most of the error states contain 3DPRIMITIVE commands in quick succession, with very few state packets between them - usually VERTEX_BUFFERS/ELEMENTS and CONSTANT_BUFFER. I trimmed an apitrace of the glmark2 hang down to two draw calls with a glUniformMatrix4fv call between the two. Either draw by itself works fine, but together, they hang the GPU. Removing the glUniform call makes the hangs disappear. In the hardware state, this translates to removing the CONSTANT_BUFFER packet between the two 3DPRIMITIVE packets. Flushing before emitting CONSTANT_BUFFER packets also appears to make the hangs disappear. I observed a slowdown in glxgears by doing it all the time, so I've chosen to only do it when BRW_NEW_BATCH and BRW_NEW_PSP are unset (i.e. we haven't done a CS_URB_STATE change or already flushed the whole pipeline). I'd much rather understand the problem, but at this point, I don't see how we'd ever be able to track it down further. We have no real tools, and the hardware people moved on years ago. I've analyzed 20+ error states and read every scrap of documentation I could find. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=80568 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=85367 Signed-off-by: Kenneth Graunke <kenneth@whitecape.org> Acked-by: Matt Turner <mattst88@gmail.com> Cc: "10.4 10.3" <mesa-stable@lists.freedesktop.org> It's in git, and backports are in Mesa 10.4.x for x > 3. Please try upgrading to >10.4.3. If it's resolved by such an upgrade, please mark as a duplicate of bug 80568. No reply. Marking as duplicate. *** This bug has been marked as a duplicate of bug 80568 *** I'm only running mesa 10.4.2 (debian sid has nothing newer) so i wasn't able to test this, sorry. however, trying to view the same video again on the same hardware with chromium doesn't cause a gnome crash any more, so i don't know how to replicate it anyway. thanks for the followup. (In reply to Daniel Kahn Gillmor from comment #4) > I'm only running mesa 10.4.2 (debian sid has nothing newer) so i wasn't able > to test this, sorry. however, trying to view the same video again on the > same hardware with chromium doesn't cause a gnome crash any more, so i don't > know how to replicate it anyway. thanks for the followup. Thanks. You might file a bug with Debian and suggest that they backport the patch to their 10.4.2. |
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.