From: Anders Eriksson <aeriksson@fastmail.fm>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: 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: Tue, 15 Mar 2011 21:58:35 +0100 [thread overview]
Message-ID: <4D7FD2FB.9090505@fastmail.fm> (raw)
In-Reply-To: <AANLkTik0nXX+WEwa2xZ9VV+yHwrWnx+tYNdZXPEjk=SO@mail.gmail.com>
On 03/14/11 23:22, Alex Deucher wrote:
> On Mon, Mar 14, 2011 at 6:20 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
> > On Sun, Mar 13, 2011 at 10:08 AM, Anders Eriksson <aeriksson@fastmail.fm> wrote:
> >> Hi,
> >>
> >> I've found what I guess is a radeon (or drm/kms) regression post 2.6.35.
> >> I've got my TV conneced to my RS690G over HDMI, and the display has
> >> always been jittery after POST and at the GRUB screen. Pre-KMS, the X
> >> server (or driver got it sorted), and when KMS started, the display
> >> stabilized right after the kernel driver was initiated. However, post
> >> 2.6.35, I see the jitter is back.
> >>
> >> I've spent the last month trying to bisect it, but pretty much failed.
> >> It appears that versions closer to 2.6.38-rcX are more prone to display
> >> jitter, while 2.6.36 or so can have many successful runs. It also
> >> appears to be related to device power-on order, or so I've come to
> >> believe; A stable display can turn jittery, just by power cycling the TV.
> >>
Some further testing on a clean rc8 suggests that the jitter seen
there can reliably be removed by power cycling the TV while in X,
or starting X with the TV off.
I'm tempted to think that something makes too much out of bad
info collected from the TV, and falls backs to saner defaults if
the TV has nothing to say.
I've seen in the logs that the EDID is disliked:
[drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but
no|invalid EDID
Not sure if that is related though (cannot seem to be able to provoke
that error message right now)
-A
WARNING: multiple messages have this Message-ID (diff)
From: Anders Eriksson <aeriksson@fastmail.fm>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: airlied@redhat.com, xorg-driver-ati@lists.x.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: Radeon jittery post 2.6.35
Date: Tue, 15 Mar 2011 21:58:35 +0100 [thread overview]
Message-ID: <4D7FD2FB.9090505@fastmail.fm> (raw)
In-Reply-To: <AANLkTik0nXX+WEwa2xZ9VV+yHwrWnx+tYNdZXPEjk=SO@mail.gmail.com>
On 03/14/11 23:22, Alex Deucher wrote:
> On Mon, Mar 14, 2011 at 6:20 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
> > On Sun, Mar 13, 2011 at 10:08 AM, Anders Eriksson <aeriksson@fastmail.fm> wrote:
> >> Hi,
> >>
> >> I've found what I guess is a radeon (or drm/kms) regression post 2.6.35.
> >> I've got my TV conneced to my RS690G over HDMI, and the display has
> >> always been jittery after POST and at the GRUB screen. Pre-KMS, the X
> >> server (or driver got it sorted), and when KMS started, the display
> >> stabilized right after the kernel driver was initiated. However, post
> >> 2.6.35, I see the jitter is back.
> >>
> >> I've spent the last month trying to bisect it, but pretty much failed.
> >> It appears that versions closer to 2.6.38-rcX are more prone to display
> >> jitter, while 2.6.36 or so can have many successful runs. It also
> >> appears to be related to device power-on order, or so I've come to
> >> believe; A stable display can turn jittery, just by power cycling the TV.
> >>
Some further testing on a clean rc8 suggests that the jitter seen
there can reliably be removed by power cycling the TV while in X,
or starting X with the TV off.
I'm tempted to think that something makes too much out of bad
info collected from the TV, and falls backs to saner defaults if
the TV has nothing to say.
I've seen in the logs that the EDID is disliked:
[drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but
no|invalid EDID
Not sure if that is related though (cannot seem to be able to provoke
that error message right now)
-A
next prev parent reply other threads:[~2011-03-15 21:04 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 [this message]
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
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=4D7FD2FB.9090505@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.