From: Sedat Dilek <sedat.dilek@gmail.com>
To: Chris Bainbridge <chris.bainbridge@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
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: Mon, 30 May 2016 23:07:01 +0200 [thread overview]
Message-ID: <CA+icZUWm_a=6Lk=aKQ3oH2CXN8VZqh7fKqph00JFJqg_rBOOjg@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUUHWhqBKLzN4J9TZYXXKCDGVXkBhfa0-dkpBaU2pwB7qg@mail.gmail.com>
On 5/28/16, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On 5/27/16, Chris Bainbridge <chris.bainbridge@gmail.com> wrote:
>> On 25 May 2016 at 08:31, 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
>>
>> Guessing this is https://bugs.freedesktop.org/show_bug.cgi?id=95736
>>
>
> I did some last testing (for this weekend) with drm-intel-nightly
> (2016y-05m-27d-12h-32m-45s UTC) on top of Linux v4.6 final.
>
> This did not help as I see the same *ERROR* outputs.
>
With drm-intel-nightly (2016y-05m-30d-17h-51m-33s-UTC) the outputs
look a bit different and more helpful?
[ 19.139790] [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
*ERROR* CPU pipe A FIFO underrun
[ 19.140274] [drm:intel_set_pch_fifo_underrun_reporting [i915]]
*ERROR* uncleared pch fifo underrun on pch transcoder A
[ 19.140299] [drm:intel_pch_fifo_underrun_irq_handler [i915]]
*ERROR* PCH transcoder A FIFO underrun
- Sedat -
WARNING: multiple messages have this Message-ID (diff)
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Chris Bainbridge <chris.bainbridge@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v4.6-10530-g28165ec7a99b] i915: *ERROR* "CPU pipe/PCH transcoder" A FIFO underrun
Date: Mon, 30 May 2016 23:07:01 +0200 [thread overview]
Message-ID: <CA+icZUWm_a=6Lk=aKQ3oH2CXN8VZqh7fKqph00JFJqg_rBOOjg@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUUHWhqBKLzN4J9TZYXXKCDGVXkBhfa0-dkpBaU2pwB7qg@mail.gmail.com>
On 5/28/16, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On 5/27/16, Chris Bainbridge <chris.bainbridge@gmail.com> wrote:
>> On 25 May 2016 at 08:31, 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
>>
>> Guessing this is https://bugs.freedesktop.org/show_bug.cgi?id=95736
>>
>
> I did some last testing (for this weekend) with drm-intel-nightly
> (2016y-05m-27d-12h-32m-45s UTC) on top of Linux v4.6 final.
>
> This did not help as I see the same *ERROR* outputs.
>
With drm-intel-nightly (2016y-05m-30d-17h-51m-33s-UTC) the outputs
look a bit different and more helpful?
[ 19.139790] [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
*ERROR* CPU pipe A FIFO underrun
[ 19.140274] [drm:intel_set_pch_fifo_underrun_reporting [i915]]
*ERROR* uncleared pch fifo underrun on pch transcoder A
[ 19.140299] [drm:intel_pch_fifo_underrun_irq_handler [i915]]
*ERROR* PCH transcoder A FIFO underrun
- Sedat -
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-30 21:07 UTC|newest]
Thread overview: 14+ 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 ` [Intel-gfx] " Jani Nikula
2016-05-25 9:42 ` Jani Nikula
2016-05-26 5:40 ` [Intel-gfx] " Sedat Dilek
2016-05-26 5:40 ` Sedat Dilek
2016-05-27 8:19 ` [Intel-gfx] " Chris Bainbridge
2016-05-27 8:19 ` Chris Bainbridge
2016-05-28 7:57 ` [Intel-gfx] " Sedat Dilek
2016-05-28 7:57 ` Sedat Dilek
2016-05-28 10:04 ` [Intel-gfx] " Sedat Dilek
2016-05-28 10:04 ` Sedat Dilek
2016-05-30 21:07 ` Sedat Dilek [this message]
2016-05-30 21:07 ` Sedat Dilek
2017-02-02 19:16 [Intel-gfx] " 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='CA+icZUWm_a=6Lk=aKQ3oH2CXN8VZqh7fKqph00JFJqg_rBOOjg@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=chris.bainbridge@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.