Bug 107561

Summary: [amdgpu] / rx550 / half the fps after thaw
Product: DRI Reporter: arne_woerner
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: high    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
radeontop (before and after the thaw)
none
Xorg.0.log from fresh boot until second suspend
none
log messages from reboot until second suspend none

Description arne_woerner 2018-08-13 19:05:18 UTC
Created attachment 141070 [details]
radeontop (before and after the thaw)

Hi!

When I hibernate+thaw my box i get just appr. 13fps in the same scene that I saw with appr. 26fps after a fresh reboot.

I use archlinux with 4.17.14-arch1-1-ARCH and a A10-5800K and a RX550.

Funnily after the thaw the GPU seems to be much busier with the same scene
(see the attached radeontop output).

I would prefer not to reboot daily...

Thx.

Bye
Arne
Comment 1 arne_woerner 2018-12-28 21:36:10 UTC
Hi!

The bug is still there.

Is there something I could do in order to fix it?

Or is suspend/resume not really supported?
I use it daily and almost never use `halt -p`...

Thx.

Bye.
Comment 2 Alex Deucher 2018-12-28 21:51:13 UTC
Please attach your xorg log and dmesg output.
Comment 3 arne_woerner 2018-12-29 04:49:14 UTC
Created attachment 142906 [details]
Xorg.0.log from fresh boot until second suspend
Comment 4 arne_woerner 2018-12-29 05:05:15 UTC
Created attachment 142907 [details]
log messages from reboot until second suspend
Comment 5 arne_woerner 2018-12-29 05:09:46 UTC
Comment on attachment 142907 [details]
log messages from reboot until second suspend

i removed the lines with
crond|CROND|iptables(vaako.intern.wgboome.org kernel: IN=eth0 OUT= MAC=)
-arne
Comment 6 arne_woerner 2019-01-02 07:46:58 UTC
Hi!
Since kernel-4.20.0 the fps after thaw are as before thaw...
Thx.
Bye.

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.