Skip to contentSkip to conversation

Mismatch in gmch_pfit.lvds_border_bits on EeePC 900

DISCUSSION Sitsofe Wheeler 3 participants 7 messages Jun 8, 2014 – Jul 19, 2014 3 messages not in the archive

lore
Share & tools
lore
#0 lore raw

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 ]---
Signature · 1 line
Sitsofe | http://sucs.org/~sits/
#1 lore raw
Quoted 4 lines · 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)

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).

Also, do you have any ideas when you reproduce this? Anything that changes the lvds output could be relevant ...
-Daniel

Quoted 38 lines
------------[ 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 ]---
Signature · 1 line
Sitsofe | http://sucs.org/~sits/
Signature · 3 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
#2 lore raw
Quoted 4 lines · Daniel Vetter
Quoted 3 lines · 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:

Quoted 8 lines
Quoted 1 line

[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.

Quoted 2 lines

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.

Signature · 1 line
Sitsofe | http://sucs.org/~sits/
#3 lore raw

(resending because Daniel was dropped from the reply list - I don't know why)

Quoted 27 lines · Sitsofe Wheeler
Quoted 4 lines · Daniel Vetter
Quoted 3 lines · 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:

Quoted 8 lines
Quoted 1 line

[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.

Quoted 2 lines

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.

Signature · 1 line
Sitsofe | http://sucs.org/~sits/
Signature · 1 line
Sitsofe | http://sucs.org/~sits/
#4 lore raw
Quoted 19 lines · Sitsofe Wheeler

(resending because Daniel was dropped from the reply list - I don't know why)

Quoted 15 lines · Sitsofe Wheeler
Quoted 4 lines · Daniel Vetter
Quoted 3 lines · 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:

Quoted 8 lines
Quoted 1 line

[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.

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines

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?

Thanks, Daniel

Signature · 3 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
#5 lore raw
Quoted 17 lines · Daniel Vetter
Quoted 16 lines · Sitsofe Wheeler
Quoted 14 lines · Sitsofe Wheeler
Quoted 12 lines · Daniel Vetter
Quoted 4 lines · 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)

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).

Quoted 4 lines
Quoted 1 line
Quoted 1 line

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....

Quoted 11 lines
Quoted 8 lines
Quoted 8 lines
Quoted 2 lines

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...

Signature · 1 line
Sitsofe | http://sucs.org/~sits/

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): CALjAwxjOLuA4vxG3ZH5ApafogvtENXsmnJRtxRNbWupkCkJ81A@mail.gmail.com

A message that is not in the archive (sent off-list or not yet received): CALjAwxih5eYm02++Ao3og9YqaSDSVnxrXoiqo8aR9rLnK4P9Hw@mail.gmail.com

#9 lore raw

If I'm matching bugs correctly then yeah, we just reverted the offending commit. But only in drm-intel-fixes. Sorry that I dropped the ball on this. And please ping with mailing lists still on cc. -Daniel

Quoted 43 lines · Sitsofe Wheeler

(also resending to daniel.vetter at ffwll.ch)

Quoted 28 lines · Sitsofe Wheeler
Quoted 27 lines · Sitsofe Wheeler
Quoted 25 lines · Sitsofe Wheeler
Quoted 3 lines · Daniel Vetter

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....

Quoted 11 lines
Quoted 8 lines
Quoted 8 lines
Quoted 2 lines

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...

Quoted 7 lines
Quoted 2 lines

Just checking - did you get the previous mail (above) saying where the log was?

Did this one get fixed (I never heard back)? If so I can test a newer kernel...

--
Sitsofe | http://sucs.org/~sits/

--
Sitsofe | http://sucs.org/~sits/

Signature · 3 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch