dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100577] DC + TearFree  display lock
Date: Wed, 05 Apr 2017 10:52:40 +0000	[thread overview]
Message-ID: <bug-100577-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1956 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100577

            Bug ID: 100577
           Summary: DC + TearFree  display lock
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adf.lists@gmail.com

Created attachment 130688
  --> https://bugs.freedesktop.org/attachment.cgi?id=130688&action=edit
dmesg with errors and trace

This one may be hard to reproduce for some as it seems to rely a bit on cpufreq
ondemand being a bit rubbish on my old cpu. Lowest is 800MHz for me (high 3.4
GHz).

I don't use a compositing desktop and vids played in my browser (seamonkey)
don't get vsync.

Turning on TearFree gets me vsync, but while testing I got a screen lock. Seems
to involve timing luck - I couldn't reproduce with the browser in a sane
timescale so invented a different test that could run while AFK.

mpv -fs --vo=x11 a720p60video --loop=inf

Will usually lock in < 15 minutes with cpufreq ondemand.

It was still going after an hour with cpufreq set to perf.

Also seems OK with amdgpu.dc=0 on same kernel = amd-staging-4.9

As I've only recently started running DC, and never tried this test before, I
have no idea whether it ever worked.

xserver is latest release ddx is git.

dmesg attached shows errors and a trace starting with

[ 2009.442985] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]]
*ERROR* [CRTC:39:crtc-0] flip_done timed out
[ 2013.027575] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]]
*ERROR* [CRTC:39:crtc-0] flip_done timed out
[ 2013.027727] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR*
dm_dc_surface_commit: acrtc 0, already busy

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3379 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-04-05 10:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 10:52 bugzilla-daemon [this message]
2017-04-06  2:29 ` [Bug 100577] DC + TearFree display lock bugzilla-daemon
2017-05-04  9:08 ` bugzilla-daemon
2017-05-04  9:10 ` bugzilla-daemon
2017-05-06 17:54 ` bugzilla-daemon
2017-05-07  7:38 ` bugzilla-daemon
2017-05-16 21:47 ` bugzilla-daemon
2017-05-17 13:16 ` bugzilla-daemon
2017-05-17 22:17 ` bugzilla-daemon
2017-07-05 18:44 ` bugzilla-daemon
2017-07-05 18:59 ` bugzilla-daemon
2017-07-05 19:19 ` bugzilla-daemon
2017-07-05 20:01 ` bugzilla-daemon
2017-07-05 20:02 ` bugzilla-daemon
2017-07-05 20:03 ` bugzilla-daemon
2017-07-05 20:11 ` bugzilla-daemon
2017-07-05 20:37 ` bugzilla-daemon
2017-08-16 12:54 ` bugzilla-daemon

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=bug-100577-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox