From: William Dauchy <wdauchy@gmail.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [lkp] [drm/i915] 396e33ae20: [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B
Date: Thu, 17 Mar 2016 11:49:28 +0100 [thread overview]
Message-ID: <CAJ75kXZyC4PkX+4Y4H4vfPbuj=oj9NHLA_RC9aMB_p6ak0DRuQ@mail.gmail.com> (raw)
In-Reply-To: <87vb70ew4v.fsf@yhuang-dev.intel.com>
On Mon, Jan 11, 2016 at 2:35 AM, kernel test robot
<ying.huang@linux.intel.com> wrote:
> FYI, we noticed the below changes on
>
> git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
> commit 396e33ae204f52abebec9e578f44c749305500f4 ("drm/i915: Add two-stage ILK-style watermark programming (v10)")
>
>
> +--------------------------------------------------+------------+------------+
> | | 2dfb0b816d | 396e33ae20 |
> +--------------------------------------------------+------------+------------+
> | boot_successes | 8 | 19 |
> | boot_failures | 0 | 4 |
> | drm:intel_set_cpu_fifo_underrun_reporting[i915]] | 0 | 4 |
> | drm:intel_cpu_fifo_underrun_irq_handler[i915]] | 0 | 4 |
> | drm:intel_set_pch_fifo_underrun_reporting[i915]] | 0 | 4 |
> | drm:intel_pch_fifo_underrun_irq_handler[i915]] | 0 | 4 |
> +--------------------------------------------------+------------+------------+
>
>
>
> [ 36.077826] NFS: Registering the id_resolver key type
> [ 36.078178] Key type id_resolver registered
> [ 36.078444] Key type id_legacy registered
> [ 60.884026] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B
> [ 60.884659] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
> [ 60.885221] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder B
> [ 60.885887] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun
> [ 61.180651] random: nonblocking pool is initialized
> [ 81.430503] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe C
> [ 81.431193] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe C FIFO underrun
> [ 81.431782] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder C
> [ 81.432474] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder C FIFO underrun
>
>
> To reproduce:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> cd lkp-tests
> bin/lkp install job.yaml # job file is attached in this email
> bin/lkp run job.yaml
I am still triggering these errors on v4.4.6
Does anybody knows if there is a fix in queue? What can I do to help
debug this issue?
Thanks,
--
William
next prev parent reply other threads:[~2016-03-17 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 1:35 [lkp] [drm/i915] 396e33ae20: [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B kernel test robot
2016-03-17 10:49 ` William Dauchy [this message]
2016-03-17 11:27 ` Maarten Lankhorst
2016-03-17 14:29 ` William Dauchy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ75kXZyC4PkX+4Y4H4vfPbuj=oj9NHLA_RC9aMB_p6ak0DRuQ@mail.gmail.com' \
--to=wdauchy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.d.roper@intel.com \
--cc=ying.huang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).