intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [regression] drm/i915: cleanup per-pipe reg usage
Date: Thu, 17 Feb 2011 21:54:23 +0100	[thread overview]
Message-ID: <1297976063.2608.0.camel@mini> (raw)
In-Reply-To: <20110217103259.4dd6caf6@jbarnes-desktop>

Am Donnerstag, den 17.02.2011, 10:32 -0800 schrieb Jesse Barnes:
> On Thu, 17 Feb 2011 08:26:20 +0100
> Alexey Fisher <bug-track@fisher-privat.net> wrote:
> 
> > Am Mittwoch, den 16.02.2011, 10:57 -0800 schrieb Jesse Barnes:
> > > On Sat, 12 Feb 2011 22:02:36 +0100
> > > Alexey Fisher <bug-track@fisher-privat.net> wrote:
> > > 
> > > > In attachment are reg_dumps.
> > > > 
> > > > intel_1 - is gdm login screen, every thing is ok
> > > > intel_2 - is after login, noise
> > > > intel_3 - is after mouse pointer was placed to the upper left corner,
> > > > image is ok again.
> > > > 
> > > > Am Samstag, den 12.02.2011, 18:09 +0000 schrieb Chris Wilson:
> > > > > 
> > > > > On Sat, 12 Feb 2011 15:16:16 +0100, Alexey Fisher
> > > > > <bug-track@fisher-privat.net> wrote:
> > > > > > Video is in attachment.
> > > > > > 
> > > > > > If mouse pointer is on the left top corner i get still image .. if
> > > > > not -
> > > > > > noise.
> > > > > 
> > > > > I think intel_reg_dumper before/after will be the best guide as to
> > > > > where
> > > > > the mistake crept in.
> > > > > -Chris
> > > 
> > > Also, seeing the kernel messages from a clean boot after setting
> > > drm.debug=4 would help; they'll tell us what FIFO watermarks we used
> > > and might help me track down the flicker.
> > 
> > the bad files are from version 2.6.38-rc2-00090-g9db4a9c
> > the good are 2.6.38-rc2-00079-g4a1dc3f
> 
> Hm watermarks actually look good, but the cursor b control reg is
> different for some reason.
> 
> Oops, I see a problem.  Does this patch help?

Yes, it is working!

Thank you.

  reply	other threads:[~2011-02-17 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 20:59 [regression] drm/i915: cleanup per-pipe reg usage Alexey Fisher
     [not found] ` <1297520176.10989.1.camel@zwerg>
     [not found]   ` <b9dded$hu5fo8@orsmga002.jf.intel.com>
2011-02-12 21:02     ` Alexey Fisher
2011-02-16 18:42       ` Jesse Barnes
2011-02-16 18:57       ` Jesse Barnes
2011-02-17  7:26         ` Alexey Fisher
2011-02-17 18:32           ` Jesse Barnes
2011-02-17 20:54             ` Alexey Fisher [this message]
2011-02-17 21:09               ` Jesse Barnes
2011-02-17 21:24                 ` Alexey Fisher
2011-02-17 21:26                   ` Alexey Fisher

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=1297976063.2608.0.camel@mini \
    --to=bug-track@fisher-privat.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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;
as well as URLs for NNTP newsgroup(s).