From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Marius_Gr=F6ger?= Subject: Re: Glitch in newer drm-next/drm-radeon-testing Date: Fri, 04 Jun 2010 17:10:35 +0200 Message-ID: <4C09176B.2050404@googlemail.com> References: <4C05F51E.8040603@googlemail.com> <1275466919.5860.72.camel@thor.local> <4C09012B.5020606@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail-bw0-f49.google.com (mail-bw0-f49.google.com [209.85.214.49]) by gabe.freedesktop.org (Postfix) with ESMTP id D0CC19E710 for ; Fri, 4 Jun 2010 08:10:38 -0700 (PDT) Received: by bwz5 with SMTP id 5so420698bwz.36 for ; Fri, 04 Jun 2010 08:10:37 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Alex Deucher Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org Alex Deucher schrieb: > 2010/6/4 Marius Gr=F6ger : >> Hi All, >> >> Michel D=E4nzer schrieb: >>> On Mit, 2010-06-02 at 08:07 +0200, Marius Gr=F6ger 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 t= he >>>> 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=3Dprofile and profile=3Ddefault. Afai= ct >> 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