All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: Mismatch in gmch_pfit.lvds_border_bits on EeePC 900
Date: Wed, 11 Jun 2014 06:46:40 +0100	[thread overview]
Message-ID: <20140611054640.GA31892@sucs.org> (raw)
In-Reply-To: <20140610062655.GA5821@phenom.ffwll.local>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

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.

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

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

[-- Attachment #2: kern.log.gz --]
[-- Type: application/octet-stream, Size: 31115 bytes --]

  reply	other threads:[~2014-06-11  5:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-08 21:30 Mismatch in gmch_pfit.lvds_border_bits on EeePC 900 Sitsofe Wheeler
2014-06-10  6:26 ` Daniel Vetter
2014-06-10  6:26   ` Daniel Vetter
2014-06-11  5:46   ` Sitsofe Wheeler [this message]
2014-06-11  6:03     ` Sitsofe Wheeler
2014-06-11  9:32       ` Daniel Vetter
2014-06-11  9:32         ` Daniel Vetter
2014-06-11 14:30         ` Sitsofe Wheeler
     [not found]           ` <20140621033312.GA21715@sucs.org>
     [not found]             ` <CALjAwxjOLuA4vxG3ZH5ApafogvtENXsmnJRtxRNbWupkCkJ81A@mail.gmail.com>
     [not found]               ` <CALjAwxih5eYm02++Ao3og9YqaSDSVnxrXoiqo8aR9rLnK4P9Hw@mail.gmail.com>
2014-07-19  9:44                 ` Daniel Vetter

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=20140611054640.GA31892@sucs.org \
    --to=sitsofe@gmail.com \
    --cc=airlied@linux.ie \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.