[Bug 111214] [CI][BAT] igt at i915_module_load@reload - timeout - Unable to sync register 0x2f8100
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Aug 26 13:10:44 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111214
--- Comment #14 from Stanislav Lisovskiy <stanislav.lisovskiy at intel.com> ---
(In reply to Lakshmi from comment #13)
> (In reply to Stanislav Lisovskiy from comment #12)
> > (In reply to Chris Wilson from comment #11)
> > > Module reload still takes over 190s. It is not fixed.
> >
> > I thought that was about audio issue, i.e "snd_hda_intel 0000:00:1f.3:
> > azx_get_response timeout, switching to polling mode: last cmd=0x202f8100
> > <4> [389.635866] snd_hda_intel 0000:00:1f.3: No response from codec,
> > disabling MSI: last cmd=0x202f8100
> > <3> [581.484906] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register
> > 0x2f8100. -11"
> >
> > CI bug log filter doesn't catch that issue anymore -
> > http://gfx-ci.fi.intel.com/cibuglog-ng/issue/1623
> >
> > So we need to either edit filter or create another bug.
> Stan, that's part of Bug 110595.
Despite it is also about module reload, I don't think those have anything in
common except that issue happens also in module_reload. 110595 is about dmesg
warn which we get because Port D was incorrectly marked as non-legacy TypeC
port. Which I believe is not related anyhow to audio codec issue, we are
dealing with here. Also I don't think it affects module_load at reload execution
time, as it is just a dmesg-warn.
I guess we really need to avoid this kind generic bugs to which we associate
all kinds of bugs/issues which happen during this particular test case.
Initially this bug was about azx_response_timeout message we get during
module_load, which is related to audio codec.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190826/622b5a0a/attachment.html>
More information about the intel-gfx-bugs
mailing list