From: Anders Eriksson <aeriksson@fastmail.fm>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
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: Wed, 16 Mar 2011 22:40:44 +0100 [thread overview]
Message-ID: <4D812E5C.1010708@fastmail.fm> (raw)
In-Reply-To: <AANLkTikpBh2+OU2MUFo63oq9kBte7MK7rgwcuDKSwA_j@mail.gmail.com>
On 03/15/11 22:08, Jerome Glisse wrote:
> EDID failure could very well explain it, EDID retrieval seems to fails
> on some GPU under some circonstance (when there is CPU load that
> interfer with i2c timing i guess). Does the log have the edid failure
> message when the tv is jittering ? Or is it the otherway around ?
>
> Cheers,
> Jerome
It seems to be related to whether the TV is on (on that HDMI source) or not.
Mar 16 09:50:41 mynet kernel: [ 933.060281] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 09:53:46 mynet kernel: [ 1117.724206] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 09:54:47 mynet kernel: [ 1179.218109] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 09:54:57 mynet kernel: [ 1189.411883] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 09:55:32 mynet kernel: [ 1220.050871] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 20:27:51 mynet kernel: [ 952.693085] [drm:radeon_dvi_detect]
*ERROR* HDMI Type A-1: probed a monitor but no|invalid EDID
Mar 16 21:30:21 mynet kernel: [ 2272.384410] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 21:32:44 mynet kernel: [ 2415.931947] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 21:40:45 mynet kernel: [ 2896.698214] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 21:45:05 mynet kernel: [ 3152.643541] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Mar 16 21:53:00 mynet kernel: [ 3631.146133] [drm:radeon_dvi_detect]
*ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
The TV was
off at about 10 AM this morning (the HTPC was on playing music)
on a couple of hours in the afternoon showing the RS690 HDMI
on at 20:50-22:00 NOT showing the RS690 HDMI
Unfortunately I'm not sure what the TV's state was at 20:27:51
/A
next prev parent reply other threads:[~2011-03-16 21:41 UTC|newest]
Thread overview: 16+ 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-14 20:35 ` Anders Eriksson
2011-03-14 22:20 ` 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 21:08 ` Jerome Glisse
2011-03-16 21:40 ` Anders Eriksson [this message]
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
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=4D812E5C.1010708@fastmail.fm \
--to=aeriksson@fastmail.fm \
--cc=airlied@redhat.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
--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 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).