Description of the problem: Running ioquake results in an mismatch in gmch_pfit.lvds_border_bits error on my EeePC 900. Steps to reproduce: 1. Run ioquake binary. 2. Quit ioquake. 3. Check dmesg. Expected result: No error messages. Actual results: Error message like: [ 234.206074] [drm:check_crtc_state] *ERROR* mismatch in gmch_pfit.lvds_border_bits (expected 32768, found 0) [ 234.206085] ------------[ cut here ]------------ [ 234.206093] WARNING: CPU: 0 PID: 1725 at drivers/gpu/drm/i915/intel_display.c:10872 check_crtc_state+0x81b/0x1060() [ 234.206097] pipe state doesn't match! [ 234.206105] CPU: 0 PID: 1725 Comm: Xorg Not tainted 3.19.0-00001-gfb8cfc5 #28 [ 234.206109] Hardware name: ASUSTeK Computer INC. 900/900, BIOS 1006 03/03/2009 [ 234.206113] b0654371 b012d323 b0785afa e9c63a74 000006bd b0760dcc 00002a78 b03b9fcb [ 234.206125] b03b9fcb ee500028 ee50031c ee533190 ee500000 b012d3b3 00000009 e9c63a5c [ 234.206133] b0785afa e9c63a74 b03b9fcb b0760dcc 00002a78 b0785afa ffffffff 00000000 [ 234.206143] Call Trace: [ 234.206155] [<b0654371>] ? dump_stack+0xa/0x13 [ 234.206165] [<b012d323>] ? warn_slowpath_common+0x83/0xc0 [ 234.206171] [<b03b9fcb>] ? check_crtc_state+0x81b/0x1060 [ 234.206177] [<b03b9fcb>] ? check_crtc_state+0x81b/0x1060 [ 234.206184] [<b012d3b3>] ? warn_slowpath_fmt+0x33/0x40 [ 234.206190] [<b03b9fcb>] ? check_crtc_state+0x81b/0x1060 [ 234.206200] [<b03c7ce4>] ? intel_modeset_check_state+0x274/0x9a0 [ 234.206206] [<b03c1a2c>] ? i9xx_crtc_disable+0x15c/0x430 [ 234.206213] [<b03ccaae>] ? i9xx_check_fifo_underruns+0x5e/0xc0 [ 234.206220] [<b03c29c6>] ? __intel_set_mode+0x176/0xab0 [ 234.206227] [<b03c9441>] ? intel_crtc_set_config+0x981/0xd70 [ 234.206235] [<b035d616>] ? drm_mode_set_config_internal+0x46/0xb0 [ 234.206242] [<b035d9d2>] ? drm_mode_setcrtc+0xc2/0x540 [ 234.206248] [<b035d910>] ? drm_crtc_check_viewport+0x160/0x160 [ 234.206255] [<b03535cd>] ? drm_ioctl+0x19d/0x5c0 [ 234.206262] [<b035d910>] ? drm_crtc_check_viewport+0x160/0x160 [ 234.206271] [<b01e44c7>] ? fsnotify+0x2b7/0x3b0 [ 234.206277] [<b0353430>] ? drm_version+0x80/0x80 [ 234.206285] [<b01c1044>] ? do_vfs_ioctl+0x354/0x540 [ 234.206291] [<b01b1c25>] ? vfs_write+0x135/0x1b0 [ 234.206297] [<b01c1273>] ? SyS_ioctl+0x43/0x80 [ 234.206305] [<b0658f3d>] ? sysenter_do_call+0x12/0x12 [ 234.206310] ---[ end trace 67cef6fff90a8197 ]--- [ 234.230438] [drm:check_crtc_state] *ERROR* mismatch in gmch_pfit.lvds_border_bits (expected 32768, found 0) [ 234.230448] ------------[ cut here ]------------ How reproducible is the problem? It is reproducible every time. Additional information: Spun off from Bug #89108 (See https://bugs.freedesktop.org/attachment.cgi?id=113465 for dmesg). Version information: Ubuntu 14.04 EeePC 900 xorg 1:7.7+1ubuntu8 xserver-xorg 1:7.7+1ubuntu8 xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 Linux kernel 3.19
Does this happen on older kernels too? If not, would it be possible to bisect?
Could you add drm.debug=0xe to your kernel command line, reproduce the bug and attach the dmesg again?
(In reply to Ander Conselvan de Oliveira from comment #2) > Could you add drm.debug=0xe to your kernel command line, reproduce the bug > and attach the dmesg again? Never mind, looks like we already have that in bug 87632. *** This bug has been marked as a duplicate of bug 87632 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.