From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 97461] FS-UAE waits forever with glClientWaitSync() when using glFenceSync() on amdgpu/radeonsi Date: Wed, 24 Aug 2016 09:06:57 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1456755451==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 179176E028 for ; Wed, 24 Aug 2016 09:06:57 +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 --===============1456755451== Content-Type: multipart/alternative; boundary="14720296170.dfddC45.26660"; charset="UTF-8" --14720296170.dfddC45.26660 Date: Wed, 24 Aug 2016 09:06:57 +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=3D97461 Bug ID: 97461 Summary: FS-UAE waits forever with glClientWaitSync() when using glFenceSync() on amdgpu/radeonsi Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: lem.jjr@gmail.com QA Contact: dri-devel@lists.freedesktop.org Created attachment 125993 --> https://bugs.freedesktop.org/attachment.cgi?id=3D125993&action=3Dedit apitrace of fs-uae waiting forever after using glFenceSync() Hi, In recent mesa-git (during August 2016), there was a change to amdgpu/radeo= nsi that has caused FS-UAE (Amiga emulator) to wait forever with glClientWaitSy= nc() after using glFenceSync(). While it is waiting, it uses 24% CPU but does not cause the CPU to clock to higher pstates. Using an alternative OpenGL rende= ring mode that does not include fences allows FS-UAE to start as expected. This problem is not present on nVidia, AMDGPU-PRO, nor open source amdgpu as shi= pped with Ubuntu 16.04, and has only been a problem during this month (August 20= 16). Hardware: AMD FX-8350 AMD Radeon 380X 4Gb Asus MG279 27" 2560x1440 144Hz IPS, connected via DisplayPort Software: Ubuntu 16.04 AMD64 Padoka PPA FS-UAE 2.7.14dev2 from https://launchpad.net/~fengestad/+archive/ubuntu/dev= el Notable apitrace output on frame number 3 of a waiting instance of fs-uae (= from the attached apitrace file): 1490 @0 glFenceSync(condition =3D GL_SYNC_GPU_COMMANDS_COMPLETE, flags =3D = 0) =3D 0x8aba220 1491 @0 glFlush() 1492 @0 glClientWaitSync(sync =3D 0x8aba220, flags =3D GL_SYNC_FLUSH_COMMAN= DS_BIT, timeout =3D 0) =3D GL_TIMEOUT_EXPIRED 1493 @0 glClientWaitSync(sync =3D 0x8aba220, flags =3D 0x0, timeout =3D 0) = =3D GL_TIMEOUT_EXPIRED ..... 15561 @0 glClientWaitSync(sync =3D 0x8aba220, flags =3D 0x0, timeout =3D 0)= =3D GL_TIMEOUT_EXPIRED I suspect this will be related to the fences work that has been committed recently? Happy to do more testing. I have also reported the bug in the FS-UAE development thread here: http://eab.abime.net/showpost.php?p=3D1107609&postcount=3D1146 In case it's helpful at this point: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TONGA (DRM 3.1.0 / 4.4.0-34-lowlatency, LLVM 4.0.0) OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.1.0-devel - padoka PPA OpenGL core profile shading language version string: 4.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 12.1.0-devel - padoka PPA OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.1.0-devel - padoka = PPA OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 Cheers --=20 You are receiving this mail because: You are the assignee for the bug.= --14720296170.dfddC45.26660 Date: Wed, 24 Aug 2016 09:06:57 +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 97461
Summary FS-UAE waits forever with glClientWaitSync() when using glFen= ceSync() on amdgpu/radeonsi
Product Mesa
Version git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component Drivers/Gallium/radeonsi
Assignee dri-devel@lists.freedesktop.org
Reporter lem.jjr@gmail.com
QA Contact dri-devel@lists.freedesktop.org 

Created attachment 125993 [details]
apitrace of fs-uae waiting forever after using glFenceSync()

Hi,

In recent mesa-git (during August 2016), there was a change to amdgpu/radeo=
nsi
that has caused FS-UAE (Amiga emulator) to wait forever with glClientWaitSy=
nc()
after using glFenceSync(). While it is waiting, it uses 24% CPU but does not
cause the CPU to clock to higher pstates. Using an alternative OpenGL rende=
ring
mode that does not include fences allows FS-UAE to start as expected. This
problem is not present on nVidia, AMDGPU-PRO, nor open source amdgpu as shi=
pped
with Ubuntu 16.04, and has only been a problem during this month (August 20=
16).

Hardware:
AMD FX-8350
AMD Radeon 380X 4Gb
Asus MG279 27" 2560x1440 144Hz IPS, connected via DisplayPort

Software:
Ubuntu 16.04 AMD64
Padoka PPA
FS-UAE 2.7.14dev2 from https://launchpad.net/~fengestad/+archive/ubuntu/devel


Notable apitrace output on frame number 3 of a waiting instance of fs-uae (=
from
the attached apitrace file):

1490 @0 glFenceSync(condition =3D GL_SYNC_GPU_COMMANDS_COMPLETE, flags =
=3D 0) =3D
0x8aba220
1491 @0 glFlush()
1492 @0 glClientWaitSync(sync =3D 0x8aba220, flags =3D GL_SYNC_FLUSH_CO=
MMANDS_BIT,
timeout =3D 0) =3D GL_TIMEOUT_EXPIRED
1493 @0 glClientWaitSync(sync =3D 0x8aba220, flags =3D 0x0, timeout =3D=
 0) =3D
GL_TIMEOUT_EXPIRED
.....
15561 @0 glClientWaitSync(sync =3D 0x8aba220, flags =3D 0x0, timeout =
=3D 0) =3D
GL_TIMEOUT_EXPIRED


I suspect this will be related to the fences work that has been committed
recently?

Happy to do more testing. I have also reported the bug in the FS-UAE
development thread here:
http://eab.abime.net/showpost.php?p=3D1107609&postcount=3D1146

In case it's helpful at this point:

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD TONGA (DRM 3.1.0 /
4.4.0-34-lowlatency, LLVM 4.0.0)
OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.1.0-devel -
padoka PPA
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 12.1.0-devel - padoka PPA
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.1.0-devel - padoka =
PPA
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10


Cheers

You are receiving this mail because:
  • You are the assignee for the bug.
= --14720296170.dfddC45.26660-- --===============1456755451== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1456755451==--