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 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.
Not in the resend and I didn't seem to receive your original mail somehow at all. Can you please resend.
Downloadable from http://sucs.org/~sits/test/eeepc-900/dmesg-20140611 .
By the way, Mutt seems to be becoming upset when I group reply to your mails. I think it's because your address is in both the To: and the Cc: fields....
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.
Ok, makes sense. Smells a bit like leftover pfit state. Can you please also try latest drm-intel-nightly?
The previous log is from drm-intel-nightly but there seem to be more warnings in it rather than less...