<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][BAT] igt@pm_rpm@(module-reload|dpm_resources_equal) - dmesg-fail / fail - Failed assertion: c1->count_modes == c2->count_modes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104767#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][BAT] igt@pm_rpm@(module-reload|dpm_resources_equal) - dmesg-fail / fail - Failed assertion: c1->count_modes == c2->count_modes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104767">bug 104767</a>
from <span class="vcard"><a class="email" href="mailto:dhinakaran.pandiyan@intel.com" title="Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>"> <span class="fn">Dhinakaran Pandiyan</span></a>
</span></b>
<pre>(In reply to Martin Peres from <a href="show_bug.cgi?id=104767#c6">comment #6</a>)
<span class="quote">> Also seen on APL:
> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1980/fi-apl-guc/">https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1980/fi-apl-guc/</a>
> igt@<a href="mailto:pm_rpm@module-reload.html">pm_rpm@module-reload.html</a>
>
> Starting subtest: module-reload
> (pm_rpm:3480) CRITICAL: Test assertion failure function
> assert_drm_connectors_equal, file ../tests/pm_rpm.c:512:
> (pm_rpm:3480) CRITICAL: Failed assertion: c1->count_modes == c2->count_modes
> (pm_rpm:3480) CRITICAL: error: 45 != 32
> Subtest module-reload failed.</span >
There is a variation in the number of modes that are getting pruned. The driver
decides the max supported dot clock based on source and sink capabilities;
given that the source side caps. do not change, it most likely is the
drm_dp_downstream_max_clock() from the lspcon device that is changing.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<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>