<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - The big SKQP bug" href="https://bugs.freedesktop.org/show_bug.cgi?id=105301#c31">Comment # 31</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - The big SKQP bug" href="https://bugs.freedesktop.org/show_bug.cgi?id=105301">bug 105301</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>(In reply to Kenneth Graunke from <a href="show_bug.cgi?id=105301#c30">comment #30</a>) > (In reply to Dongseong Hwang from <a href="show_bug.cgi?id=105301#c28">comment #28</a>) > > Created <a href="attachment.cgi?id=142282" name="attach_142282" title="error state decoded by latest decoder">attachment 142282</a> <a href="attachment.cgi?id=142282&action=edit" title="error state decoded by latest decoder">[details]</a> > > error state decoded by latest decoder > > > > btw, let me upload the decoded error state decoded by latest decoder, which > > belongs to chromeos itself. > > I got this error state in kernel version v4.14 chromeos and decode it in the > > device. > > > > Kenneth, Zhang, does it look sane? > > That's still a garbage decoder. We're also not going to get anywhere > looking at the error state at this point. By the way, you can tell because of all the "Bad length X in (null)" and "3D UNKNOWN: 3d_965 opcode = 0x7824" messages. It's clearly struggling to decode. That's because intel_error_decode uses a libdrm decoder that hasn't been updated in roughly 6 years. aubinator_error_decode works. Most people just post the raw decodes, so people can decode them using whatever tools, though :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>