| Summary: | [Fiji/amdgpu/Powerplay] Problems with interactivity, performance, EQ overflow with Powerplay | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Ernst Sjöstrand <ernstp> | ||||||
| Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | medium | ||||||||
| Version: | XOrg git | ||||||||
| Hardware: | Other | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Ernst Sjöstrand
2015-11-18 17:07:52 UTC
So that was with the amdgpu DDX. I get a similar experience with modesetting driver, ie. mouse freezes when starting Steam, vsync doesn't work in gnome-shell, low FPS (at least on screen). Created attachment 119917 [details]
modesetting-dmesg
Created attachment 119918 [details]
modesetting-Xorg.0.log
It sounds like maybe the GPU interrupt isn't working reliably or something like that. My system only support PCI-Express 2.0, not 3.0. Could that be something? Does someone _not_ have these problems with Fiji? I don't even get 60 fps in glxgears with a tiny window: 292 frames in 5.0 seconds = 58.264 FPS 286 frames in 5.0 seconds = 57.198 FPS 291 frames in 5.0 seconds = 58.198 FPS (amdgpu ddx+dri2) Alex: is the commit causing that really part of your powerplay branch? Ok if I revert the two patches mentioned in bug 93147 I get 60.0 fps in glxgears and smoother desktop at startup. But I still have 1) mouse freezes when starting steam 2) if I run Unigine Heaven benchmark, apart from low performance (~30 fps @ 1080p), vsync seems to break down really bad during the run, and stays severely broken afterwards. (In reply to Ernst Sjöstrand from comment #9) > 1) mouse freezes when starting steam This is probably fixed in xserver 1.17.3 by http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.17-branch&id=8415eca0abc00ec96cb94cd656b58edbfa8f09a3 > 2) if I run Unigine Heaven benchmark, apart from low performance (~30 fps @ > 1080p), vsync seems to break down really bad during the run, and stays > severely broken afterwards. What does "vsync breaks down" mean exactly? It means that I get a lot of tearing both in 3D graphics like Unigine Heaven even though vsync is enabled, and when moving around a window in Gnome Shell. The modesetting driver in xserver 1.17 didn't support page flipping yet. To avoid tearing, you need the modesetting driver from xserver 1.18 or current xf86-video-amdgpu with Fiji support (and enable Option "DRI3" to avoid tearing when moving around windows in gnome-shell). I have xserver 2:1.17.2-1ubuntu9 and xserver-xorg-video-amdgpu 1.0.99+git1511200733.43c2dc~gd~w with DRI3 enabled now. Doesn't help, very bad interactivity during Unigine Heaven and vsync does not work during and after running Heaven. Please attach the log file for that and provide the output of "LIBGL_DEBUG=verbose glxinfo >/dev/null". Ah, I had been running with LIBGL_DRI3_DISABLE=1 because of https://bugs.freedesktop.org/show_bug.cgi?id=84252 https://bugzilla.mozilla.org/show_bug.cgi?id=1069523 So only applying that variable to Firefox it seems like I can't break vsync. (This was OK before powerplay though?) I saw a bunch of regressions when switching to the powerplay kernel so I listed them here, thinking they were caused by "powerplay". The rest are still there. Yey, seems to be solved! Seems to be solved for another user on the Phoronix forums also: http://openbenchmarking.org/result/1511262-HA-1510216HA93 http://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/834606-amd-tonga-fiji-open-source-performance-boosted-by-powerplay-patches/page6 After my latest pull of agd5f/amdgpu-powerplay I now get > 100 FPS in Unigine Heaven, the mouse cursor doesn't freeze when I start Steam etc. So it's one of the new commits on drm-next-4.5-wip I guess. Actually the EQ overflowing errors are not gone, they just happen so quickly now that I hardly notice it. Right, this was fixed! :-) |
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.