<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#c12">Comment # 12</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 Dhinakaran Pandiyan from <a href="show_bug.cgi?id=104767#c9">comment #9</a>)
<span class="quote">> (In reply to Martin Peres from <a href="show_bug.cgi?id=104767#c5">comment #5</a>)
> > <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4780/fi-glk-j4005/">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4780/fi-glk-j4005/</a>
> > igt@<a href="mailto:pm_rpm@module-reload.html">pm_rpm@module-reload.html</a>
> >
> > (pm_rpm:3993) CRITICAL: Test assertion failure function
> > assert_drm_connectors_equal, file ../tests/pm_rpm.c:507:
> > (pm_rpm:3993) CRITICAL: Failed assertion: c1->count_modes == c2->count_modes
> > (pm_rpm:3993) CRITICAL: error: 40 != 43
> > Subtest module-reload failed.
>
> These failures are different from those on fi-apl-guc, we should split this
> bug.
> * fi-apl-guc has lspcon link training failures and should possibly be merged
> with <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][BAT] igt@* - dmesg-warn - [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -5, then *ERROR* Failed to probe lspcon"
href="show_bug.cgi?id=108529">https://bugs.freedesktop.org/show_bug.cgi?id=108529</a>
>
> * fi-glk-j4005 has edid read errors.</span >
The problematic display was already changed on this machine; let's open a new
bug if this machine has any new issues.
To summarize, the only remaining problem is the lspcon link training failures
on fi-apl-guc.
Martin,
How can I get the last failure of this signature on fi-apl-guc? Also, can you
make cibuglog track only failures on this machine for this bug?</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>
</ul>
</body>
</html>