Re: [Intel-gfx] REGRESSION 3.14 i915 warning & mouse cursor vanishing

[Jani Nikula]

On Tue, 15 Apr 2014, Imre Deak <imre.deak@xxxxxxxxx> 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 <steven@xxxxxxxxxxxxxx> 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?

I'm wondering the same. Perhaps double check your kernel build and
modules are all right and matching?

BR,
Jani.


>
> For HSW the rc6 kernel option shouldn't make a difference.
>
> --Imre  
>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/