All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Eriksson <aeriksson@fastmail.fm>
To: Alex Deucher <alexdeucher@gmail.com>,
	airlied@redhat.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, xorg-driver-ati@lists.x.org
Subject: Re: Radeon jittery post 2.6.35
Date: Sun, 24 Apr 2011 11:24:05 +0200	[thread overview]
Message-ID: <4DB3EC35.7000601@fastmail.fm> (raw)
In-Reply-To: <4D831E18.9020904@fastmail.fm>

 On 03/18/11 09:55, Anders Eriksson wrote:
>  On 03/16/11 21:09, Anders Eriksson wrote:
> >  On 03/15/11 22:46, Alex Deucher wrote:
> > >  Try booting with radeon.audio=0 on 2.6.38rc, some TVs have problems
> > > with the hdmi packets we send by default.  disabling audio will treat
> > > the hdmi like dvi.
> > >
> > > Alex
> > You seem to be on to something there. radeon.audio=0 removes
> > what appears to be all of the jitter. I say "appear", because during
> > my many test runs today, I've come across moments where my brain
> > goes "wasn't what I just noticed on the TV something abnormal?" Both
> > in fb mode (post KMS), and in X11. It's definetly improved from useless
> > for family use, to perfectly ok though.
> >
> I was too early on this one. Yesterday (.38) , and today (38-rc8),
> are both jittery in post-KMS fb mode and in X, even though I use
> radeon.audio=0.
>
> A power cycling of the TV stabilizes it though.
>
> I'd be more than happy to test out any patches or ideas you might have.
>
> -A

It turns out all the failure patterns I've thought I've seen so far up
through .38.x are moot.

However, now on .39-rc, the KMS'd console is stable, and starting X
makes it bad again.

It there anything useful I can pull from any logs on the startup of X?
Either from the X
server, or the kernel. Last time I looked at the drm log from the kernel
It was unreadable
to a mere mortal, but I hope you guys can point me to what debug knobs
to enable to get a good
view of the interesting parts (How does one start a minimal X, btw?
"xinit" gives me an
undecorated xterm with the jitter. Can one start something more minimal?)

Currently running today's git xorg-server and xf86-video-dri.

-Anders
 


  reply	other threads:[~2011-04-24  9:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-13 14:08 Radeon jittery post 2.6.35 Anders Eriksson
2011-03-13 17:15 ` Arthur Titeica
2011-03-13 17:15   ` Arthur Titeica
2011-03-14 20:35   ` Anders Eriksson
2011-03-14 20:35     ` Anders Eriksson
2011-03-14 22:20 ` Alex Deucher
2011-03-14 22:20   ` Alex Deucher
2011-03-14 22:22   ` Alex Deucher
2011-03-14 22:22     ` Alex Deucher
2011-03-15  8:35     ` Anders Eriksson
2011-03-15 20:58     ` Anders Eriksson
2011-03-15 20:58       ` Anders Eriksson
2011-03-15 21:08       ` Jerome Glisse
2011-03-15 21:08         ` Jerome Glisse
2011-03-16 21:40         ` Anders Eriksson
2011-03-15 21:46       ` Alex Deucher
2011-03-16 20:09         ` Anders Eriksson
2011-03-18  8:55           ` Anders Eriksson
2011-04-24  9:24             ` Anders Eriksson [this message]
2011-04-25 14:53               ` Jerome Glisse
2011-04-27 12:16                 ` Anders Eriksson
2011-03-15  8:18   ` Anders Eriksson
2011-03-15  8:18     ` Anders Eriksson

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=4DB3EC35.7000601@fastmail.fm \
    --to=aeriksson@fastmail.fm \
    --cc=airlied@redhat.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xorg-driver-ati@lists.x.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.