Bug 91375 - [radeon] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed
Summary: [radeon] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performanc...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-17 17:14 UTC by Alexandre Demers
Modified: 2017-11-02 15:16 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg log (91.39 KB, text/plain)
2015-09-15 22:08 UTC, Raman Gupta
no flags Details
Kernel log (113.22 KB, text/plain)
2015-09-15 22:09 UTC, Raman Gupta
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandre Demers 2015-07-17 17:14:42 UTC
[drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed

I just found out there is this message at boot. Using latest ddx, mesa and drm from git combined with a 4.1 kernel. I don't see any impact or side effect.

As always, using a R9 280X.
Comment 1 Alex Deucher 2015-07-20 15:29:17 UTC
please attach your xorg log and dmesg output.  In most cases this can be ignored if things are working properly.
Comment 2 Alexandre Demers 2015-07-20 20:03:39 UTC
(In reply to Alex Deucher from comment #1)
> please attach your xorg log and dmesg output.  In most cases this can be
> ignored if things are working properly.

Hi Alex. I'll be attaching them later today. Sorry, that was my intention but I got distracted by another bug in Xserver (it was the bug in X that allowed me to discover this error in dmesg). However, there was nothing interesting in both files from what I remember.

I'm pretty sure it was not appearing in a previous combination of mesa, ddx, drm and kernel. I could try with a previous combination. I'll begin with an older kernel.

If this error can be ignored when things are working properly, we probably shouldn't output an error. It should be at most a warning and be displayed as an error only if it fails seriously, don't you think?
Comment 3 Alexandre Demers 2015-08-04 14:09:51 UTC
I've not encountered the error again... I wonder if it is related to a sleep / wake-up cycle... I'll have a look at that option. If I catch the error again, I'll post the info. Otherwise, I may just close the bug.
Comment 4 Raman Gupta 2015-09-15 22:08:27 UTC
I just got this error. My X server froze, though the mouse was still active. When I switched away to a different VT and then switched back, the screens were black.

Here are some more reports of the same problem:
https://bbs.archlinux.org/viewtopic.php?id=179906

My environment is Fedora 21 with the latest packages:

# uname -a
Linux edison 4.1.6-100.fc21.x86_64 #1 SMP Mon Aug 17 22:20:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Mesa 10.4.7

I will attach the Xorg log and kernel output from journalctl.
Comment 5 Raman Gupta 2015-09-15 22:08:52 UTC
Created attachment 118295 [details]
Xorg log
Comment 6 Raman Gupta 2015-09-15 22:09:11 UTC
Created attachment 118296 [details]
Kernel log
Comment 7 Raman Gupta 2015-09-15 22:13:02 UTC
Oh and the card information:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] (prog-if 00 [VGA controller])
        Subsystem: Hightech Information System Ltd. Device 2316
        Flags: bus master, fast devsel, latency 0, IRQ 47
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at fbe00000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at e000 [size=256]
        Expansion ROM at fbe40000 [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

02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] (prog-if 00 [VGA controller])
        Subsystem: Hightech Information System Ltd. Device 2316
        Flags: bus master, fast devsel, latency 0, IRQ 49
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at fbd00000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at d000 [size=256]
        Expansion ROM at fbd40000 [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
Comment 8 Daniel Exner 2015-11-04 10:27:42 UTC
Just started getting this when I upgraded my Monitor setup from single monitor connected via DVI at 1680x1050 by connecting another one via DisplayPort at 3440x1440.

Card (this is one of the one from #76490 using limited DPM):

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM] (prog-if 00 [VGA controller])
        Subsystem: Micro-Star International Co., Ltd. [MSI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM]
        Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at fea00000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at e000 [size=256]
        Expansion ROM at fea40000 [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: [200] #15  
        Capabilities: [270] #19  
        Capabilities: [2b0] Address Translation Service (ATS)
        Capabilities: [2c0] #13  
        Capabilities: [2d0] #1b  
        Kernel driver in use: radeon
        Kernel modules: radeon 

Kernel 4.3
Comment 9 Raman Gupta 2016-01-14 13:59:11 UTC
Still getting this error periodically on Fedora 23 kernel 4.3.3-300.fc23.x86_64, mesa 11.1.0.

The user-visible issue it seems to cause now is that one of my three monitors never wakes up from sleep (the monitor shows "no signal"). I have to switch to a VT, unplug the monitor and replug it (DisplayPort), which usually brings back the monitor display. Then I can switch back to X.

Note that the sleep issue is not immediately after the si_restrict_performance_levels_before_switch error message in dmesg, so it may or may not be related.

When the monitor is sleeping with no signal, xrandr -q shows that the monitor is connected normally (the monitor in question is DisplayPort-1):

~ xrandr -q
Screen 0: minimum 320 x 200, current 5920 x 1440, maximum 16384 x 16384
DisplayPort-0 connected primary 2560x1440+1680+0 (normal left inverted right x axis y axis) 597mm x 336mm
   2560x1440     59.95*+
   1920x1200     59.88  
   1920x1080     60.00    60.00    50.00    59.94    24.00    23.98  
   1920x1080i    60.00    50.00    59.94  
   1600x1200     60.00  
   1680x1050     59.95  
   1280x1024     75.02    60.02  
   1280x800      59.81  
   1152x864      75.00  
   1280x720      60.00    50.00    59.94  
   1024x768      75.08    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x576i      50.00  
   720x480       60.00    59.94  
   720x480i      60.00    59.94  
   640x480       75.00    60.00    59.94  
   720x400       70.08  
DisplayPort-1 connected 1680x1050+0+195 (normal left inverted right x axis y axis) 433mm x 270mm
   1680x1050     59.95*+
   1280x1024     60.02  
   1440x900      59.90  
   1280x960      60.00  
   1280x720      60.00  
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       60.00  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1680x1050+4240+195 (normal left inverted right x axis y axis) 433mm x 270mm
   1680x1050     59.95*+
   1280x1024     60.02  
   1440x900      59.90  
   1280x960      60.00  
   1280x720      60.00  
   1024x768      60.00  
   800x600       60.32    56.25                                                                                                                                                           
   640x480       60.00                                                                                                                                                                    
DisplayPort-1-2 disconnected (normal left inverted right x axis y axis)                                                                                                                   
DisplayPort-1-3 disconnected (normal left inverted right x axis y axis)                                                                                                                   
HDMI-1-1 disconnected (normal left inverted right x axis y axis)                                                                                                                          
DVI-1-1 disconnected (normal left inverted right x axis y axis)
Comment 10 Alex Perez 2017-08-09 00:39:34 UTC
I also get the "[drm:.si_dpm_set_power_state] *ERROR* si_restrict_performance_levels_before_switch failed"

...with 4.12.4, on Big Endian based powerpc64 machine (debian sid userland)
Comment 11 Alex Perez 2017-08-09 00:49:33 UTC
I also get the same message with 4.13.0-rc3
Comment 12 Harrison 2017-10-25 00:43:39 UTC
Also experiencing this bug on a fresh install of Ubuntu 17.10. I'm using a Radeon HD 7850.

harry@harry-ubuntu:~$ uname -a
Linux harry-ubuntu 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
harry@harry-ubuntu:~$ dmesg | egrep 'drm|radeon'
[    0.801726] [drm] radeon kernel modesetting enabled.
[    0.805265] fb: switching to radeondrmfb from VESA VGA
[    0.805474] [drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6819 0x174B:0xE218 0x00).
[    0.805569] radeon 0000:08:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[    0.805570] radeon 0000:08:00.0: GTT: 2048M 0x0000000080000000 - 0x00000000FFFFFFFF
[    0.805573] [drm] Detected VRAM RAM=2048M, BAR=256M
[    0.805573] [drm] RAM width 256bits DDR
[    0.805638] [drm] radeon: 2048M of VRAM memory ready
[    0.805638] [drm] radeon: 2048M of GTT memory ready.
[    0.805644] [drm] Loading pitcairn Microcode
[    0.805719] [drm] Internal thermal controller with fan control
[    0.805751] [drm] probing gen 2 caps for device 8086:151 = 261a103/e
[    0.812955] [drm] radeon: dpm initialized
[    0.816286] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[    0.816292] [drm] GART: num cpu pages 524288, num gpu pages 524288
[    0.817432] [drm] probing gen 2 caps for device 8086:151 = 261a103/e
[    0.817435] [drm] PCIE gen 3 link speeds already enabled
[    0.823221] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
[    0.823328] radeon 0000:08:00.0: WB enabled
[    0.823330] radeon 0000:08:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff9f7a09864c00
[    0.823331] radeon 0000:08:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff9f7a09864c04
[    0.823332] radeon 0000:08:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff9f7a09864c08
[    0.823332] radeon 0000:08:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff9f7a09864c0c
[    0.823333] radeon 0000:08:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff9f7a09864c10
[    0.823648] radeon 0000:08:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffb467c1635a18
[    0.843640] radeon 0000:08:00.0: fence driver on ring 6 use gpu addr 0x0000000080000c18 and cpu addr 0xffff9f7a09864c18
[    0.843641] radeon 0000:08:00.0: fence driver on ring 7 use gpu addr 0x0000000080000c1c and cpu addr 0xffff9f7a09864c1c
[    0.843647] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    0.843647] [drm] Driver supports precise vblank timestamp query.
[    0.843648] radeon 0000:08:00.0: radeon: MSI limited to 32-bit
[    0.843676] radeon 0000:08:00.0: radeon: using MSI.
[    0.843696] [drm] radeon: irq initialized.
[    0.998252] [drm] ring test on 0 succeeded in 4 usecs
[    0.998255] [drm] ring test on 1 succeeded in 1 usecs
[    0.998258] [drm] ring test on 2 succeeded in 1 usecs
[    0.998267] [drm] ring test on 3 succeeded in 6 usecs
[    0.998274] [drm] ring test on 4 succeeded in 5 usecs
[    1.173960] [drm] ring test on 5 succeeded in 2 usecs
[    1.173964] [drm] UVD initialized successfully.
[    1.283164] [drm] ring test on 6 succeeded in 29 usecs
[    1.283174] [drm] ring test on 7 succeeded in 3 usecs
[    1.283175] [drm] VCE initialized successfully.
[    1.283357] [drm] ib test on ring 0 succeeded in 0 usecs
[    1.283409] [drm] ib test on ring 1 succeeded in 0 usecs
[    1.283461] [drm] ib test on ring 2 succeeded in 0 usecs
[    1.283504] [drm] ib test on ring 3 succeeded in 0 usecs
[    1.283545] [drm] ib test on ring 4 succeeded in 0 usecs
[    1.952142] [drm] ib test on ring 5 succeeded
[    2.464166] [drm] ib test on ring 6 succeeded
[    2.976121] [drm] ib test on ring 7 succeeded
[    2.977065] [drm] Radeon Display Connectors
[    2.977065] [drm] Connector 0:
[    2.977065] [drm]   DP-1
[    2.977066] [drm]   HPD4
[    2.977067] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
[    2.977067] [drm]   Encoders:
[    2.977067] [drm]     DFP1: INTERNAL_UNIPHY2
[    2.977068] [drm] Connector 1:
[    2.977068] [drm]   DP-2
[    2.977068] [drm]   HPD5
[    2.977069] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c
[    2.977069] [drm]   Encoders:
[    2.977069] [drm]     DFP2: INTERNAL_UNIPHY2
[    2.977070] [drm] Connector 2:
[    2.977070] [drm]   HDMI-A-1
[    2.977070] [drm]   HPD1
[    2.977071] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
[    2.977071] [drm]   Encoders:
[    2.977071] [drm]     DFP3: INTERNAL_UNIPHY1
[    2.977071] [drm] Connector 3:
[    2.977072] [drm]   DVI-I-1
[    2.977072] [drm]   HPD6
[    2.977073] [drm]   DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 0x658c
[    2.977073] [drm]   Encoders:
[    2.977073] [drm]     DFP4: INTERNAL_UNIPHY
[    2.977073] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[    3.153644] [drm] fb mappable at 0xE05D8000
[    3.153645] [drm] vram apper at 0xE0000000
[    3.153645] [drm] size 8294400
[    3.153645] [drm] fb depth is 24
[    3.153646] [drm]    pitch is 7680
[    3.153682] fbcon: radeondrmfb (fb0) is primary device
[    3.153747] radeon 0000:08:00.0: fb0: radeondrmfb frame buffer device
[    3.168057] [drm] Initialized radeon 2.50.0 20080528 for 0000:08:00.0 on minor 0
[    3.182342] [drm] amdgpu kernel modesetting enabled.
[  888.873960] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed
harry@harry-ubuntu:~$ lspci -nn | grep -E 'VGA|Display'
08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819]
harry@harry-ubuntu:~$


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.