Bug 108547 - RX550 amdgpu_job_timedout ring sdma0 timeout; failed to send message; uvd_v6_0_enc_ring_test_ring; amdgpu_device_ip_resume failed
Summary: RX550 amdgpu_job_timedout ring sdma0 timeout; failed to send message; uvd_v6_...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-25 08:25 UTC by devbazilio
Modified: 2018-10-30 10:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg log file (132.58 KB, text/plain)
2018-10-25 08:25 UTC, devbazilio
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description devbazilio 2018-10-25 08:25:48 UTC
Created attachment 142190 [details]
dmesg log file

I had a lot of warning/or error messages in dmesg, sometimes UI and keyboard is completely freezes for several seconds, especially when browsing youtube

- [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout;
- [drm] IP block:gfx_v8_0 is hung!
- failed to send message N ret is 0
- [drm:uvd_v6_0_enc_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 13 test failed
- [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <uvd_v6_0> failed -110
- amdgpu_device_ip_resume failed
- amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 


Linux version 4.18.16-arch1-1-ARCH (builduser@heftig-28760) (gcc version 8.2.1 20180831 (GCC)) #1 SMP PREEMPT Sat Oct 20 22:06:45 UTC 2018


00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev ca) (prog-if 00 [VGA controller])
	Subsystem: Acer Incorporated [ALI] Wani [Radeon R5/R6/R7 Graphics]
	Flags: bus master, fast devsel, latency 0, IRQ 43
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Memory at d0800000 (64-bit, prefetchable) [size=8M]
	I/O ports at 4000 [size=256]
	Memory at d1500000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [270] Secondary PCI Express <?>
	Capabilities: [2b0] Address Translation Service (ATS)
	Capabilities: [2c0] Page Request Interface (PRI)
	Capabilities: [2d0] Process Address Space ID (PASID)
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu



03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon RX 550/550X] (rev c3)
	Subsystem: Acer Incorporated [ALI] Lexa PRO [Radeon RX 550/550X]
	Physical Slot: 0
	Flags: bus master, fast devsel, latency 0, IRQ 50
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Memory at d0000000 (64-bit, prefetchable) [size=2M]
	I/O ports at 2000 [size=256]
	Memory at d1200000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at d1240000 [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: [270] Secondary PCI Express <?>
	Capabilities: [320] Latency Tolerance Reporting
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu



Please let me know if I can help with something
Comment 1 Michel Dänzer 2018-10-25 08:47:34 UTC
Looks like bug 107762. There have been scheduler fixes which might help for this, but I'm not sure whether they've landed for 4.19 or only for 4.20.
Comment 2 devbazilio 2018-10-30 10:24:13 UTC
Downgraded all mesa packages from 18.2.3-1 to Mesa 18.2.2 and system works much better and stable


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.