journalctl radeon error, switch to amdgpu kills lightdm

Post your bugs here.
User avatar
ilu
Posts: 2072
Joined: 09 Oct 2013 12:45

journalctl radeon error, switch to amdgpu kills lightdm

Postby ilu » 30 Jul 2018 17:00

I'm experiencing stutters, 10-20 secs hangs and sometimes the cursor vanishes. This journalctl message might be related:

Code: Select all

drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed
There are bug reports https://bugs.freedesktop.org/show_bug.cgi?id=91375 but, as it seems, no fix.

Code: Select all

dmesg | egrep 'drm|radeon'
[    1.489835] [drm] radeon kernel modesetting enabled.
[    1.490049] [drm] initializing kernel modesetting (VERDE 0x1002:0x683F 0x174B:0xE213 0x00).
[    1.490805] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[    1.490807] radeon 0000:01:00.0: GTT: 2048M 0x0000000040000000 - 0x00000000BFFFFFFF
[    1.490809] [drm] Detected VRAM RAM=1024M, BAR=256M
[    1.490809] [drm] RAM width 128bits DDR
[    1.490877] [drm] radeon: 1024M of VRAM memory ready
[    1.490878] [drm] radeon: 2048M of GTT memory ready.
[    1.490884] [drm] Loading verde Microcode
[    1.490991] [drm] Internal thermal controller without fan control
[    1.491054] [drm] probing gen 2 caps for device 1022:9603 = 300d02/0
[    1.497655] [drm] radeon: dpm initialized
[    1.498472] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[    1.498478] [drm] GART: num cpu pages 524288, num gpu pages 524288
[    1.500872] [drm] probing gen 2 caps for device 1022:9603 = 300d02/0
[    1.500875] [drm] PCIE gen 2 link speeds already enabled
[    1.530217] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
[    1.530316] radeon 0000:01:00.0: WB enabled
[    1.530318] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x        (ptrval)
[    1.530319] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0x        (ptrval)
[    1.530320] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0x        (ptrval)
[    1.530321] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x        (ptrval)
[    1.530322] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0x        (ptrval)
[    1.530581] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x        (ptrval)
[    1.554253] radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0x        (ptrval)
[    1.554254] radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0x        (ptrval)
[    1.554256] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.554256] [drm] Driver supports precise vblank timestamp query.
[    1.554257] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
[    1.554287] radeon 0000:01:00.0: radeon: using MSI.
[    1.554309] [drm] radeon: irq initialized.
[    2.060289] [drm] ring test on 0 succeeded in 1 usecs
[    2.060294] [drm] ring test on 1 succeeded in 1 usecs
[    2.060298] [drm] ring test on 2 succeeded in 1 usecs
[    2.060311] [drm] ring test on 3 succeeded in 9 usecs
[    2.060316] [drm] ring test on 4 succeeded in 3 usecs
[    2.238017] [drm] ring test on 5 succeeded in 2 usecs
[    2.238021] [drm] UVD initialized successfully.
[    2.348095] [drm] ring test on 6 succeeded in 20 usecs
[    2.348110] [drm] ring test on 7 succeeded in 5 usecs
[    2.348111] [drm] VCE initialized successfully.
[    2.348233] [drm] ib test on ring 0 succeeded in 0 usecs
[    2.348276] [drm] ib test on ring 1 succeeded in 0 usecs
[    2.348318] [drm] ib test on ring 2 succeeded in 0 usecs
[    2.348361] [drm] ib test on ring 3 succeeded in 0 usecs
[    2.348401] [drm] ib test on ring 4 succeeded in 0 usecs
[    3.000032] [drm] ib test on ring 5 succeeded
[    3.504042] [drm] ib test on ring 6 succeeded
[    4.008042] [drm] ib test on ring 7 succeeded
[    4.008372] [drm] Radeon Display Connectors
[    4.008373] [drm] Connector 0:
[    4.008373] [drm]   DP-1
[    4.008374] [drm]   HPD4
[    4.008375] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c
[    4.008375] [drm]   Encoders:
[    4.008376] [drm]     DFP1: INTERNAL_UNIPHY2
[    4.008376] [drm] Connector 1:
[    4.008376] [drm]   HDMI-A-1
[    4.008377] [drm]   HPD1
[    4.008378] [drm]   DDC: 0x6570 0x6570 0x6574 0x6574 0x6578 0x6578 0x657c 0x657c
[    4.008378] [drm]   Encoders:
[    4.008378] [drm]     DFP2: INTERNAL_UNIPHY2
[    4.008379] [drm] Connector 2:
[    4.008379] [drm]   DVI-I-1
[    4.008379] [drm]   HPD2
[    4.008380] [drm]   DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c
[    4.008380] [drm]   Encoders:
[    4.008381] [drm]     DFP3: INTERNAL_UNIPHY
[    4.008381] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[    4.131982] [drm] fb mappable at 0xD05D9000
[    4.131983] [drm] vram apper at 0xD0000000
[    4.131984] [drm] size 24883200
[    4.131984] [drm] fb depth is 24
[    4.131984] [drm]    pitch is 7680
[    4.132035] fbcon: radeondrmfb (fb0) is primary device
[    4.309783] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed
[    4.364351] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[    4.370055] [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 0
[    4.395950] [drm] amdgpu kernel modesetting enabled.
[    9.258036] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[   21.139863] radeon_dp_aux_transfer_native: 74 callbacks suppressed
I'm trying to circumvent this by using amdgpu instead of radeon, but the old way of blacklisting radeon doesn't work with my liquorix kernel. Instead grub needs this boot parameter

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="radeon.si_support=0 amdgpu.si_support=1"
(Replace si with cik if you are on a Sea Islands card)
I tried it by editing grub on the fly and the graphic booted up ok but lightdm refused to start.

Code: Select all

● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-07-30 19:23:17 CEST; 1min 49s ago
     Docs: man:lightdm(1)
  Process: 1315 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
  Process: 1311 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS)
 Main PID: 1315 (code=exited, status=1/FAILURE)

