<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@kms_frontbuffer_tracking@*psr* - fail - Failed assertion: psr_wait_entry(drm.debugfs), PSR still disabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=109355#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@kms_frontbuffer_tracking@*psr* - fail - Failed assertion: psr_wait_entry(drm.debugfs), PSR still disabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=109355">bug 109355</a> from <a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> Martin Peres</a> <pre>(In reply to Jose Roberto de Souza from <a href="show_bug.cgi?id=109355#c3">comment #3</a>) > Yep another panel with a not reliable PSR implementation. > Our options are swap the panel or add PSR tests running into ICLB7 to the CI > whitelist. I wonder how common these panels are in practice. I don't really care if this is just bad panels we use for testing, but if user machines tend to have these non-working panels, we should maybe try a little harder or find workarounds. I'll add this panel to list of non-functioning panels.</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> <li>You are on the CC list for the bug.</li> </ul> </body> </html>