Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

[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 drivers/gpu/drm/i915/intel_display.c:9834 check_crtc_state+0x998/0x9ef()
pipe state doesn't match!
CPU: 0 PID: 1594 Comm: Xorg Not tainted 3.15.0-rc8-00106-ge585b54 #49
Hardware name: ASUSTeK Computer INC. 900/900, BIOS 1006    03/03/2009
 b0485438 b011f61f b057c98a ebb03b04 0000063a b057b5f4 0000266a b02c31ef
 b02c31ef ee42c000 ee488c00 00000000 ee488d74 b011f684 00000009 ebb03aec
 b057c98a ebb03b04 b02c31ef b057b5f4 0000266a b057c98a 00000000 ebb03bdc
Call Trace:
 [<b0485438>] ? dump_stack+0xa/0x13
 [<b011f61f>] ? warn_slowpath_common+0x70/0x85
 [<b02c31ef>] ? check_crtc_state+0x998/0x9ef
 [<b02c31ef>] ? check_crtc_state+0x998/0x9ef
 [<b011f684>] ? warn_slowpath_fmt+0x33/0x37
 [<b02c31ef>] ? check_crtc_state+0x998/0x9ef
 [<b02cdbe6>] ? intel_modeset_check_state+0x353/0x5fb
 [<b02cdefd>] ? intel_set_mode+0x2a/0x32
 [<b02cebfd>] ? intel_crtc_set_config+0x8c9/0x962
 [<b02151e4>] ? idr_alloc+0xb5/0xc3
 [<b0292d68>] ? drm_mode_set_config_internal+0x39/0x9b
 [<b0293325>] ? drm_mode_setcrtc+0x397/0x438
 [<b0292f8e>] ? drm_crtc_check_viewport+0xef/0xef
 [<b028a871>] ? drm_ioctl+0x327/0x38f
 [<b0292f8e>] ? drm_crtc_check_viewport+0xef/0xef
 [<b016f5f5>] ? do_sync_read+0x5a/0x7f
 [<b028a54a>] ? drm_version+0x73/0x73
 [<b017a883>] ? do_vfs_ioctl+0x350/0x419
 [<b0125e02>] ? recalc_sigpending+0xe/0x36
 [<b0126867>] ? __set_task_blocked+0x61/0x67
 [<b0127ad6>] ? __set_current_blocked+0xd/0xf
 [<b0127bf9>] ? sigprocmask+0x77/0x87
 [<b017a97d>] ? SyS_ioctl+0x31/0x54
 [<b04898c9>] ? sysenter_do_call+0x12/0x26
 [<b0480000>] ? klist_release+0x14/0x87
---[ end trace 900fd39ab2e2b03f ]---

-- 
Sitsofe | http://sucs.org/~sits/
--
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/