[Bug 103989] [BAT][ELK only] igt@* - dmesg-warn - *ERROR* CPU pipe A FIFO underrun leading to incomplete.

[bugzilla-daemon at freedesktop.org]

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

Matt Roper <matthew.d.roper at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matthew.d.roper at intel.com
           Priority|high                        |medium

--- Comment #13 from Matt Roper <matthew.d.roper at intel.com> ---
All of CI links in this report are dead now, but my understanding is that when
this bug was first reported the pattern was that watermark underruns were seen
and then the machine would hang shortly thereafter, leaving tests incomplete. 
Digging through the more recent CI results for this defect, it looks like the
cibuglog filters may be a bit overzealous now.  There have been some kernel
panics resulting in incomplete runs recently, but as far as I can see, those
panics are caused by the snd_hda driver (a NULL pointer dereference) which
would be more appropriately attached to
https://bugzilla.kernel.org/show_bug.cgi?id=204565 (CI issue #1670).

There are also still very occasional watermark underruns at the very end of
cursor tests when the fb console is restored (last instance seen was ~1 week
ago), but those are non-fatal now and the system continues to run properly
after the underrun is detected.  Watermark underruns by themselves can lead to
brief flickering/corruption, but given how rarely they're showing up now (and
that they're only showing up when the fbcon is restored) it's likely that
they'd be completely unnoticed in general usage.  Dropping the
priority/severity of this ticket down to medium.

-- 
You are receiving this mail because:
You are the assignee for the bug.
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/20190819/a727db3b/attachment.html>