On Tue, Apr 15, 2014 at 12:59 PM, Imre Deak <imre.d...@intel.com> wrote: > 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 <ste...@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.
Correct, it's Haswell. _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
