mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [WARNING 4.1-rc2] i915: Unclaimed register detected before writing to register 0xc4040
Date: Mon, 11 May 2015 11:22:55 +0200	[thread overview]
Message-ID: <20150511092255.GL15256@phenom.ffwll.local> (raw)
In-Reply-To: <20150508125701.58ac46d0@gandalf.local.home>

On Fri, May 08, 2015 at 12:57:01PM -0400, Steven Rostedt wrote:
> On Fri, 8 May 2015 12:18:10 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> > On Fri, 8 May 2015 12:08:31 -0400
> > Steven Rostedt <rostedt@goodmis.org> wrote:
> > 
> > 
> > > Maybe it's my bios still (it is an older box). I'll just block out
> > > compiling in SND_HDA_INTEL, so that it doesn't break my tests (they
> > > fail on a WARNING).
> > 
> > Hmm, right after I posted this I triggered the Call Trace again with 
> > 
> > # CONFIG_SND_HDA_INTEL is not set
> > 
> > :-/
> > 
> > Now to figure out how to keep this from triggering. I may just keep
> > adding a patch to hide that warning.

Ok, so it's really i915 to blame for this.

> Oh, I forgot to mention, that before the Call Trace, I get theses:
> 
> 
> [  673.093330] [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt
> [  673.103206] [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt
> [  673.139252] [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt
> [  673.151323] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A
> [  673.160745] [drm:intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe A FIFO underrun
> 
> Mean anything?

Display fifo underflow. It doesn happen very rarely when we change the
configuration of cursors/overlays (because our code sucks, getting fixed).
But in general I though we've curbed most of them ...

How easy is this to reproduce? It would be interesting to see what the
driver is doing with drm.debug=0xe, but that's a veritable firehose. You
can change that modparam in /sys/modules/drm/parameters/debug at runtime
and it has immediate effect. But we don't keep a running log around.
 
Other things to check:
- Is the fifo underrun always right next to to unclaimed register issue in
  dmesg?
- i915.mmio_debug=10 or so for hopefully more information around the next
  splat. Has some gfx performance impact though.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

      reply	other threads:[~2015-05-11  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 19:40 Steven Rostedt
2015-05-08  6:55 ` [Intel-gfx] " Daniel Vetter
2015-05-08 16:08   ` Steven Rostedt
2015-05-08 16:18     ` Steven Rostedt
2015-05-08 16:57       ` Steven Rostedt
2015-05-11  9:22         ` Daniel Vetter [this message]

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=20150511092255.GL15256@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®