[Bug 105870] 4.14.15: drm:intel_pipe_update_end *ERROR* Atomic update failure on pipe B

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed May 30 19:16:04 UTC 2018


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

mmokrejs at fold.natur.cuni.cz <mmokrejs at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED

--- Comment #14 from mmokrejs at fold.natur.cuni.cz <mmokrejs at gmail.com> ---
Hi,
  so with drm-tip as of the most-recent commit

commit fe5bde58dca53de7b615789c69ed83c6420d2d1a (HEAD -> drm-tip,
origin/drm-tip, origin/HEAD)
Author: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
Date:   Fri May 11 18:43:26 2018 +0200

    drm-tip: 2018y-05m-11d-16h-42m-25s UTC integration manifest


for the last 13 days

# uname -a
Linux dell_e5580 4.17.0-rc4+ #1 SMP Sun May 13 02:59:16 CEST 2018 x86_64
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz GenuineIntel GNU/Linux
# w
 21:11:07 up 13 days, 16:09,  1 user,  load average: 0,17, 0,10, 0,03
...

I haven't seen the 

# grep -i underrun /var/log/messages 
Apr  9 19:48:44 dell_e5580 kernel: [drm:intel_cpu_fifo_underrun_irq_handler]
*ERROR* CPU pipe A FIFO underrun
Apr  9 19:48:44 dell_e5580 kernel: [drm:intel_fbc_underrun_work_fn] Disabling
FBC due to FIFO underrun.
#

anymore. Unfortunately, the laptop was just running, I haven't been using it
during that time, but maybe it is really fixed in drm-tip!

I will add some dmesg dumps from the fe5bde58dca53de7b615789c69ed83c6420d2d1a
kernel. I wonder why is the kernel logging so dense if both the internal LCD
and external LCD via HDMI are turned off.

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


More information about the intel-gfx-bugs mailing list