Summary: | [BSW] Aztec Ruins benchmark crashes | ||
---|---|---|---|
Product: | Mesa | Reporter: | Clayton Craft <clayton.a.craft> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | /sys/class/drm/card0/error |
Description
Clayton Craft
2018-02-22 16:54:25 UTC
FWIW, gl_5_normal seems to be working fine on my HD 405 (BSW). Created attachment 137809 [details]
/sys/class/drm/card0/error
I am still seeing this with recent commits to master. There was a GPU hang when this occurs: [Mar 5 19:08] [drm] GPU HANG: ecode 8:0:0x85dffffb, in testfw_app [2297], reason: Hang on rcs0, action: reset GPU is identified as the following in glxinfo: Device: Mesa DRI Intel(R) HD Graphics 400 (Braswell) (0x22b1) OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 400 (Braswell) Clayton's error state looks just like Eero's, so I'm pretty sure they're hitting the same bug. Clayton's is on HD 400, while I tested HD 405, so maybe there's something specific to that model. Resolving as a dup of Eero's bug. *** This bug has been marked as a duplicate of bug 104636 *** |
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.