<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_cursor_crc@pipe-[abc]-cursor-suspend - incomplete - ACPI: EC: interrupt blocked" href="https://bugs.freedesktop.org/show_bug.cgi?id=110741#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@kms_cursor_crc@pipe-[abc]-cursor-suspend - incomplete - ACPI: EC: interrupt blocked" href="https://bugs.freedesktop.org/show_bug.cgi?id=110741">bug 110741</a> from <a class="email" href="mailto:vanshidhar.r.konda@intel.com" title="Vanshidhar Konda <vanshidhar.r.konda@intel.com>"> Vanshidhar Konda</a> <pre>This issue occurs multiple times everyday on SKL machines. No other machines were noted as failing with the kms_cursor_crc@pipe-[abc]-cursor-suspend tests. TGL errors are being tracked by another bug. The ACPI: EC: interrupt blocked line in the logs occurs even during successful runs. This line is indicating that the system is getting ready to enter suspend to RAM (S3) state. The actual error is only that the test is "incomplete". There are 2 kinds of failures captured by this bug/filter. One is that the machine just resumes from S3 and then fails. The other is that the machine even fails to enter S3.</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>