You are not logged in.

#1 2018-11-25 00:09:07

unit73e
Member
Registered: 2018-11-24
Posts: 3

R9 380 fails to retrieve minimum clocks and fails testing IB on ring

A lot of errors occur with AMDGPU and linux 4.19.2. With linux 4.18.16 everything works fine.

[   13.221304] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device
[   13.338690] audit: type=1130 audit(1543099458.478:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-F52E\x2dDC95 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   13.630888] amdgpu: [powerplay] 
                failed to send message 148 ret is 0 
[   14.172545] audit: type=1130 audit(1543099459.311:11): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-catalog-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   14.381173] amdgpu: [powerplay] 
                last message was failed ret is 0
[   14.754117] amdgpu: [powerplay] 
                failed to send message 145 ret is 0 
[   15.500203] amdgpu: [powerplay] 
                last message was failed ret is 0
[   15.876378] amdgpu: [powerplay] 
                failed to send message 146 ret is 0 
[   16.593945] audit: type=1131 audit(1543099461.734:12): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   16.620162] amdgpu: [powerplay] 
                last message was failed ret is 0
[   16.992487] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   17.676222] audit: type=1130 audit(1543099462.814:13): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ldconfig comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   17.734546] amdgpu: [powerplay] 
                last message was failed ret is 0
[   17.758106] audit: type=1130 audit(1543099462.898:14): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-done comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   18.105544] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   18.850562] amdgpu: [powerplay] 
                last message was failed ret is 0
[   19.222350] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   19.963335] amdgpu: [powerplay] 
                last message was failed ret is 0
[   20.333596] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   20.752419] audit: type=1130 audit(1543099465.891:15): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   21.077442] amdgpu: [powerplay] 
                last message was failed ret is 0
[   21.170048] microcode: CPU4: new patch_level=0x06000852
[   21.184597] microcode: CPU3: new patch_level=0x06000852
[   21.190235] microcode: CPU1: new patch_level=0x06000852
[   21.199207] microcode: CPU7: new patch_level=0x06000852
[   21.199261] x86/CPU: CPU features have changed after loading microcode, but might not take effect.
[   21.199262] x86/CPU: Please consider either early loading through initrd/built-in or a potential BIOS update.
[   21.238772] audit: type=1130 audit(1543099466.378:16): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   21.264310] audit: type=1127 audit(1543099466.404:17): pid=480 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
[   21.291947] audit: type=1130 audit(1543099466.431:18): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   21.335581] audit: type=1130 audit(1543099466.474:19): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   21.452023] it87: Found IT8721F chip at 0x290, revision 3
[   21.489728] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   22.233248] amdgpu: [powerplay] 
                last message was failed ret is 0
[   22.265840] audit: type=1130 audit(1543099467.404:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=alsa-restore comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   22.266304] audit: type=1130 audit(1543099467.408:21): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   22.305220] IPv6: ADDRCONF(NETDEV_UP): wlp6s5: link is not ready
[   22.438490] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   22.438492] Bluetooth: BNEP filters: protocol multicast
[   22.438496] Bluetooth: BNEP socket layer initialized
[   22.532823] audit: type=1130 audit(1543099467.671:22): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   22.615116] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   22.729500] audit: type=1130 audit(1543099467.868:23): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lm_sensors comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   22.753992] audit: type=1130 audit(1543099467.894:24): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   23.369143] amdgpu: [powerplay] 
                last message was failed ret is 0
[   23.543787] wlp6s5: authenticate with 9c:97:26:28:58:01
[   23.576017] wlp6s5: send auth to 9c:97:26:28:58:01 (try 1/3)
[   23.577799] wlp6s5: authenticated
[   23.579637] wlp6s5: associate with 9c:97:26:28:58:01 (try 1/3)
[   23.583106] wlp6s5: RX AssocResp from 9c:97:26:28:58:01 (capab=0x411 status=0 aid=1)
[   23.583320] wlp6s5: associated
[   23.662066] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s5: link becomes ready
[   23.754050] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   23.995041] 8021q: 802.1Q VLAN Support v1.8
[   24.500735] amdgpu: [powerplay] 
                last message was failed ret is 0
[   24.872506] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   25.617778] amdgpu: [powerplay] 
                last message was failed ret is 0
[   25.992049] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   26.741596] amdgpu: [powerplay] 
                last message was failed ret is 0
[   27.114620] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   27.855011] amdgpu: [powerplay] 
                last message was failed ret is 0
[   28.228628] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   28.968812] amdgpu: [powerplay] 
                last message was failed ret is 0
[   29.341100] amdgpu: [powerplay] 
                failed to send message 260 ret is 0 
[   29.341142] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:01:00.0 on minor 0
[   29.721961] amdgpu: [powerplay] 
                last message was failed ret is 0
[   30.095295] amdgpu: [powerplay] 
                failed to send message 155 ret is 0 
