[Radeon HD 7770 GHz Edition] Cape Verde XT: DPM set state failed

Submitted by Stepan Bakshaev

Assigned to Default DRI bug account

Link to original bug (#73788)

Description

Created attachment 92378
dmesg

I got in dmesg

[drm:si_dpm_set_power_state] ERROR si_set_sw_state failed

I have low fps in Team Fortress 2. There are 15-30 fps. cpu governor is performance. All settings are low and 1920 res. If I use catalyst I got more then 120 at high settings.

Attachment 92378, "dmesg":
dmesg

added Radeon bugzilla labels

📎 Stepan Bakshaev uploaded an attachment:

Attachment 92379, "xorg.log":
Xorg.0.log

💬 Hohahiu said:

I can confirm this bug. It also happens on mine 7750M.

💬 Stepan Bakshaev said:

Unigine Sanctuary on Cape Verde XT:
At present: 30 fps

Unigine
Sanctuary demo
benchmark edition v2.3
FPS: 29.9
Scores: 1267
Min FPS: 26.9
Max FPS: 31.8

Hardware
Binary: Linux 32bit GCC 4.3.2 Release May 20 2010
Operating system: Linux 3.13.0-4-generic x86_64
CPU model: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz
CPU flags: 3392MHz MMX SSE SSE2 SSE3 SSSE3 SSE41 SSE42 HTT
GPU model: Gallium 0.4 on AMD CAPE VERDE 3.0 Mesa 10.0.1 256Mb

Settings
Render: opengl
Mode: 1920x1080 fullscreen
Shaders: high
Textures: high
Filter: trilinear
Anisotropy: 4x
Translucence: enabled
Parallax: enabled
Reflection: enabled
DOF: disabled
HDR: disabled

Vsync is disabled.

Temp grows from 37 to 59.

💬 Alex Deucher @agd5f said:

Is this a regression? Was dpm working previously at some point, if so when?

💬 Stepan Bakshaev said:

(In reply to comment 4)

Is this a regression? Was dpm working previously at some point, if so when?

Alex, I want to check this. What should I start from? You added si_dpm.c at 2013-06-27 (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/gpu/drm/radeon/si_dpm.c?showmsg=1). Were there another system to change power management before? Is it enought to find first stable version available in ubuntu repo with si_dpm.c? Or should I use kernel from git and start bisect by history of si_dpm.c?

💬 Arek Ruśniak said:

3.12.8 looks good. 3.13rc2 gives me this message on cape verde xt, I couldn't build&test rc1 (don't know why)

💬 Hohahiu said:

(In reply to comment 4)

Is this a regression? Was dpm working previously at some point, if so when?

It worked fine in 3.11 and 3.12. The problem appeared somewhere during the development of 3.13. At those point vgaswitcheroo didn't work and I had to stick to older versions of the kernel.

💬 Stepan Bakshaev said:

I installed kernel from here http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

and try to change power_method by http://xorg.freedesktop.org/wiki/RadeonFeature/#kmspowermanagementoptions

root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# uname -a
Linux silverstone 3.12.0-031200-generic #201311071835 SMP Thu Nov 7 23:36:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.12.0-031200-generic root=UUID=4d025cce-1bf0-466f-a5c3-501d3f548e70 ro quiet splash vt.handoff=7 radeon.dpm=1

root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# echo "dynpm" > power_method
bash: echo: write error: Invalid argument
root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# echo "profile" > power_method
bash: echo: write error: Invalid argument
root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# cat power_method
dpm

root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# echo "high" > power_profile
bash: echo: write error: Invalid argument
root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# cat power_profile
default

root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# dmesg | grep 'drm.*error'

root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# cat class
0x030000
root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# cat vendor
0x1002
root@silverstone:/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0# cat device
0x683d

There are no errors and no success in changing power_method. Where did I do mistake?

💬 Stepan Bakshaev said:

Return to 3.13

root@silverstone:/sys/class/drm/card0/device# uname -a
Linux silverstone 3.13.0-5-generic #20 (closed)-Ubuntu SMP Mon Jan 20 19:56:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
root@silverstone:/sys/class/drm/card0/device# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=4d025cce-1bf0-466f-a5c3-501d3f548e70 ro quiet splash vt.handoff=7 radeon.dpm=1

root@silverstone:/sys/class/drm/card0/device# echo "dynpm" > power_method
bash: echo: write error: Invalid argument
root@silverstone:/sys/class/drm/card0/device# cat power_method
dpm

root@silverstone:/sys/class/drm/card0/device# echo "high" > power_profile
bash: echo: write error: Invalid argument

root@silverstone:/sys/class/drm/card0/device# dmesg | grep -i "drm.*error"
[ 13.800555] [drm:si_dpm_set_power_state] ERROR si_set_sw_state failed

root@silverstone:/sys/class/drm/card0/device# cat vendor
0x1002
root@silverstone:/sys/class/drm/card0/device# cat device
0x683d

💬 Alex Deucher @agd5f said:

(In reply to comment 7)

(In reply to comment 4)

Is this a regression? Was dpm working previously at some point, if so when?

It worked fine in 3.11 and 3.12. The problem appeared somewhere during the
development of 3.13. At those point vgaswitcheroo didn't work and I had to
stick to older versions of the kernel.

Any chance you could bisect?

💬 Alex Deucher @agd5f said:

(In reply to comment 8)

There are no errors and no success in changing power_method. Where did I do
mistake?

We don't support changing between dpm and the older methods dynamically. When you enable dpm, you can't switch to the older pm methods.

💬 Arek Ruśniak said:

Alex it's here:

http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-3.13-wip&id=4573388c92ee60b4ed72b8d95b73df861189988c

💬 Arek Ruśniak said:

in my case it's error message in dmesg output only, performance is pretty the same.

kernel ver. 3.13 vs 12.8
lightsmark 245,42 245,84
unigine:
valley 17,55 17,5
sanctuary 65,64 65,63
gputest:
plot3D 16603 16555
furmark 1519 1520
triangle 96610 96541
pix. piano 127 127
pix. volplosion 1060 1060

powered by pts :)

hardware: i5-4670 + 8GB + radeon hd7770 + display@1680x1050
software: archlinux 64b/mesa-git-00c6720/llvm-svn-199943/ddx&glamor-8 days old/xserver-1.15/gnome3

💬 Alex Deucher @agd5f said:

(In reply to comment 12)

Alex it's here:

http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-3.13-
wip&id=4573388c92ee60b4ed72b8d95b73df861189988c

Does reverting that commit fix the problem?

💬 Arek Ruśniak said:

yes it does. dmesg doesn't show "[drm:si_dpm_set_power_state] ERROR si_set_sw_state failed".
i've tested it on mainline tree

💬 Stepan Bakshaev said:

1. checkout git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git
   
2. revert 4573388c92ee60b4ed72b8d95b73df861189988c
   
3. no error si_set_sw_state failed

closed