Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-11 Thread Sitsofe Wheeler
On Wed, Jun 11, 2014 at 11:32:29AM +0200, Daniel Vetter wrote: > On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote: > > > > 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,

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-11 Thread Daniel Vetter
On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote: > (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,

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-11 Thread Sitsofe Wheeler
(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

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-11 Thread Sitsofe Wheeler
(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

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-11 Thread Daniel Vetter
On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote: (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,

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-11 Thread Sitsofe Wheeler
On Wed, Jun 11, 2014 at 11:32:29AM +0200, Daniel Vetter wrote: On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote: 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

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-10 Thread Sitsofe Wheeler
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]

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-10 Thread Daniel Vetter
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)

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-10 Thread Daniel Vetter
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,

Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-10 Thread Sitsofe Wheeler
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 on EeePC 900

2014-06-08 Thread Sitsofe Wheeler
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) [ cut here ] WARNING: CPU: 0 PID: 1594 at

Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

2014-06-08 Thread Sitsofe Wheeler
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) [ cut here ] WARNING: CPU: 0 PID: 1594 at