From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sitsofe Wheeler Subject: Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900 Date: Wed, 11 Jun 2014 07:03:39 +0100 Message-ID: <20140611060339.GA6261@sucs.org> References: <20140608213015.GA30713@sucs.org> <20140610062655.GA5821@phenom.ffwll.local> <20140611054640.GA31892@sucs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20140611054640.GA31892@sucs.org> Sender: linux-kernel-owner@vger.kernel.org To: Daniel Vetter Cc: Jani Nikula , David Airlie , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org List-Id: dri-devel@lists.freedesktop.org (resending because Daniel was dropped from the reply list - I don't know why) On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote: > On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote: > > On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote: > > > With a tree that is close to 3.15 final I'm regularly seeing the > > > following on my EeePC 900 when starting ioquake3: > > > > > > [drm:intel_pipe_config_compare] *ERROR* mismatch in gmch_pfit.lvds_border_bits (expected 32768, found 0) > > > > Hm, I've thought we've fixed that by now. Alas, no :( > > > > Can you please add drm.debug=0xe to your kernel cmdline, reproduce the > > issue and attach the entire dmesg? Please make sure it contains everything > > since boot-up so that we can reconstruct the state properly (might need to > > grab it from logfiles if dmesg is cut off). > > Please find kern.log.gz attached. > > > Also, do you have any ideas when you reproduce this? Anything that changes > > the lvds output could be relevant ... > > Doing > xrandr -s 800x600 > xrandr -s 0 > > was enough to provoke the messages in the attached log. > > -- > Sitsofe | http://sucs.org/~sits/ -- Sitsofe | http://sucs.org/~sits/