<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@*crc tests* - warn / dmesg-warn - Suspicious CRC: it looks like the CRC read back was from a register in a powered down well" href="https://bugs.freedesktop.org/show_bug.cgi?id=108336#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@*crc tests* - warn / dmesg-warn - Suspicious CRC: it looks like the CRC read back was from a register in a powered down well" href="https://bugs.freedesktop.org/show_bug.cgi?id=108336">bug 108336</a> from <a class="email" href="mailto:stanislav.lisovskiy@intel.com" title="Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>"> Stanislav Lisovskiy</a> <pre>Current conclusion about the root cause is that some test cases like kms_atomic_transition cause this when they apply extreme plane width and height, drm_atomic_check_only fails then in calc_watermarks function, however there are seem to be some not canceled side effects after that, which lead to the issue. Then all subsequent tests fail with that "suspicious crc" issue. I have suspicion that calc_watermarks which is called after some changes were already applied in the end of intel_atomic_check, which leaves the system in some weird state. So the patch was to simply try calling it earlier. Unfortunately it helps only partly, for some reason now at least every first time I run this test case, everything seems to be OK, however next time we still get this "suspicious crc". So I will continue looking to figure out the correct change.</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>