[   30.464511] amdgpu: [powerplay] 
                last message was failed ret is 0
[   30.836680] amdgpu: [powerplay] 
                failed to send message 15b ret is 0 
[   31.890401] amdgpu: [powerplay] 
                last message was failed ret is 0
[   32.284229] amdgpu: [powerplay] 
                failed to send message 154 ret is 0 
[   33.309795] [drm:amdgpu_uvd_ring_test_ib [amdgpu]] *ERROR* amdgpu: (0)IB test timed out.
[   33.309883] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 12 (-110).
[   33.939532] amdgpu: [powerplay] 
                last message was failed ret is 0
[   34.369127] amdgpu: [powerplay] 
                failed to send message 15a ret is 0 
[   34.369356] [drm:process_one_work] *ERROR* ib ring test failed (-110).
[   35.810908] amdgpu: [powerplay] 
                last message was failed ret is 0
[   36.216532] amdgpu: [powerplay] 
                failed to send message 155 ret is 0 
[   36.587560] amdgpu: [powerplay] 
                last message was failed ret is 0
[   36.962904] amdgpu: [powerplay] 
                failed to send message 15b ret is 0 

I'm using an MSI R9 380 Gaming 4G.

EDIT:
After searching a bit more I found there's an open bug: https://bugs.freedesktop.org/show_bug.cgi?id=108704
I'll check if this fixes my problem.

Last edited by unit73e (2018-11-25 00:25:24)

Offline

#2 2018-11-25 01:34:35

jamespharvey20
Member
Registered: 2015-06-09
Posts: 125

Re: R9 380 fails to retrieve minimum clocks and fails testing IB on ring

There's that patch which might help.

If that doesn't fix everything and if you're using "amdgpu.dpm=1" as a kenrel option, try removing "amdgpu.dpm=1".

If after trying both the patch and removing "amdgpu.dpm=1" it still doesn't work, if you have an error including "Cannot find any crtc or sizes", there's a bug open here: https://bugs.freedesktop.org/show_bug.cgi?id=108781

amdgpu 4.19 has at least 3 separate blackscreen bugs hitting the 280/290/380/390 chipsets.

Offline

#3 2018-11-25 01:48:30

loqs
Member
Registered: 2014-03-06
Posts: 7,480

Re: R9 380 fails to retrieve minimum clocks and fails testing IB on ring

Additional suggestions if the above does not resolve the issue you try linux 4.20-rc3 or amd-staging-drm-next.
Also as a general note please do not post grepped / severity filtered output as it removes context.

Offline

#4 2018-11-25 20:26:51

unit73e
Member
Registered: 2018-11-24
Posts: 3

Re: R9 380 fails to retrieve minimum clocks and fails testing IB on ring

jamespharvey20 wrote:

There's that patch which might help.

If that doesn't fix everything and if you're using "amdgpu.dpm=1" as a kenrel option, try removing "amdgpu.dpm=1".

If after trying both the patch and removing "amdgpu.dpm=1" it still doesn't work, if you have an error including "Cannot find any crtc or sizes", there's a bug open here: https://bugs.freedesktop.org/show_bug.cgi?id=108781

amdgpu 4.19 has at least 3 separate blackscreen bugs hitting the 280/290/380/390 chipsets.

The following patch solved my problem: https://bugs.freedesktop.org/show_bug.cgi?id=108781
I used linux 4.19.4 with the patch in that link.

loqs wrote:

Also as a general note please do not post grepped / severity filtered output as it removes context.

It's just cut where the amdgpu/drm lines begin, it's not grepped. Is it better to have the entire dmesg? I won't cut next time if that's the case.

Offline

#5 2018-11-25 20:30:12

2ManyDogs
Forum Moderator
Registered: 2012-01-15
Posts: 2,431

Re: R9 380 fails to retrieve minimum clocks and fails testing IB on ring

unit73e wrote:

It's just cut where the amdgpu/drm lines begin, it's not grepped. Is it better to have the entire dmesg? I won't cut next time if that's the case.

Yes, the full version is better. Use a pastebin client (not pastebin.com) if the file is large.

https://bbs.archlinux.org/viewtopic.php?id=57855

Last edited by 2ManyDogs (2018-11-25 20:32:22)

Offline

#6 2018-11-25 20:38:00

unit73e
Member
Registered: 2018-11-24
Posts: 3

Re: R9 380 fails to retrieve minimum clocks and fails testing IB on ring

2ManyDogs wrote:
unit73e wrote:

It's just cut where the amdgpu/drm lines begin, it's not grepped. Is it better to have the entire dmesg? I won't cut next time if that's the case.

Yes, the full version is better. Use a pastebin client (not pastebin.com) if the file is large.

https://bbs.archlinux.org/viewtopic.php?id=57855

Ok, thanks. Read and bookmarked. Hopefully this patch will be applied soon.

Offline

Board footer

Powered by FluxBB