From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900
Date: Sun, 8 Jun 2014 22:30:15 +0100 [thread overview]
Message-ID: <20140608213015.GA30713@sucs.org> (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 ]---
--
Sitsofe | http://sucs.org/~sits/
next reply other threads:[~2014-06-08 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 21:30 Sitsofe Wheeler [this message]
2014-06-10 6:26 ` Daniel Vetter
2014-06-11 5:46 ` Sitsofe Wheeler
2014-06-11 6:03 ` Sitsofe Wheeler
2014-06-11 9:32 ` Daniel Vetter
2014-06-11 14:30 ` Sitsofe Wheeler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140608213015.GA30713@sucs.org \
--to=sitsofe@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome