<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][DRMTIP] igt@pm_rpm@* - dmesg-warn - *ERROR* DBus power enable timeout!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108654#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][DRMTIP] igt@pm_rpm@* - dmesg-warn - *ERROR* DBus power enable timeout!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108654">bug 108654</a>
from <span class="vcard"><a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> <span class="fn">Imre Deak</span></a>
</span></b>
<pre>(In reply to Martin Peres from <a href="show_bug.cgi?id=108654#c16">comment #16</a>)
<span class="quote">> (In reply to Imre Deak from <a href="show_bug.cgi?id=108654#c15">comment #15</a>)
> > (In reply to CI Bug Log from <a href="show_bug.cgi?id=108654#c13">comment #13</a>)
> > > A CI Bug Log filter associated to this bug has been updated:
> > >
> > > {- ICL: igt@runner@aborted - fail - Previous test: pm_rpm (fences) -}
> > > {+ ICL: igt@runner@aborted - fail - Previous test: i915_pm_rpm +}
> > >
> > > New failures caught by the filter:
> > >
> > > *
> > > <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5640/shard-iclb1/">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5640/shard-iclb1/</a>
> > > igt@<a href="mailto:runner@aborted.html">runner@aborted.html</a>
>
> Links to igt@runner@aborted are often wrong because if one run got more than
> 1 abort, they will all write to the same file and that leads to seeing only
> one of them.</span >
Okay. In the above case I also looked at the actual dmesg
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5640/shard-iclb1/dmesg23.log">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5640/shard-iclb1/dmesg23.log</a>
which also doesn't have the "DBus power enable.." error message. But I suppose
the error happened then on another ICL shard instance.
<span class="quote">>
> >
> > Hm, the above one gets stuck during kms_frontbuffer_tracking and has the
> > following error:
> >
> > <3>[ 531.484666] [drm:pipe_config_err [i915]] *ERROR* mismatch in
> > pixel_rate (expected 138780, found 92519)
> > <3>[ 531.485032] [drm:pipe_config_err [i915]] *ERROR* mismatch in
> > base.adjusted_mode.crtc_clock (expected 138780, found 92519)
> > <4>[ 531.485111] ------------[ cut here ]------------
> > <4>[ 531.485116] pipe state doesn't match!
> > <4>[ 531.485225] WARNING: CPU: 2 PID: 2088 at
> > drivers/gpu/drm/i915/intel_display.c:12503
> > intel_atomic_commit_tail+0x1224/0x1290 [i915
> >
> > So not sure how it's related to the originally reported bug, which should be
> > about the "DBus power enable timeout" error.
> >
> > So I think this new one here is an unrelated issue and would need to be
> > tracked somewhere else.
> >
> > This ticket (<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][DRMTIP] igt@pm_rpm@* - dmesg-warn - *ERROR* DBus power enable timeout!"
href="show_bug.cgi?id=108654">bug 108654</a>) OTOH was fixed by
> >
> > commit ad3e7b824c185125f281d56a9e8f614effcdae91
> > Author: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>>
> > Date: Wed Jan 30 17:51:10 2019 +0200
> >
> > drm/i915: Don't use the second dbuf slice on icl
> >
> > and so can be closed.
>
> We still hit this issue:
>
> icl-y:
> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5700/fi-icl-y/">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5700/fi-icl-y/</a>
> igt@<a href="mailto:i915_pm_rpm@basic-rte.html">i915_pm_rpm@basic-rte.html</a>
> icl-u3:
> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4862/fi-icl-u3/">https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4862/fi-icl-u3/</a>
> igt@<a href="mailto:i915_pm_rpm@universal-planes.html">i915_pm_rpm@universal-planes.html</a>
> icl-u2:
> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5663/fi-icl-u2/">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5663/fi-icl-u2/</a>
> igt@<a href="mailto:i915_pm_rpm@basic-rte.html">i915_pm_rpm@basic-rte.html</a>
> shard-iclb:
> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5694/shard-iclb1/">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5694/shard-iclb1/</a>
> igt@<a href="mailto:i915_pm_rpm@universal-planes.html">i915_pm_rpm@universal-planes.html</a>
>
> For more info, check the cibuglog data!</span >
Ok, thanks for the above links, I think I know where the problem is, will
follow up with a fix.</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>