Jul 30 19:23:17 asusx9 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 30 19:23:17 asusx9 systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 30 19:23:17 asusx9 systemd[1]: Stopped Light Display Manager.
Jul 30 19:23:17 asusx9 systemd[1]: lightdm.service: Start request repeated too quickly.
Jul 30 19:23:17 asusx9 systemd[1]: Failed to start Light Display Manager.
Jul 30 19:23:17 asusx9 systemd[1]: lightdm.service: Unit entered failed state.
Jul 30 19:23:17 asusx9 systemd[1]: lightdm.service: Failed with result 'exit-code'. 
Any ideas why?

User avatar
ilu
Posts: 2072
Joined: 09 Oct 2013 12:45

Re: journalctl radeon error, switch to amdgpu kills lightdm

Postby ilu » 30 Jul 2018 18:05

This is the same problem but no solution: https://www.phoronix.com/forums/forum/l ... ith-amdgpu

Most other reports deal with amdgpu-pro.

Code: Select all

cat /var/log/Xorg.0.log |grep EE
(EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
This bug is usually reported for Intel/Nvidia combinations (bumblebee) but not for AMD.

Somebody said I should create a new desktop configuration for the user by resetting to defaults.

Code: Select all

sudo service lightdm stop
rm ~/.config/dconf/user
sudo service lightdm start
Did not help. Lightdm still refuses to cooperate.

Somebody else said to create /etc/X11/xorg.conf (which I thought was not needed anymore?) by

Code: Select all

sudo amdconfig --adapter=all --initial
Since I don't want to risk my running conf I'm holding back on this one.

I found an obscure remark about SDDM on https://wiki.gentoo.org/wiki/SDDM saying to fix permission issues with

Code: Select all

usermod -a -G video sddm
so I tried this next, for lightdm of course. Although the log complains about a permission issue it did not help.

Arjen, could you please have a look at this?


Return to “Bug control”

Who is online

Users browsing this forum: No registered users and 3 guests