<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@drv_selftest@live_coherency - dmesg-fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103707#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@drv_selftest@live_coherency - dmesg-fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103707">bug 103707</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>That's actually:
<7>[ 4062.736709] BUG: MAX_LOCKDEP_CHAINS too low!
<7>[ 4062.736710] turning off the locking correctness validator.
It's telling us that we've overflowed the static array lockdep uses for
tracking unique lockclasses -- we have too many locks! lockclasses are not
recycled when the module is unload, so every time we run a drv_selftest subtest
we load the module twice (the intention was to run drv_selftest in one batch so
the extra reload only happened once for the entire set). We can drop the
reload, so long as we teach igt to load i915.ko when required:
<a href="https://patchwork.freedesktop.org/series/33703/">https://patchwork.freedesktop.org/series/33703/</a> but this still means that there
is an upper limit to the number of kselftests we run in this manner. Annoying.
I think the ultimate fix here is recycling the lockclasses on module unload.</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 on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>