From: Daniel Vetter <daniel@ffwll.ch>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org >> dri-devel"
<dri-devel@lists.freedesktop.org>
Subject: Re: [drm:hsw_unclaimed_reg_detect] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.
Date: Mon, 15 Dec 2014 11:16:54 +0100 [thread overview]
Message-ID: <20141215101654.GU27182@phenom.ffwll.local> (raw)
In-Reply-To: <548EA8E5.1000508@gmx.de>
On Mon, Dec 15, 2014 at 10:24:53AM +0100, Toralf Förster wrote:
> On 12/15/2014 08:45 AM, Daniel Vetter wrote:
> > Nah, this is just a kernel cmdlineoption. So please boot with
> > i915.mmio_debug=1 added to the kernel cmdline, reproduce and then grab the
> > entire dmesg.
> >
> > Thanks, Daniel
>
> errm, I did it, rebooted, suspended and then the WARNING appeared:
>
> >Dec 12 13:22:13 t44 kernel: ------------[ cut here ]------------
> >Dec 12 13:22:13 t44 kernel: WARNING: CPU: 3 PID: 2750 at drivers/gpu/drm/i915/intel_uncore.c:528 hsw_unclaimed_reg_debug.isra.11+0x8d/0xa0 [i915]()
Annoying, the unclaimed register write seems to happen before we do
anything really. Can you please test what happens when you disable all
sound modules?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-12-15 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <548AE03A.6090608@gmx.de>
2014-12-15 7:45 ` [drm:hsw_unclaimed_reg_detect] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem Daniel Vetter
2014-12-15 9:24 ` Toralf Förster
2014-12-15 10:16 ` Daniel Vetter [this message]
2014-12-15 15:56 ` Toralf Förster
2014-12-15 16:29 ` Imre Deak
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=20141215101654.GU27182@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=toralf.foerster@gmx.de \
/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