<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@kms_plane@pixel-format-pipe-[abc]-planes - dmesg-warn - *ERROR* Overflow of CRC buffer, userspace reads too slow." href="https://bugs.freedesktop.org/show_bug.cgi?id=106885#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@kms_plane@pixel-format-pipe-[abc]-planes - dmesg-warn - *ERROR* Overflow of CRC buffer, userspace reads too slow." href="https://bugs.freedesktop.org/show_bug.cgi?id=106885">bug 106885</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 Mika Kahola from <a href="show_bug.cgi?id=106885#c6">comment #6</a>) > If this error is not seen regularly, maybe we could pump up a bit the size > of a ringbuffer. Now, we have DRM_CRC_ENTRIES_NR defined as 128, so maybe we > could increase it to 256? Are the CRCs per pipe or global? If it is per-pipe, then 128 CRCs @ 60 Hz is more than 2 seconds of not reading the crc... I would think that this ought to be sufficient and if it is not, we really need to look into why we have such latency in the userspace, don't you think? :o</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>