All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org,
	Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: Warning: Broadwell/i915: Unclaimed register detected before reading register 0x130040
Date: Mon, 15 Jun 2015 11:47:46 +0100	[thread overview]
Message-ID: <20150615104746.GV28462@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20150615102510.GT8341@phenom.ffwll.local>

On Mon, Jun 15, 2015 at 12:25:10PM +0200, Daniel Vetter wrote:
> On Mon, May 25, 2015 at 08:04:45PM +0200, Dominik Brodowski wrote:
> > Hey,
> > 
> > this just popped up in the dmesg of my Dell XPS 13 -- the system seems to
> > run well, but still, it asks about being cut and sent, so here it is. It is
> > on 4.1.0-rc4+ (Linus' tree as of May 24th, around 3pm UTC -- don't have the
> > git commit ID anymore).
> 
> Can you please boot with i915.mmio_debug=10 and try to reproduce the
> issue? 

It won't help. To see this WARN implies that hsw_unclaimed_reg_detect()
fired and mmio debugging is enabled, and the WARN then fires before a
subsequent register access. So it implies the unclaimed register is not
being accessed by the display driver -- presuming that we have wrapped
all register access appropriately.

<invalid register access>
hsw_unclaimed_reg_detect -> fires, clears the invalid flag
...
(
	hsw_unclaimed_reg_debug before
	mmio
	hsw_unclaimed_reg_debug  after
) -> nothing x N
...
<invalid register access>
hsw_unclaimed_reg_debug -> fires before, ergo no more useful information

Or else I nerfed the automatic debugging too much.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-15 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 18:04 Warning: Broadwell/i915: Unclaimed register detected before reading register 0x130040 Dominik Brodowski
2015-06-15 10:25 ` Daniel Vetter
2015-06-15 10:47   ` Chris Wilson [this message]
2015-06-15 10:57     ` Daniel Vetter
2015-06-16 18:02 Jochen Betz

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=20150615104746.GV28462@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux@dominikbrodowski.net \
    /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.