All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97362] Low performance after suspend on RX 480
Date: Tue, 16 Aug 2016 10:32:53 +0000	[thread overview]
Message-ID: <bug-97362-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2468 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=97362

            Bug ID: 97362
           Summary: Low performance after suspend on RX 480
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: haagch@frickel.club

Created attachment 125811
  --> https://bugs.freedesktop.org/attachment.cgi?id=125811&action=edit
dmesg

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Ellesmere [Polaris10] (rev c7)

Tried on vanilla Linux 4.7 and 4.8-rc2 with the async pageflip commit reverted.

I'm testing with a very simple directx9 application (without nine) because the
impact is extremely obvious with wine:
http://www.codesampler.com/dx9src/dx9src_1.htm#dx9_initialization

Before suspending it runs with 5000+ FPS, after suspending it runs with <1000.
Also, if you keep the mouse pointer over the window moving, it will have a very
small performance drop before suspending and a huuuge performance drop after
suspending.

I looked at the powerplay values in sysfs while that application is running in
wine and before suspend,
pcie is
0: 2.5GB, x8 
1: 8.0GB, x16 *
and sclk is
0: 300Mhz 
1: 608Mhz 
2: 910Mhz 
3: 1077Mhz 
4: 1145Mhz 
5: 1191Mhz 
6: 1236Mhz 
7: 1288Mhz *

after suspend it's
pcie
0: 2.5GB, x8 *
1: 8.0GB, x16 
and sclk
0: 300Mhz 
1: 608Mhz *
2: 910Mhz 
3: 1077Mhz 
4: 1145Mhz 
5: 1191Mhz 
6: 1236Mhz 
7: 1288Mhz 


mclk is
0: 300Mhz 
1: 2000Mhz *
in both cases.

I then tried
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
and the sclk clock goes to max and pcie goes to 16x again, but the performance
of the application does NOT increase so it looks like the low clocks are a
symptom of whatever causes low performance.

dmesg from 4.8-rc2 attached, shows some errors:

[  574.369317] 
                failed to send message 5e ret is 0 


[  574.369317] [drm:amdgpu_vce_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 12
test failed
[  574.369317] [drm:amdgpu_resume [amdgpu]] *ERROR* resume of IP block
<vce_v3_0> failed -110
[  574.369317] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed
(-110).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3949 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-08-16 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 10:32 bugzilla-daemon [this message]
2016-08-17 23:50 ` [Bug 97362] Low performance after suspend on RX 480 bugzilla-daemon
2016-08-23 21:10 ` bugzilla-daemon
2016-08-30 12:50 ` bugzilla-daemon
2017-02-12 22:03 ` bugzilla-daemon
2019-11-19  8:09 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-97362-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.