[Bug 108654] [CI][DRMTIP] igt at pm_rpm@* - dmesg-warn - *ERROR* DBus power enable timeout!

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=108654

--- Comment #17 from Imre Deak <imre.deak at intel.com> ---
(In reply to Martin Peres from comment #16)
> (In reply to Imre Deak from comment #15)
> > (In reply to CI Bug Log from comment #13)
> > > A CI Bug Log filter associated to this bug has been updated:
> > > 
> > > {- ICL: igt at runner@aborted - fail - Previous test: pm_rpm (fences) -}
> > > {+ ICL: igt at runner@aborted - fail - Previous test: i915_pm_rpm +}
> > > 
> > > New failures caught by the filter:
> > > 
> > > *
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5640/shard-iclb1/
> > > igt at runner@aborted.html
> 
> Links to igt at 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.

Okay. In the above case I also looked at the actual dmesg

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5640/shard-iclb1/dmesg23.log

which also doesn't have the "DBus power enable.." error message. But I suppose
the error happened then on another ICL shard instance.

> 
> > 
> > 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 (bug 108654) OTOH was fixed by
> > 
> > commit ad3e7b824c185125f281d56a9e8f614effcdae91
> > Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
> > 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:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5700/fi-icl-y/
> igt at i915_pm_rpm@basic-rte.html
> icl-u3:
> https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4862/fi-icl-u3/
> igt at i915_pm_rpm@universal-planes.html
> icl-u2:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5663/fi-icl-u2/
> igt at i915_pm_rpm@basic-rte.html
> shard-iclb:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5694/shard-iclb1/
> igt at i915_pm_rpm@universal-planes.html
> 
> For more info, check the cibuglog data!

Ok, thanks for the above links, I think I know where the problem is, will
follow up with a fix.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190306/11aafef5/attachment.html>