Linux 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon HD 7790/8770 / R7 360 / R9 260/360 OEM] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Bonaire XT [Radeon HD 7790/8770 / R7 360 / R9 260/360 OEM] Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at d0000000 (64-bit, prefetchable) [size=256M] Memory at cf800000 (64-bit, prefetchable) [size=8M] I/O ports at d000 [size=256] Memory at f7fc0000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] #19 Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] #13 Capabilities: [2d0] #1b Kernel driver in use: radeon Kernel modules: radeon, amdgpu After update linux kernel (> 4.09) VSYNC always(!!!) ON mode in all OpenGL videogames (max < 60 fps). Please, FIX and set correct VSYNC mode. "vblank_mode=0" is do NOT resolve this problem!
Please attach the Xorg log file and the output of dmesg and LIBGL_DEBUG=verbose vblank_mode=0 glxgears -info
This could be caused by the Ubuntu's Unity Compositor (Compiz). You could try forcing VSync off in one of Compiz config/tweak tools. It could also be caused by the tear free parameter. To test that try: xrandr --output VIDEO --set TearFree off where "VIDEO" is the name of your monitor output; you can find out by just running "xrandr" and it will list all of your monitor outputs. For example mine reads: HDMI-A-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm 1920x1080 60.00*+ 50.00 59.94 1920x1080i 60.00 50.00 59.94 1680x1050 59.88 1400x1050 59.95 1600x900 60.00 1280x1024 60.02 1440x900 59.90 1280x800 59.91 1152x864 75.00 1280x720 60.00 50.00 59.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.00 59.94 640x480 60.00 59.94 Thus I should write: xrandr --output HDMI-A-0 --set TearFree off
Created attachment 137954 [details] X.ORG log
Created attachment 137955 [details] glxinfo results
(In reply to Matias N. Goldberg from comment #2) > Thus I should write: > xrandr --output HDMI-A-0 --set TearFree off I also HDMI-0 output, but this command doesn't give any effect > This could be caused by the Ubuntu's Unity Compositor (Compiz). > You could try forcing VSync off in one of Compiz config/tweak tools. VSync is disabled in Compiz. In kernel <=4.09 VSync is correctly disabled in every video-game if appropriate checkbox is unset. But for kernels above 4.09 appropriate checkbox in the game has no effect. VSync ALWAYS ON!
(In reply to Matias N. Goldberg from comment #2) > This could be caused by the Ubuntu's Unity Compositor (Compiz). > You could try forcing VSync off in one of Compiz config/tweak tools. > > It could also be caused by the tear free parameter. Neither compositing nor TearFree directly affect the application's frame timing. (In reply to Vasya from comment #4) > glxinfo results As you can see, glxgears is running at thousands of frames per second, sync-to-vblank is clearly not enabled. Please provide the corresponding terminal output from running an affected application with LIBGL_DEBUG=verbose vblank_mode=0 .
Created attachment 138165 [details] cs source
It seems clear that the problem you're seeing is not related to sync-to-vblank. Since you say the problem started after updating the kernel, it's probably best to isolate the kernel change which introduced the problem. Can you bisect, or at least narrow down the version which introduced the problem?
(In reply to Michel Dänzer from comment #8) > It seems clear that the problem you're seeing is not related to > sync-to-vblank. > > Since you say the problem started after updating the kernel, it's probably > best to isolate the kernel change which introduced the problem. Can you > bisect, or at least narrow down the version which introduced the problem? It isn't possible. Also, after update video-driver (today) - i have 100% CPU load and 5 FPS in Counter-Strike Source. Facepalm!
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/843.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.