From: Daniel Vetter <daniel@ffwll.ch>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: 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 11:32:29 +0200 [thread overview]
Message-ID: <20140611093229.GD5821@phenom.ffwll.local> (raw)
In-Reply-To: <20140611060339.GA6261@sucs.org>
On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote:
> (resending because Daniel was dropped from the reply list - I don't know
> why)
>
> On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
> > 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.
Not in the resend and I didn't seem to receive your original mail somehow
at all. Can you please resend.
> > > 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
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
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 11:32:29 +0200 [thread overview]
Message-ID: <20140611093229.GD5821@phenom.ffwll.local> (raw)
In-Reply-To: <20140611060339.GA6261@sucs.org>
On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote:
> (resending because Daniel was dropped from the reply list - I don't know
> why)
>
> On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
> > 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.
Not in the resend and I didn't seem to receive your original mail somehow
at all. Can you please resend.
> > > 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
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-06-11 9:32 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
2014-06-11 6:03 ` Sitsofe Wheeler
2014-06-11 9:32 ` Daniel Vetter [this message]
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=20140611093229.GD5821@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@gmail.com \
/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.