[Bug 109099] New: pipe error 0x00000080 not handled

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 109099
           Summary: pipe error 0x00000080 not handled
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: olaf at aepfle.de
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 142851
  --> https://bugs.freedesktop.org/attachment.cgi?id=142851&action=edit
dmesg-4.12.14-lp150.12.28-default.txt

Dell Latitude E7470, "Skylake GT2 [HD Graphics 520]".

With kernels later than linux-4.4 (have not checked when it started), dmesg is
flooded with messages like this:

[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x00000080

# dmesg | grep -cw 0x00000080
67621


This happens when the system is booted as Xen dom0. IMO everything is working
fine, no issues to report beside the flooding of syslog. The used desktop
environment makes no difference, nor makes the used version of SLE or Leap or
Tumbleweed any difference.



The actual things I want to see fixed are:

What is bit (1 << 3)? There is no constant defined for this issue.

Why do DRM_ERROR() and related helpers not use printk_ratelimited()?
The use can not do anything about the issue anyway, other than reporting it, so
a single message would be fine.

And if you feel like it: what needs to be done to get this driver fixed for a
Xen dom0?

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