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: Sun, 06 Jun 2010 11:17:29 +0200 Message-ID: <4C0B67A9.2080209@googlemail.com> References: <4C05F51E.8040603@googlemail.com> <1275466919.5860.72.camel@thor.local> <4C09012B.5020606@googlemail.com> <4C09176B.2050404@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail-fx0-f49.google.com (mail-fx0-f49.google.com [209.85.161.49]) by gabe.freedesktop.org (Postfix) with ESMTP id 51D6C9E710 for ; Sun, 6 Jun 2010 02:17:32 -0700 (PDT) Received: by fxm15 with SMTP id 15so1645955fxm.36 for ; Sun, 06 Jun 2010 02:17:31 -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 Am 04.06.2010 17:17, schrieb Alex Deucher: > 2010/6/4 Marius Gr=F6ger: >> 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= 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 coupl= e of >>>>>> seconds there's a very visual hickup, especially in scroll texts. >>>>>> >>>>>> Apologies for such an unspecific description, and for what almost se= ems >>>>>> 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. [...] > Any chance you can bisect the problematic commit? I did a second attempt at bisecting and now I'm confident it is this = commit which broke my real-time performance in mythtv: commit eb1f8e4f3be898df808e2dfc131099f5831d491d Author: Dave Airlie Date: Fri May 7 06:42:51 2010 +0000 drm/fbdev: rework output polling to be back in the core. (v4) Having found the commit is the good news. The bad news is that this = commit is rather large, so again I'd be depended on the experts around = here to isolate what's going on. Dave, would you mind giving a hand as well as the author of this commit? Thanks Marius