From: Imre Deak <imre.deak@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: REGRESSION 3.14 i915 warning & mouse cursor vanishing
Date: Tue, 15 Apr 2014 22:59:49 +0300 [thread overview]
Message-ID: <1397591989.2715.18.camel@ideak-mobl> (raw)
In-Reply-To: <20140415194303.GH1023@phenom.ffwll.local>
On Tue, 2014-04-15 at 21:43 +0200, Daniel Vetter wrote:
> On Mon, Apr 14, 2014 at 11:56:03AM -0700, Steven Noonan wrote:
> > On Mon, Apr 14, 2014 at 11:35:05AM -0700, Keith Packard wrote:
> > > Steven Noonan <steven@uplinklabs.net> writes:
> > >
> > > > Was using my machine normally, then my mouse cursor vanished. After switching
> > > > to a VT and back to X11, my cursor came back. But I did notice a nasty trace in
> > > > dmesg (below).
> > >
> > > I don't think the trace below is related to the cursor disappearing.
> >
> > Any idea what the trace is all about then? Seems it has something to do
> > with runtime power management (maybe my aggressive kernel command-line
> > options are triggering it).
>
> Please test without them. Currently runtime pm should be disabled still on
> vlv (since it's incomplete in 3.14). If you've force-enabled that then you
> get to keep all pieces ;-)
>
> In general don't set any i915 options if you're not a developer or someone
> else who _really_ knows what's going on.
Note that the lspci output and the
[ 1795.275026] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed
register before writing to 70084
line suggests HSW and the specs for ThinkPad Yoga suggests the same. But
I don't know how the vlv_* functions can possible end up in those traces
then, perhaps just a coincidence, random data on stack?
For HSW the rc6 kernel option shouldn't make a difference.
--Imre
next prev parent reply other threads:[~2014-04-15 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 16:40 REGRESSION 3.14 i915 warning & mouse cursor vanishing Steven Noonan
2014-04-14 18:35 ` Keith Packard
2014-04-14 18:56 ` Steven Noonan
2014-04-14 19:42 ` Keith Packard
2014-04-15 19:43 ` Daniel Vetter
2014-04-15 19:59 ` Imre Deak [this message]
2014-04-15 23:34 ` Steven Noonan
2014-04-16 21:46 ` Jani Nikula
2014-04-16 22:03 ` Steven Noonan
2014-06-10 19:35 ` Steven Noonan
2014-06-10 20:40 ` 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=1397591989.2715.18.camel@ideak-mobl \
--to=imre.deak@intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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