<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][SHARDS] igt@perf_pmu@busy-idle-no-semaphores-bcs0 - dmesg-warn - WARNING: possible irq lock inversion dependency detected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111626#c26">Comment # 26</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][SHARDS] igt@perf_pmu@busy-idle-no-semaphores-bcs0 - dmesg-warn - WARNING: possible irq lock inversion dependency detected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111626">bug 111626</a>
from <span class="vcard"><a class="email" href="mailto:cibuglog@gmail.com" title="CI Bug Log <cibuglog@gmail.com>"> <span class="fn">CI Bug Log</span></a>
</span></b>
<pre>A CI Bug Log filter associated to this bug has been updated:
{- SKL: igt@gem_persistent_relocs@forked-faulting-reloc-thrashing - dmesg-warn
- WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected -}
{+ SKL ICL: igt@gem_persistent_relocs@forked-faulting-reloc-thrashing -
dmesg-warn - WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected,
acquire at: __mutex_unlock_slowpath, holding by:
intel_gt_retire_requests_timeout +}
New failures caught by the filter:
*
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5265/shard-iclb3/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html">https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5265/shard-iclb3/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html</a>
*
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7280/shard-iclb3/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7280/shard-iclb3/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>