From: Jan Niehusmann <jan@gondor.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Thomas Gummerer <t.gummerer@gmail.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [BUG/REGRESSION] Screen flickering
Date: Wed, 13 May 2015 11:53:19 +0200 [thread overview]
Message-ID: <20150513095319.GA4249@jannic.reliablesolutions.de> (raw)
In-Reply-To: <87iobw3klc.fsf@intel.com>
Hi,
On Wed, May 13, 2015 at 12:14:39PM +0300, Jani Nikula wrote:
> Is this the same as https://bugzilla.kernel.org/show_bug.cgi?id=98141 ?
The visible effect in the video is similar to what I see on the LVDS
display. I also see some influence of the mouse pointer position on the
blanked areas.
The effect on the external screen is more like single scan
lines jumping to the right and back, at a high (but still visible)
frequency.
What I'm missing in the report, are some log entries I'm seeing on my
notebook:
Apr 30 08:50:23 localhost kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
Apr 30 08:50:23 localhost kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun
Apr 30 08:50:29 localhost kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Apr 30 08:50:29 localhost kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
Jan
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-13 9:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 19:54 [BUG/REGRESSION] Screen flickering Thomas Gummerer
2015-05-13 9:14 ` Jani Nikula
2015-05-13 9:53 ` Jan Niehusmann [this message]
2015-05-13 10:32 ` Sudip Mukherjee
2015-05-13 11:10 ` Jan Niehusmann
2015-05-13 11:28 ` Sudip Mukherjee
2015-05-13 11:27 ` Thomas Gummerer
2015-05-13 11:34 ` Sudip Mukherjee
2015-05-13 11:23 ` Thomas Gummerer
2015-05-14 3:21 ` Matt Roper
2015-05-14 7:16 ` [PATCH v2] drm/i915: fix screen flickering Thomas Gummerer
2015-05-14 14:28 ` Matt Roper
2015-05-19 7:37 ` 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=20150513095319.GA4249@jannic.reliablesolutions.de \
--to=jan@gondor.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=t.gummerer@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