All of lore.kernel.org
 help / color / mirror / Atom feed
From: ykzhao <yakui.zhao@intel.com>
To: Andres Freund <andres@anarazel.de>
Cc: David Airlie <airlied@linux.ie>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.sourceforge.net"
	<dri-devel@lists.sourceforge.net>, Adam Jackson <ajax@redhat.com>
Subject: Re: lvds downclocking breaks on G45/thinkpad T500
Date: Sun, 27 Dec 2009 21:10:55 +0800	[thread overview]
Message-ID: <1261919455.4499.31.camel@localhost.localdomain> (raw)
In-Reply-To: <200912261841.55828.andres@anarazel.de>

On Sun, 2009-12-27 at 01:41 +0800, Andres Freund wrote:
> On Saturday 26 December 2009 17:49:29 Andres Freund wrote:
> > On 2.6.33-rc1 I noticed that the display of my T500 with a G45 reacts very
> > slowly (you can see the text appearing) and colors take a time to
> >  "solidify". I.e. making a white terminal black takes some seconds.
> > ...
> > Anything I can do to help analyzing the issue?
> Thats with recent git checkouts of xorg btw, if thats relevant (which I doubt 
> a bit).
> 
> The missing config is attached now as well.

It will be great if you can open a new bug on
bugs.freedesktop.org(Product=xorg, component = driver/intel) and attach
the following info:
    1. add the boot option of "drm.debug=0x06" and attach the output of
dmesg.
    2. attach the output of "xrandr -q --verbose"
    3. attach the vbios.dump, which can be obtained by using the
following command:
        echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
        cat /sys/devices/pci0000:00/0000:00:02.0/rom
    4. attach the output of Xorg.0.log

Thanks.
   Yakui.
> 
> Andres


  reply	other threads:[~2009-12-27 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-26 16:49 lvds downclocking breaks on G45/thinkpad T500 Andres Freund
2009-12-26 17:41 ` Andres Freund
2009-12-27 13:10   ` ykzhao [this message]
2009-12-27 14:18     ` Andres Freund
2009-12-28  1:24       ` ykzhao
2009-12-28 12:56         ` Andres Freund

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=1261919455.4499.31.camel@localhost.localdomain \
    --to=yakui.zhao@intel.com \
    --cc=airlied@linux.ie \
    --cc=ajax@redhat.com \
    --cc=andres@anarazel.de \
    --cc=dri-devel@lists.sourceforge.net \
    --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.