From: Jani Nikula <jani.nikula@linux.intel.com>
To: sedat.dilek@gmail.com, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [v4.6-10530-g28165ec7a99b] i915: *ERROR* "CPU pipe/PCH transcoder" A FIFO underrun
Date: Wed, 25 May 2016 12:42:44 +0300 [thread overview]
Message-ID: <87wpmibhij.fsf@intel.com> (raw)
In-Reply-To: <CA+icZUWp=w7F_Pb7r4m3zTXeJ5Cx4sbsRgMTw6sSU9LHzSSeCg@mail.gmail.com>
On Wed, 25 May 2016, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> Hi Daniel,
>
> with latest Linus Git I see this with my Intel SandyBridge GPU...
>
> [ 17.629014] [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
> *ERROR* CPU pipe A FIFO underrun
> [ 17.630652] [drm:intel_set_pch_fifo_underrun_reporting [i915]]
> *ERROR* uncleared pch fifo underrun on pch transcoder A
> [ 17.630685] [drm:intel_pch_fifo_underrun_irq_handler [i915]]
> *ERROR* PCH transcoder A FIFO underrun
>
> Attached are my linux-config, dmesg-output anx Xorg-log.
>
> Any other informations you need?
For starters, please try the fixes pull I just sent on top [1]. There's
a couple of watermark fixes.
BR,
Jani.
[1] http://mid.gmane.org/87zirebjm7.fsf@intel.com
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-05-25 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 7:31 [v4.6-10530-g28165ec7a99b] i915: *ERROR* "CPU pipe/PCH transcoder" A FIFO underrun Sedat Dilek
2016-05-25 9:42 ` Jani Nikula [this message]
2016-05-26 5:40 ` [Intel-gfx] " Sedat Dilek
2016-05-27 8:19 ` Chris Bainbridge
2016-05-28 7:57 ` Sedat Dilek
2016-05-28 10:04 ` Sedat Dilek
2016-05-30 21:07 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2017-02-02 19:16 Sedat Dilek
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=87wpmibhij.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.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