<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=101991#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=101991">bug 101991</a> from <a class="email" href="mailto:thiago@kde.org" title="Thiago Macieira <thiago@kde.org>"> Thiago Macieira</a> <pre>(In reply to Elizabeth from <a href="show_bug.cgi?id=101991#c11">comment #11</a>) > (In reply to Thiago Macieira from <a href="show_bug.cgi?id=101991#c9">comment #9</a>) > > ... How many more hangs are necessary?... > Hello Thiago, the idea is to identify a pattern. Any event that triggers the > hang, hangs ecode repeating constantly, similar or same dmesg > warnings/errors/messages repeating just before the hang happening, etc. The only pattern I've identified so far is that it happens within 2 hours of resuming from hibernation. I'll try to narrow the time down. I can tell you it's not related to the USB-C dock being plugged, since this morning it happened without the dock being in use (hadn't been for over 60 hours). > Maybe it would be possible to get a dmesg with debug info since it seems to > repeat. Just add drm.debug=0x1e log_bug_len=2M to the grub. I'll do that.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>