From: "Marius Gröger" <marius.groeger@googlemail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Glitch in newer drm-next/drm-radeon-testing
Date: Fri, 04 Jun 2010 17:10:35 +0200 [thread overview]
Message-ID: <4C09176B.2050404@googlemail.com> (raw)
In-Reply-To: <AANLkTinyqi8GW56RtKtOcdzZvwDNSdY5SmG61iG0a-RA@mail.gmail.com>
Alex Deucher schrieb:
> 2010/6/4 Marius Gröger <marius.groeger@googlemail.com>:
>> Hi All,
>>
>> Michel Dänzer schrieb:
>>> On Mit, 2010-06-02 at 08:07 +0200, Marius Gröger wrote:
>>>> Hello All,
>>>>
>>>> I'm trying the top-of-trunk drm-2.6 trees (both drm-next and
>>>> drm-radeon-testing) with my Radeon HD 3200 GPU over HDMI. The primary
>>>> application is mythtv which uses DRM syncing for the frame
>>>> syncronisation. Now, with the exact same userland software I noticed the
>>>> introduction of sync gliches in the May-timeframe. The
>>>> drm-radeon-testing on May 9 was still ok, but both drm-next and
>>>> drm-radeon-testing at the end of May showed that glitch: every couple of
>>>> seconds there's a very visual hickup, especially in scroll texts.
>>>>
>>>> Apologies for such an unspecific description, and for what almost seems
>>>> like a support request for MythTV. I wouldn't post here if I were not
>>>> 100% sure it must be related with the recent drm changes.
>>> Note that the DRM APIs are intended for use by userspace components of
>>> graphics drivers / API libraries, not applications directly. MythTV
>>> shouldn't use the DRM directly for synchronization but rather use GLX
>>> synchronization APIs.
>> What about that new dri2 vsync stuff which was mentioned related to [Bug
>> 28383]? Could the changes done for that in any way alter the timing? BTW
>> I measured the glitches I'm experiencing and the appear to be to happen
>> in intervals of 10 seconds. Again, all I'm changing is the kernel, and
>> even the kernel config is the same. I'd be most grateful for any
>> clues/hints/tips I could follow to resolve this regression.
>>
>>> If you have dynamic PM enabled, does disabling that help?
>> I checked again and there's method=profile and profile=default. Afaict
>> this is not using dynpm, right?
>>
>
> Correct.
Ok so with dynpm more or less ruled out, what could have such a visible
impact on the latencies? For instance, are we now more dependent (or
less) on some kind of interrupt or deferred processing than 6 weeks ago?
Btw, I have HDMI audio pretty much ruled out as well.
Thanks
Marius
next prev parent reply other threads:[~2010-06-04 15:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 6:07 Glitch in newer drm-next/drm-radeon-testing Marius Gröger
2010-06-02 8:21 ` Michel Dänzer
2010-06-02 8:47 ` Marius Gröger
2010-06-04 13:35 ` Marius Gröger
2010-06-04 15:01 ` Alex Deucher
2010-06-04 15:10 ` Marius Gröger [this message]
2010-06-04 15:17 ` Alex Deucher
2010-06-04 18:55 ` Marius Gröger
2010-06-04 20:02 ` Alex Deucher
2010-06-06 9:17 ` Marius Gröger
2010-06-06 16:47 ` James Simmons
2010-06-06 17:52 ` Marius Gröger
2010-06-06 22:15 ` Dave Airlie
2010-08-02 10:12 ` Marius Gröger
2010-08-02 10:17 ` Dave Airlie
-- strict thread matches above, loose matches on Subject: below --
2010-06-02 6:02 Marius Gröger
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=4C09176B.2050404@googlemail.com \
--to=marius.groeger@googlemail.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.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.