From mboxrd@z Thu Jan 1 00:00:00 1970 From: Imre Deak Subject: Re: REGRESSION 3.14 i915 warning & mouse cursor vanishing Date: Tue, 15 Apr 2014 22:59:49 +0300 Message-ID: <1397591989.2715.18.camel@ideak-mobl> References: <20140414164010.GA1019@falcon> <867g6ryd2e.fsf@hiro.keithp.com> <20140414185602.GA892@falcon> <20140415194303.GH1023@phenom.ffwll.local> Reply-To: imre.deak@intel.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by gabe.freedesktop.org (Postfix) with ESMTP id DB6566E984 for ; Tue, 15 Apr 2014 13:01:50 -0700 (PDT) In-Reply-To: <20140415194303.GH1023@phenom.ffwll.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Daniel Vetter Cc: David Airlie , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org List-Id: intel-gfx@lists.freedesktop.org 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 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