From: jon <jmoroney@hawaii.edu>
To: Jani Nikula <jani.nikula@linux.intel.com>,
daniel.vetter@intel.com, Intel-gfx@lists.freedesktop.org
Subject: Re: PCH fifo underrun in 3.18
Date: Wed, 11 Feb 2015 10:19:20 -1000 [thread overview]
Message-ID: <54DBB948.6030000@hawaii.edu> (raw)
In-Reply-To: <87fvafwii6.fsf@intel.com>
Under what product should I submit the bug? dmr.debug=14 doesn't show much.
[jon@localhost]~% dmesg | grep drm
[ 1.936241] [drm] Initialized drm 1.1.0 20060810
[ 2.193043] [drm] Memory usable by graphics device = 2048M
[ 2.193046] [drm] Replacing VGA console driver
[ 2.199998] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.200000] [drm] Driver supports precise vblank timestamp query.
[ 2.287949] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to
bit banging on pin 5
[ 2.297614] fbcon: inteldrmfb (fb0) is primary device
[ 2.576664] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[ 2.576666] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
Jon
On 02/08/2015 11:18 PM, Jani Nikula wrote:
> On Fri, 30 Jan 2015, jon <jmoroney@hawaii.edu> wrote:
>> Just updated my thinkpad (x230, ivy bridge platform) to 3.18 and boot
>> fails with the error 'PCH fifo underrun'. This is under fedora 21 with
>> the fedora kernel version 3.18.3-201
> Please file a bug on [1], attach a dmesg from boot to the problem with
> drm.debug=14 module parameter set. Reference this thread.
>
> Thanks,
> Jani.
>
> [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
>
--
Jon
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-02-11 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 23:21 PCH fifo underrun in 3.18 jon
2015-02-07 1:11 ` Fwd: " jon
2015-02-08 1:27 ` Fwd: " jon
2015-02-09 9:18 ` Jani Nikula
2015-02-11 20:19 ` jon [this message]
2015-02-12 6:26 ` Jani Nikula
2015-02-12 6:27 ` Jani Nikula
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=54DBB948.6030000@hawaii.edu \
--to=jmoroney@hawaii.edu \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel.vetter@intel.com \
--cc=jani.nikula@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