All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jan Niehusmann <jan@gondor.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 16:58:59 +0530	[thread overview]
Message-ID: <20150513112859.GA8887@sudip-PC> (raw)
In-Reply-To: <20150513111010.GA7009@jannic.reliablesolutions.de>

On Wed, May 13, 2015 at 01:10:11PM +0200, Jan Niehusmann wrote:
> On Wed, May 13, 2015 at 04:02:25PM +0530, Sudip Mukherjee wrote:
> > > 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
> > hi,
> > I also have the similar entries in my dmesg, though my problem is a
> > little different from yours and my bisect lead to another commit.
> > And that also is still not fixed (last tested with 4.0).
> 
> (Please note that I didn't do a bisect - that was Thomas. I only noted
> that I can confirm his observations and that his patch helps to prevent
> or hide the issue.)
> 
> Perhaps these are two completely unrelated issues?
yes, maybe unrelated issue. since I am also having similar errors in
dmesg and also having a similar type of problem so replied here.

regards
sudip
> 
> Jan
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jan Niehusmann <jan@gondor.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Thomas Gummerer <t.gummerer@gmail.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
	Michael Leuchtenburg <michael@slashhome.org>,
	Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [BUG/REGRESSION] Screen flickering
Date: Wed, 13 May 2015 16:58:59 +0530	[thread overview]
Message-ID: <20150513112859.GA8887@sudip-PC> (raw)
In-Reply-To: <20150513111010.GA7009@jannic.reliablesolutions.de>

On Wed, May 13, 2015 at 01:10:11PM +0200, Jan Niehusmann wrote:
> On Wed, May 13, 2015 at 04:02:25PM +0530, Sudip Mukherjee wrote:
> > > 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
> > hi,
> > I also have the similar entries in my dmesg, though my problem is a
> > little different from yours and my bisect lead to another commit.
> > And that also is still not fixed (last tested with 4.0).
> 
> (Please note that I didn't do a bisect - that was Thomas. I only noted
> that I can confirm his observations and that his patch helps to prevent
> or hide the issue.)
> 
> Perhaps these are two completely unrelated issues?
yes, maybe unrelated issue. since I am also having similar errors in
dmesg and also having a similar type of problem so replied here.

regards
sudip
> 
> Jan
> 

  reply	other threads:[~2015-05-13 11:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 19:54 [BUG/REGRESSION] Screen flickering Thomas Gummerer
2015-05-12 19:54 ` Thomas Gummerer
2015-05-13  9:14 ` Jani Nikula
2015-05-13  9:14   ` Jani Nikula
2015-05-13  9:53   ` Jan Niehusmann
2015-05-13  9:53     ` Jan Niehusmann
2015-05-13 10:32     ` Sudip Mukherjee
2015-05-13 10:32       ` Sudip Mukherjee
2015-05-13 11:10       ` Jan Niehusmann
2015-05-13 11:10         ` Jan Niehusmann
2015-05-13 11:28         ` Sudip Mukherjee [this message]
2015-05-13 11:28           ` Sudip Mukherjee
2015-05-13 11:27       ` Thomas Gummerer
2015-05-13 11:27         ` Thomas Gummerer
2015-05-13 11:34         ` Sudip Mukherjee
2015-05-13 11:23     ` Thomas Gummerer
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  7:16     ` Thomas Gummerer
2015-05-14 14:28     ` Matt Roper
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=20150513112859.GA8887@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jan@gondor.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 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.