From: "Michel Dänzer" <michel@daenzer.net>
To: "Marius Gröger" <marius.groeger@googlemail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Glitch in newer drm-next/drm-radeon-testing
Date: Wed, 02 Jun 2010 10:21:59 +0200 [thread overview]
Message-ID: <1275466919.5860.72.camel@thor.local> (raw)
In-Reply-To: <4C05F51E.8040603@googlemail.com>
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 I've tried so far:
>
> * I tried bisecting, but I failed to spot the offending commits somehow.
> My last hope is this list of experts - for me the git logs look sane,
> but you guy surely have more insight.
>
> * I tried turning on drm debug=1, but did not see anything suspicious,
> especially with relation to the r600 irq handling changes.
>
> * Currently I'm in the process of setting up systemtap to profile the
> scheduling, but I'm still on the learning curve :)
>
> I'd be most grateful for any tips and things to try to isolate this issue.
If you have dynamic PM enabled, does disabling that help?
--
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2010-06-02 8:22 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 [this message]
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
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=1275466919.5860.72.camel@thor.local \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=marius.groeger@googlemail.com \
/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.