<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][DRMTIP] igt@kms_cursor_legacy@pipe - cleanup_done timed out"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107122">bug 107122</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Priority</td>
<td>medium
</td>
<td>low
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][DRMTIP] igt@kms_cursor_legacy@pipe - cleanup_done timed out"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107122#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][DRMTIP] igt@kms_cursor_legacy@pipe - cleanup_done timed out"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107122">bug 107122</a>
from <span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span></b>
<pre>The failure rate of this issue is rather low: once every 50.8 runs, across all
the platforms. This was calculated by just looking at the shards results.
It looks like the issue has been fixed, as it has not been seen since
CI_DRM_5670 (238 runs ago). However, the reproduction rate has fluctated a lot
throughout the history of the bug, so it seems very timing-sensitive. We'll
wait until CI_DRM_6178 to verify that this is indeed fixed and not that we just
have been lucky!
The test is spawning $nproc x 2 children: half of them are continuously
updating the cursor while the other half is hogging the CPUs. A set of both
types gets pinned on each available CPU. The test has no asserts and just tries
to see if anything blows up.
Based on the error, it seems like the issue is that the cleanup callback is not
called fast-enough after a flip happens, which may lead to memory leaks. Since
the reproduction rate of this issue is extremely low *even* with such a stress
test, this should not have any significant user impact.
Let's see if we can reduce the occurrence rate of this issue even more, then
close it as NOTABUG because Linux is not an RTOS and we cannot guarantee any
timings.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>