From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100577] DC + TearFree display lock Date: Wed, 05 Apr 2017 10:52:40 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0852894894==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A13EB6E79B for ; Wed, 5 Apr 2017 10:52:40 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0852894894== Content-Type: multipart/alternative; boundary="14913895600.0b94cF993.6152"; charset="UTF-8" --14913895600.0b94cF993.6152 Date: Wed, 5 Apr 2017 10:52:40 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D100577 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=3D130688&action=3Dedit dmesg with errors and trace This one may be hard to reproduce for some as it seems to rely a bit on cpu= freq 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. S= eems 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=3Dx11 a720p60video --loop=3Dinf 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=3D0 on same kernel =3D 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 --=20 You are receiving this mail because: You are the assignee for the bug.= --14913895600.0b94cF993.6152 Date: Wed, 5 Apr 2017 10:52:40 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
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 1=
30688 [details]
dmesg with errors and trace

This one may be hard to reproduce for some as it seems to rely a bit on cpu=
freq
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. S=
eems
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=3Dx11 a720p60video --loop=3Dinf

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=3D0 on same kernel =3D 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.
= --14913895600.0b94cF993.6152-- --===============0852894894== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0852894894==--