Bug 201957 - amdgpu: ring gfx timeout
Summary: amdgpu: ring gfx timeout
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: Intel Linux
: P1 blocking
Assignee: drivers_video-dri
URL:
Keywords:
: 204683 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-12-11 04:52 UTC by e88z4
Modified: 2020-01-24 10:48 UTC (History)
22 users (show)

See Also:
Kernel Version: 4.19.8, 4.20-rc5
Tree: Mainline
Regression: No


Attachments
5 second video clip that triggers a crash (2.39 MB, text/vnd.trolltech.linguist)
2019-10-27 18:44 UTC, shallowaloe
Details
attachment-25111-0.html (2.65 KB, text/html)
2019-12-08 17:32 UTC, shallowaloe
Details
kernel config 5.4.7 Fiji (105.36 KB, text/plain)
2020-01-02 09:11 UTC, Janpieter Sollie
Details
/proc/cpuinfo (10.91 KB, text/plain)
2020-01-19 17:04 UTC, F. Delente
Details
lspci output (2.41 KB, text/plain)
2020-01-19 17:04 UTC, F. Delente
Details

Description e88z4 2018-12-11 04:52:52 UTC
Error message: 
[Dec 5 22:08] amdgpu 0000:23:00.0: GPU fault detected: 146 0x0000480c for process yuzu pid 2920 thread yuzu:cs0 pid 2935
[  +0.000005] amdgpu 0000:23:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
[  +0.000002] amdgpu 0000:23:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0604800C
[  +0.000003] amdgpu 0000:23:00.0: VM fault (0x0c, vmid 3, pasid 32770) at page 0, read from 'TC4' (0x54433400) (72)
[ +10.053011] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=37241, emitted seq=37244
[  +0.000007] [drm] GPU recovery disabled.


How to reproduce the issue:
1. Playing with yuzu-emulator 
2. Load Super Mario Odyssey
3. Start new game
4. When Mario is about to jump for the first time after being woken up by Cappy, this bug must occur. 

During the issue, the following occured:
1. Graphic locked up. 
2. System can be access through SSH.

System specification:
Debian Sid
Radeon RX 580

I have tried the following combination:
1. Kernel 4.17, 4.18, 4.19, 4.20, drm-next-4.21.wip
2. Mesa 18.2, 18.3, 19.0-development branch

But none of the above combination fixes the issue. Let me know if you need more information and more testing from me.
Comment 1 Alex Deucher 2018-12-11 14:57:43 UTC
This is more likely a mesa issue than a kernel issue.
Comment 2 e88z4 2018-12-11 18:18:17 UTC
I will try to test with amdgpu-pro sometimes this week with the kernel that I mentioned above. If the application works as expected, it could be an issue with mesa opengl bug.
Comment 3 Dev Bazilio 2019-03-07 05:20:32 UTC
(In reply to Alex Deucher from comment #1)
> This is more likely a mesa issue than a kernel issue.

no, 4.14 kernel with latest mesa libs works very vell without any stucks
but from 4.20.4 and in all latest kernels (including 5.0) OS freezes and stucks every 30s ... 1min for 30s when browsing youtube with HW acceleration enabled(uvd) or playing a game, RX550, Arch, vanilla kernel

  365.021164] amdgpu: [powerplay] 
                last message was failed ret is 0
[  365.045198] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
[  365.570667] amdgpu: [powerplay] 
                failed to send message 133 ret is 0 
[  366.115228] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=9365, emitted seq=9365
[  366.115377] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
[  366.115388] [drm] Timeout, but no hardware hang detected.
[  366.689407] amdgpu: [powerplay] 
                last message was failed ret is 0
[  367.232287] amdgpu: [powerplay] 
                failed to send message 306 ret is 0 
[  367.787043] amdgpu: [powerplay] 
                last message was failed ret is 0
[  368.320138] amdgpu: [powerplay] 
                failed to send message 5e ret is 0 
[  369.367739] amdgpu: [powerplay] 
                last message was failed ret is 0
[  369.907559] amdgpu: [powerplay] 
                failed to send message 145 ret is 0 
[  370.994478] amdgpu: [powerplay] 
                last message was failed ret is 0
[  371.538753] amdgpu: [powerplay] 
                failed to send message 146 ret is 0 
[  372.075079] amdgpu: [powerplay] 
                last message was failed ret is 0
[  372.598565] amdgpu: [powerplay] 
                failed to send message 148 ret is 0 
[  373.657188] amdgpu: [powerplay] 
                last message was failed ret is 0
[  374.198637] amdgpu: [powerplay] 
                failed to send message 145 ret is 0 
[  375.075076] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
[  375.284948] amdgpu: [powerplay] 
                last message was failed ret is 0
[  375.830347] amdgpu: [powerplay] 
                failed to send message 146 ret is 0 
[  376.138428] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=10113, emitted seq=10113
[  376.138783] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
[  376.138797] [drm] IP block:sdma_v3_0 is hung!
[  376.138809] [drm] GPU recovery disabled.
[  376.394657] amdgpu: [powerplay] 
                last message was failed ret is 0
[  376.934375] amdgpu: [powerplay] 
                failed to send message 16a ret is 0 
[  377.463230] amdgpu: [powerplay] 
                last message was failed ret is 0
[  377.977725] amdgpu: [powerplay] 
                failed to send message 186 ret is 0 
[  378.518406] amdgpu: [powerplay] 
                last message was failed ret is 0
[  379.060098] amdgpu: [powerplay] 
                failed to send message 54 ret is 0 
[  379.556880] amdgpu: [powerplay] 
                last message was failed ret is 0
[  380.075217] amdgpu: [powerplay] 
                failed to send message 26b ret is 0 
[  380.605976] amdgpu: [powerplay] 
                last message was failed ret is 0
[  381.134301] amdgpu: [powerplay] 
                failed to send message 13d ret is 0 
[  381.657486] amdgpu: [powerplay] 
                last message was failed ret is 0
[  382.204551] amdgpu: [powerplay] 
                failed to send message 14f ret is 0 
[  382.741827] amdgpu: [powerplay] 
                last message was failed ret is 0
[  383.281165] amdgpu: [powerplay] 
                failed to send message 151 ret is 0 
[  383.824923] amdgpu: [powerplay] 
                last message was failed ret is 0
[  384.362266] amdgpu: [powerplay] 
                failed to send message 135 ret is 0 
[  384.903686] amdgpu: [powerplay] 
                last message was failed ret is 0
[  385.101515] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
[  385.461515] amdgpu: [powerplay] 
                failed to send message 190 ret is 0 
[  386.014015] amdgpu: [powerplay] 
                last message was failed ret is 0
[  386.164818] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=10761, emitted seq=10761
[  386.164970] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
[  386.164985] [drm] Timeout, but no hardware hang detected.
Comment 4 Alex Deucher 2019-03-07 05:24:36 UTC
Can you bisect?
Comment 5 Cameron 2019-03-12 13:15:31 UTC
I'm having a very similar issue, running Linux Mint 19.1. The issue has persisted from at least 4.15, I'm currently running 5.0.1 and the issue remains. 

Here is the latest syslog of the error:

[37258.615599] gmc_v9_0_process_interrupt: 10 callbacks suppressed
[37258.615608] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615615] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107805000 from 27
[37258.615619] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
[37258.615629] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615633] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107807000 from 27
[37258.615636] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37258.615645] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615648] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107801000 from 27
[37258.615651] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37258.615660] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615663] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107803000 from 27
[37258.615666] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37258.615675] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615678] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107809000 from 27
[37258.615681] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37258.615689] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615692] amdgpu 0000:06:00.0:   in page starting at address 0x000080010780b000 from 27
[37258.615695] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37258.615704] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615707] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107805000 from 27
[37258.615710] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37258.615740] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615743] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107807000 from 27
[37258.615746] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37258.615756] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615759] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107801000 from 27
[37258.615762] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37258.615771] amdgpu 0000:06:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1287 thread Xorg:cs0 pid 1317)
[37258.615774] amdgpu 0000:06:00.0:   in page starting at address 0x0000800107803000 from 27
[37258.615777] amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[37268.712339] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37268.712387] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37268.712389] [drm] GPU recovery disabled.
[37278.952537] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37278.952624] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37278.952628] [drm] GPU recovery disabled.
[37289.192390] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37289.192478] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37289.192481] [drm] GPU recovery disabled.
[37299.432447] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37299.432534] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37299.432538] [drm] GPU recovery disabled.
[37309.676431] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37309.676518] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37309.676522] [drm] GPU recovery disabled.
[37319.912444] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37319.912536] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37319.912541] [drm] GPU recovery disabled.
[37330.156619] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37330.156706] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37330.156710] [drm] GPU recovery disabled.
[37340.392424] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37340.392511] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37340.392515] [drm] GPU recovery disabled.
[37350.632424] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37350.632511] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37350.632514] [drm] GPU recovery disabled.
[37360.872417] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37360.872508] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37360.872511] [drm] GPU recovery disabled.
[37371.112436] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37371.112523] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37371.112527] [drm] GPU recovery disabled.
[37381.352427] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37381.352514] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37381.352517] [drm] GPU recovery disabled.
[37391.592410] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37391.592497] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37391.592500] [drm] GPU recovery disabled.
[37401.836426] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37401.836513] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37401.836517] [drm] GPU recovery disabled.
[37412.072433] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37412.072520] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37412.072524] [drm] GPU recovery disabled.
[37422.312442] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37422.312528] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37422.312532] [drm] GPU recovery disabled.
[37432.552428] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37432.552515] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37432.552519] [drm] GPU recovery disabled.
[37442.792418] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37442.792506] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37442.792510] [drm] GPU recovery disabled.
[37453.032397] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37453.032483] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37453.032487] [drm] GPU recovery disabled.
[37463.272534] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37463.272621] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37463.272624] [drm] GPU recovery disabled.
[37473.512589] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37473.512676] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37473.512680] [drm] GPU recovery disabled.
[37483.752954] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37483.753041] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37483.753044] [drm] GPU recovery disabled.
[37493.992566] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=602475, emitted seq=602478
[37493.992654] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1287 thread Xorg:cs0 pid 1317
[37493.992657] [drm] GPU recovery disabled.

During this time the laptop continues to operate (plays music and can SSH in), however the display and any input (keyboard / mouse) do not respond. The caps lock light for example does not toggle. The only way to recover is a force reboot by holding the power button.

I'm unable to provide any steps on how to re-create as the issue happens at completely random times when performing different tasks or when leaving the machine idle. 

System specs:
Lenovo ThinkPad A485
AMD Ryzen 7 PRO 2700U with Radeon Vega Mobile Gfx
Linux Mint 19.1
Kernel 5.0.1 (installed via ukuu)
Comment 6 Dev Bazilio 2019-04-01 18:20:39 UTC
tried linux-amd-staging-drm-next-git-5.1.811103.2acb851ad43b and dmes is still has a lot of warnings. Tested also youtube in chrome with UVD, got a minor freeze and long freeze ~30sec of system

Apr 01 21:01:03 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring uvd_enc0 test failed (-110)
Apr 01 21:01:03 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <uvd_v6_0> failed -110
Apr 01 21:01:03 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).


Apr 01 20:26:59 kernel: [drm] amdgpu kernel modesetting enabled.
Apr 01 20:26:59 kernel: vga_switcheroo: detected switching method \_SB_.PCI0.VGA_.ATPX handle
Apr 01 20:26:59 kernel: [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x1025:0x1201 0xCA).
Apr 01 20:26:59 kernel: [drm] register mmio base: 0xD1500000
Apr 01 20:26:59 kernel: [drm] register mmio size: 262144
Apr 01 20:26:59 kernel: [drm] add ip block number 0 <vi_common>
Apr 01 20:26:59 kernel: [drm] add ip block number 1 <gmc_v8_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 2 <cz_ih>
Apr 01 20:26:59 kernel: [drm] add ip block number 3 <gfx_v8_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 4 <sdma_v3_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 5 <powerplay>
Apr 01 20:26:59 kernel: [drm] add ip block number 6 <dm>
Apr 01 20:26:59 kernel: [drm] add ip block number 7 <uvd_v6_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 8 <vce_v3_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 9 <acp_ip>
Apr 01 20:26:59 kernel: [drm] UVD is enabled in physical mode
Apr 01 20:26:59 kernel: [drm] VCE enabled in physical mode
Apr 01 20:26:59 kernel: ATOM BIOS: 113-C91400-007
Apr 01 20:26:59 kernel: [drm] RAS INFO: ras initialized successfully, hardware ability[0] ras_mask[0]
Apr 01 20:26:59 kernel: [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
Apr 01 20:26:59 kernel: amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
Apr 01 20:26:59 kernel: amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
Apr 01 20:26:59 kernel: [drm] Detected VRAM RAM=512M, BAR=512M
Apr 01 20:26:59 kernel: [drm] RAM width 64bits UNKNOWN
Apr 01 20:26:59 kernel: [TTM] Zone  kernel: Available graphics memory: 3804974 KiB
Apr 01 20:26:59 kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 KiB
Apr 01 20:26:59 kernel: [TTM] Initializing pool allocator
Apr 01 20:26:59 kernel: [TTM] Initializing DMA pool allocator
Apr 01 20:26:59 kernel: [drm] amdgpu: 512M of VRAM memory ready
Apr 01 20:26:59 kernel: [drm] amdgpu: 3072M of GTT memory ready.
Apr 01 20:26:59 kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144
Apr 01 20:26:59 kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F4007E9000).
Apr 01 20:26:59 kernel: [drm] Found UVD firmware Version: 1.91 Family ID: 11
Apr 01 20:26:59 kernel: [drm] UVD ENC is disabled
Apr 01 20:26:59 kernel: [drm] Found VCE firmware Version: 52.4 Binary ID: 3
Apr 01 20:26:59 kernel: smu version 27.17.00
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Engine clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         300000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         480000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         533340
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         576000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         626090
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         685720
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         720000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         757900
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    engine_max_clock: 75790
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    memory_max_clock: 93300
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    level           : 8
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Display clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         300000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         400000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         496560
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         626090
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         685720
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         757900
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         800000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         847060
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    engine_max_clock: 75790
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    memory_max_clock: 93300
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    level           : 8
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Memory clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         667000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         933000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    engine_max_clock: 75790
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    memory_max_clock: 93300
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    level           : 8
Apr 01 20:26:59 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
Apr 01 20:26:59 kernel: [drm] Display Core initialized with v3.2.24!
Apr 01 20:26:59 kernel: [drm] SADs count is: -2, don't need to read it
Apr 01 20:26:59 kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Apr 01 20:26:59 kernel: [drm] Driver supports precise vblank timestamp query.

Apr 01 20:26:59 kernel: [drm] UVD initialized successfully.
Apr 01 20:26:59 kernel: [drm] VCE initialized successfully.
Apr 01 20:26:59 kernel: kfd kfd: Allocated 3969056 bytes on gart
Apr 01 20:26:59 kernel: Topology: Add APU node [0x9874:0x1002]
Apr 01 20:26:59 kernel: kfd kfd: added device 1002:9874
Apr 01 20:26:59 kernel: [drm] fb mappable at 0x21FDCD000
Apr 01 20:26:59 kernel: [drm] vram apper at 0x21F000000
Apr 01 20:26:59 kernel: [drm] size 8294400
Apr 01 20:26:59 kernel: [drm] fb depth is 24
Apr 01 20:26:59 kernel: [drm]    pitch is 7680
Apr 01 20:26:59 kernel: fbcon: amdgpudrmfb (fb0) is primary device
Apr 01 20:26:59 kernel: Console: switching to colour frame buffer device 240x67
Apr 01 20:26:59 kernel: amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device
Apr 01 20:26:59 kernel: [drm] Initialized amdgpu 3.31.0 20150101 for 0000:00:01.0 on minor 0
Apr 01 20:26:59 kernel: amdgpu 0000:03:00.0: enabling device (0002 -> 0003)
Apr 01 20:26:59 kernel: [drm] initializing kernel modesetting (POLARIS12 0x1002:0x699F 0x1025:0x1210 0xC3).
Apr 01 20:26:59 kernel: [drm] register mmio base: 0xD1200000
Apr 01 20:26:59 kernel: [drm] register mmio size: 262144
Apr 01 20:26:59 kernel: [drm] add ip block number 0 <vi_common>
Apr 01 20:26:59 kernel: [drm] add ip block number 1 <gmc_v8_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 2 <tonga_ih>
Apr 01 20:26:59 kernel: [drm] add ip block number 3 <gfx_v8_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 4 <sdma_v3_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 5 <powerplay>
Apr 01 20:26:59 kernel: [drm] add ip block number 6 <dm>
Apr 01 20:26:59 kernel: [drm] add ip block number 7 <uvd_v6_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 8 <vce_v3_0>
Apr 01 20:26:59 kernel: kfd kfd: skipped device 1002:699f, PCI rejects atomics
Apr 01 20:26:59 kernel: [drm] UVD is enabled in VM mode
Apr 01 20:26:59 kernel: [drm] UVD ENC is enabled in VM mode
Apr 01 20:26:59 kernel: [drm] VCE enabled in VM mode
Apr 01 20:26:59 kernel: vga_switcheroo: enabled
Apr 01 20:26:59 kernel: ATOM BIOS: SWBRT23054.001
Apr 01 20:26:59 kernel: [drm] GPU posting now...
Apr 01 20:26:59 kernel: [drm] RAS INFO: ras initialized successfully, hardware ability[0] ras_mask[0]
Apr 01 20:26:59 kernel: [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
Apr 01 20:26:59 kernel: amdgpu 0000:03:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
Apr 01 20:26:59 kernel: amdgpu 0000:03:00.0: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
Apr 01 20:26:59 kernel: [drm] Detected VRAM RAM=2048M, BAR=256M
Apr 01 20:26:59 kernel: [drm] RAM width 128bits GDDR5
Apr 01 20:26:59 kernel: [drm] amdgpu: 2048M of VRAM memory ready
Apr 01 20:26:59 kernel: [drm] amdgpu: 3072M of GTT memory ready.
Apr 01 20:26:59 kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536
Apr 01 20:26:59 kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Apr 01 20:26:59 kernel: [drm] Chained IB support enabled!
Apr 01 20:26:59 kernel: [drm] Found UVD firmware Version: 1.130 Family ID: 16
Apr 01 20:26:59 kernel: [drm] Found VCE firmware Version: 53.26 Binary ID: 3
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Engine clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         214000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         551000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         734000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         921000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         980000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         1046000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    engine_max_clock: 104600
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    memory_max_clock: 125000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    level           : 8
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Memory clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         300000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         625000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:         1250000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    engine_max_clock: 104600
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    memory_max_clock: 125000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB:    level           : 8
Apr 01 20:26:59 kernel: [drm] Display Core initialized with v3.2.24!
Apr 01 20:26:59 kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Apr 01 20:26:59 kernel: [drm] Driver supports precise vblank timestamp query.
Apr 01 20:26:59 kernel: [drm] UVD and UVD ENC initialized successfully.
Apr 01 20:26:59 kernel: [drm] VCE initialized successfully.
Apr 01 20:26:59 kernel: [drm] Initialized amdgpu 3.31.0 20150101 for 0000:03:00.0 on minor 1
Apr 01 20:26:59 kernel: amdgpu: [powerplay] 
                                failed to send message 15b ret is 0 
Apr 01 20:26:59 kernel: amdgpu: [powerplay] 
                                last message was failed ret is 0
Apr 01 20:26:59 kernel: amdgpu: [powerplay] 
                                failed to send message 15a ret is 0 
Apr 01 20:26:59 kernel: [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110).
Apr 01 20:26:59 kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Apr 01 20:26:59 kernel: amdgpu: [powerplay] 
                                last message was failed ret is 0
Apr 01 20:26:59 kernel: amdgpu: [powerplay] 
                                failed to send message 155 ret is 0 
Apr 01 20:26:59 kernel: amdgpu: [powerplay] 
                                last message was failed ret is 0
Apr 01 20:26:59 kernel: amdgpu: [powerplay] 
                                failed to send message 15b ret is 0
Apr 01 20:27:48 kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Apr 01 20:27:48 kernel: amdgpu: [powerplay] 
                                failed to send message 154 ret is 0 
Apr 01 20:27:49 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring uvd_enc0 test failed (-110)
Apr 01 20:27:49 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <uvd_v6_0> failed -110
Apr 01 20:27:49 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
Apr 01 20:27:50 kernel: amdgpu: [powerplay]
Apr 01 20:28:30 kernel: amdgpu: [powerplay] 
                                failed to send message 261 ret is 0 
Apr 01 20:28:31 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:31 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:32 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:32 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:33 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:33 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:34 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:34 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:35 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:35 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:36 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:36 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:37 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:37 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:38 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:39 kernel: amdgpu: [powerplay] 

Apr 01 20:29:12 kernel: amdgpu: [powerplay] 
                                failed to send message 154 ret is 0 
Apr 01 20:29:13 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring uvd_enc0 test failed (-110)
Apr 01 20:29:13 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <uvd_v6_0> failed -110
Apr 01 20:29:13 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).

Apr 01 20:30:06 kernel: amdgpu: [powerplay] 
                                last message was failed ret is 0
Apr 01 20:30:06 kernel: amdgpu: [powerplay] 
                                failed to send message 135 ret is 0 
Apr 01 20:30:07 kernel: amdgpu: [powerplay] 
                                last message was failed ret is 0
Apr 01 20:30:07 kernel: amdgpu: [powerplay] 
                                failed to send message 190 ret is 0 
Apr 01 20:30:08 kernel: amdgpu: [powerplay] 
                                last message was failed ret is 0
Apr 01 20:30:08 kernel: amdgpu: [powerplay] 
                                failed to send message 63 ret is 0 
Apr 01 20:30:09 kernel: amdgpu: [powerplay] 
                                last message was failed ret is 0
Apr 01 20:30:09 kernel: amdgpu: [powerplay] 
                                failed to send message 84 ret is 0 
Apr 01 20:30:09 kernel: amdgpu 0000:03:00.0: GPU pci config reset
Apr 01 20:34:17 kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Apr 01 20:34:18 kernel: amdgpu: [powerplay] 
                                failed to send message 154 ret is 0 
Apr 01 20:34:18 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring uvd_enc0 test failed (-110)
Apr 01 20:34:18 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <uvd_v6_0> failed -110
Apr 01 20:34:18 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
Comment 7 Dev Bazilio 2019-04-01 18:44:22 UTC
(In reply to Alex Deucher from comment #4)
> Can you bisect?

Unfortunately this is not possible as all latest kernels are now shipped with Display Core enabled by default and as I told 4.14 vanilla kernel works like a charm on same HW and with same mesa libs - no lags, no stucks or freezes and no warnings like listed above. So it's no sense to do "git bisect" as it's not a single commit which works incorrectly with GPU. DC - this a completely new functionality which replaces old amdgpu code
Comment 8 jens harms 2019-08-20 15:06:55 UTC
Hi, i have a very similar problem. My system is working with 4.15 and with 5.1.16 but not with other 5.x kernels:

The System does not boot with 5.x kernels. With 5.1.16 the gui system freezes sometimes but sshd and mouse is still working. 


CPU: Ryzen 5 2400g, BOARD: AORUS B450 I PRO WIFI, X Server 1.19.6

Kernel 5.0.x not working (blank screen after boot)
Kernel 5.2.x ( x <= 9 ) is not working (blank screen after boot)

but Kernel 5.1.16 is working (mostly)!


Error LOG with 5.1.16:
[Mi Aug 14 14:22:21 2019] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Mi Aug 14 14:22:21 2019] amdgpu 0000:09:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32768, for process Xorg pid 1848 thread Xorg:cs0 pid 1849)
[Mi Aug 14 14:22:21 2019] amdgpu 0000:09:00.0:   in page starting at address 0x000080010c205000 from 27
[Mi Aug 14 14:22:21 2019] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Mi Aug 14 14:22:31 2019] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=840738, emitted seq=840740
[Mi Aug 14 14:22:31 2019] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1848 thread Xorg:cs0 pid 1849
[Mi Aug 14 14:22:31 2019] [drm] GPU recovery disabled.
Comment 9 Ungureanu Alexandru 2019-09-11 08:36:57 UTC
Just got something similar while playing Left 4 Dead. The system simply froze with altered colors on the screen and the sound just looping over the last second or so. Cannot confirm SSH access.


journalctl -b -1 ends with


[drm:gfx_v8_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=2225992, emitted seq=2225993
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process hl2_linux pid 12532 thread hl2_


OS: Ubuntu 19.04 on 
Kernel: 5.0.0-27-generic
GPU: Radeon RX580
CPU: Ryzen 5 1600x

Thanks!
Comment 10 Dev Bazilio 2019-09-20 11:37:07 UTC
(In reply to Ungureanu Alexandru from comment #9)
> Just got something similar while playing Left 4 Dead. The system simply
> froze with altered colors on the screen and the sound just looping over the
> last second or so. Cannot confirm SSH access.

> Kernel: 5.0.0-27-generic
> GPU: Radeon RX580
> CPU: Ryzen 5 1600x

5.0 is very outdated kernel, use latest from kernel.org

as for me all works perfectly in 5.3 (Chip polaris RX540)
finally I have no more any errors like these ones:
- ERROR* resume of IP block <uvd_v6_0> failed -110
- [drm] Fence fallback timer expired on ring sdma0
- last message was failed ret is **
- [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq...
- IP block:sdma_v3_0 is hung!
- Timeout, but no hardware hang detected.

Tested on youtube with HW accelerated video and in several games
Thank you guys from AMD a lot, I had to wait 1y+ to get these bugs fixed
Comment 11 lekto 2019-10-02 10:39:30 UTC
Same problem here. It happens when I run looking-glass [1], but not everytime. I tied downgrading my kernel from 5.3.1 to 5.2.11 (I'm pretty sure it worked then), downgrading mesa from 19.2.0 to 19.1.7 (I'm sure it worked with 19.2.0-rc) and downgrading my firmware to 2019-09-23 (oldest in repo).

When it happens looking glass starts blinking and sometimes my other monitor stuck that I can only move cursor on it.

Spec:
Gentoo ~amd64
Ryzen 1600 (other have Ryzen too, coincidence?)
Linux GPU: R7 240 (with radeon driver)
Windows GPU: RX580
ASRock X370 Gaming X


[1] https://looking-glass.hostfission.com/
Comment 12 Matthias Heinz 2019-10-11 22:00:39 UTC
Hi,

I think I have the same bug and opened https://bugzilla.kernel.org/show_bug.cgi?id=204683.

At first it looked a bit different, because in newer kernels the error message has changed. But as you can see I did some testing and this seems to go way back. Sadly I couldn't test a 4.18 kernel.

Can somebody mark my report as duplicate? Because I think it is.

And Would some more debug info help?
Comment 13 Matthias Heinz 2019-10-14 17:18:59 UTC
*** Bug 204683 has been marked as a duplicate of this bug. ***
Comment 14 Konstantin Pereiaslov 2019-10-24 16:39:38 UTC
Also experiencing this with Radeon RX 5700 XT and amdgpu  19.1.0+git1910111930.b467d2~oibaf~b 

Didn't have any heavy load for the GPU to do. 

First I had some artifacts appeared on Plasma Hard Disk Monitor widget and CPU Load Widget (here is a screenshot: https://i.perk11.info/20191024_193152_kernel.png) while PC was idle and screen was locked, but everything else continued to work fine. 

I checked the logs for the period when this could've happened, but the only logs from that period are from KScreen that start like this:

Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Output:  88
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Property:  EDID
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         State (newValue, Deleted):  1
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Output:  88
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Property:  EDID
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         State (newValue, Deleted):  1
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper: RRNotify_OutputChange
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Output:  88
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         CRTC:  81
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Mode:  97
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Connection:  "Disconnected"
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Subpixel Order:  0
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper: RRScreenChangeNotify
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Window: 18874373
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Root: 1744
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Size ID: 65535
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Size:  7280 1440
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         SizeMM:  1926 381
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper: RRNotify_OutputChange
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Output:  88
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         CRTC:  81
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Mode:  97
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Connection:  "Disconnected"
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xcb.helper:         Subpixel Order:  0
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xrandr: XRandROutput 88 update
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          m_connected: 0
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          m_crtc XRandRCrtc(0x5655577da9f0)
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          CRTC: 81
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          MODE: 97
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          Connection: 1
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          Primary: false
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xrandr: Output 88 : connected = false , enabled = true
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]: kscreen.xrandr: XRandROutput 88 update
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          m_connected: 1
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          m_crtc XRandRCrtc(0x5655577da9f0)
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          CRTC: 81
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          MODE: 97
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          Connection: 1
Oct 24 16:34:58 perk11-home org.kde.KScreen[25804]:          Primary: false



90 minutes later, the system became unresponsive while I was typing a message in Skype, but the audio I had playing in Audacity continued to play and the cron jobs continued running normally for a few minutes while I was trying to get the system unstuck without rebooting it which I couldn't.

Here are the errors:

Oct 24 19:04:10 perk11-home kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
Oct 24 19:04:10 perk11-home kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
Oct 24 19:04:15 perk11-home kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!




Oct 24 19:04:10 perk11-home kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
Oct 24 19:04:10 perk11-home kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
Oct 24 19:04:15 perk11-home kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
Oct 24 19:04:15 perk11-home kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=3485981, emitted seq=3485983
Oct 24 19:04:15 perk11-home kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 2469 thread Xorg:cs0 pid 2491
Oct 24 19:04:15 perk11-home kernel: [drm] GPU recovery disabled.
Comment 15 Konstantin Pereiaslov 2019-10-24 16:40:26 UTC
My kernel version is 5.3.7-050307-generic running KDE Neon User edition with latest updates.
Comment 16 shallowaloe 2019-10-27 18:44:36 UTC
Created attachment 285665 [details]
5 second video clip that triggers a crash

Hi,

I think I'm having the same problem as you guys.  I run a mythbackend where I record cable television and those recordings often crash my system when hardware decoding is enabled.  Usually it's just the screen that freezes and I can still ssh to it.  

Kernel 5.1.6 was an exception for me too, with that kernel I'm able to restart the display manager and recover without having to reboot.

Attached is a short video that crashes my system.  I can trigger the alert by running:

mpv --vo=vaapi out.ts

I'm wondering if it crashes your systems too and if it's related.
Comment 17 jmstylr 2019-11-10 07:11:29 UTC
(In reply to shallowaloe from comment #16)
> Created attachment 285665 [details]
> 5 second video clip that triggers a crash
> 
> Hi,
> 
> I think I'm having the same problem as you guys.  I run a mythbackend where
> I record cable television and those recordings often crash my system when
> hardware decoding is enabled.  Usually it's just the screen that freezes and
> I can still ssh to it.  
> 
> Kernel 5.1.6 was an exception for me too, with that kernel I'm able to
> restart the display manager and recover without having to reboot.
> 
> Attached is a short video that crashes my system.  I can trigger the alert
> by running:
> 
> mpv --vo=vaapi out.ts
> 
> I'm wondering if it crashes your systems too and if it's related.


Just to add a data point, I tried running `mpv --vo=vaapi out.ts` against your file, and while it crashed the application, it did not freeze the system. 

My hardware is a Ryzen 3700X with a Radeon RX 5700, running Ubuntu 19.10 with default kernel (5.3.0-19-generic).

The command did result in the following lines in /var/log/syslog repeated every 5 seconds:

Nov 10 07:04:23 redacted kernel: [ 2266.802162] gmc_v10_0_process_interrupt: 23900 callbacks suppressed
Nov 10 07:04:23 redacted kernel: [ 2266.802166] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802170] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802171] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.802176] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802178] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802179] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Nov 10 07:04:23 redacted kernel: [ 2266.802566] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802568] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802569] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.802573] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802575] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802576] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Nov 10 07:04:23 redacted kernel: [ 2266.802984] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802985] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802987] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.802993] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802994] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802995] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Nov 10 07:04:23 redacted kernel: [ 2266.803403] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.803404] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.803406] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.803410] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.803411] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.803412] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Nov 10 07:04:23 redacted kernel: [ 2266.803822] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.803824] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.803825] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.803831] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.803833] amdgpu 0000:0b:00.0:   at page 0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.803834] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Comment 18 Matthias Heinz 2019-11-25 09:43:45 UTC
Hi,

I recently built a 5.4.0-rc7 from drm-next (my HEAD was 17eee668b3cad423a47c090fe2275733c55db910) and also updated Mesa to 19.3.0-RC1.

Since then I didn't get any crashes. I have tested this for a few hours now, but it's entirely possible that I just didn't run into the bug for some reason, although it usually appeared after half an hour.

If possible please try this setup and see if it is fixed.
Comment 19 j.cordoba 2019-12-03 15:53:49 UTC
Hi,

This issue is still present in the latest kernels:

5.4.1, 5.4, 5.3.14

Last usable kernel for me is 4.20.17

System Specs

- Gigabyte b450-ds3h
- Ryzen 5 3400G (with RX Vega 11)
- Mesa 19.1.2 - padoka PPA (Stable)
- Ubuntu 18.04.3 LTS
Comment 20 Matthias Heinz 2019-12-03 16:07:15 UTC
Dear j.cordoba,

is it possible that you try to build 5.4.0-rc7 from drm-next and give it a test as I mentioned in Comment 18?

I'm running on this for some time now and the bug should have appeared by now, so I'm getting more confident that it is fixed.

Best regards
Matthias
Comment 21 Łukasz Żarnowiecki 2019-12-03 21:34:03 UTC
Same is happening to me on 5.4.1.  No issue with 4.9.

[   44.172714] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[   49.292694] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
[   58.469316] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[   63.586055] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
[  156.606591] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
Comment 22 Pierre-Eric Pelloux-Prayer 2019-12-04 09:54:47 UTC
(In reply to shallowaloe from comment #16)
> Created attachment 285665 [details]
> 5 second video clip that triggers a crash
> 
> Hi,
> 
> I think I'm having the same problem as you guys.  I run a mythbackend where
> I record cable television and those recordings often crash my system when
> hardware decoding is enabled.  Usually it's just the screen that freezes and
> I can still ssh to it.  
> 
> Kernel 5.1.6 was an exception for me too, with that kernel I'm able to
> restart the display manager and recover without having to reboot.
> 
> Attached is a short video that crashes my system.  I can trigger the alert
> by running:
> 
> mpv --vo=vaapi out.ts
> 
> I'm wondering if it crashes your systems too and if it's related.


This one is probably a Mesa issue, see https://gitlab.freedesktop.org/mesa/mesa/issues/2177

What Mesa version are you using?
Comment 23 shallowaloe 2019-12-08 17:32:49 UTC
Created attachment 286227 [details]
attachment-25111-0.html

Thanks for the link to the bug. I'm running an ubuntu based system and am
using the oibaf ppa.  The current version is 20.0.



On Wed, Dec 4, 2019 at 1:54 AM <bugzilla-daemon@bugzilla.kernel.org> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=201957
>
> Pierre-Eric Pelloux-Prayer (pierre-eric.pelloux-prayer@amd.com) changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|
> |pierre-eric.pelloux-prayer@
>                    |                            |amd.com
>
> --- Comment #22 from Pierre-Eric Pelloux-Prayer (
> pierre-eric.pelloux-prayer@amd.com) ---
> (In reply to shallowaloe from comment #16)
> > Created attachment 285665 [details]
> > 5 second video clip that triggers a crash
> >
> > Hi,
> >
> > I think I'm having the same problem as you guys.  I run a mythbackend
> where
> > I record cable television and those recordings often crash my system when
> > hardware decoding is enabled.  Usually it's just the screen that freezes
> and
> > I can still ssh to it.
> >
> > Kernel 5.1.6 was an exception for me too, with that kernel I'm able to
> > restart the display manager and recover without having to reboot.
> >
> > Attached is a short video that crashes my system.  I can trigger the
> alert
> > by running:
> >
> > mpv --vo=vaapi out.ts
> >
> > I'm wondering if it crashes your systems too and if it's related.
>
>
> This one is probably a Mesa issue, see
> https://gitlab.freedesktop.org/mesa/mesa/issues/2177
>
> What Mesa version are you using?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 24 Janpieter Sollie 2020-01-02 08:30:11 UTC
Hi everyone,

I have the same issue with a Fiji Nano GPU: UVD6 and VCE3 timeout in ring buffer test @ boot with the AMDGPU driver. Other rings seem to work correctly.
To make sure the hardware functions like it should, and it's not a HW error, where (in the amdgpu driver) can I increase the timeout value?
Comment 25 Janpieter Sollie 2020-01-02 09:11:40 UTC
Created attachment 286575 [details]
kernel config 5.4.7 Fiji

Some additional info for my case:
- Running kernel 5.4.7 (vanilla), firmware 20191108 on gentoo
- Dmesg | grep -E "(drm)|(amdgpu)":
[    3.930023] [drm] amdgpu kernel modesetting enabled.
[    3.930217] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff
[    3.930219] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xf0000000 -> 0xf01fffff
[    3.930221] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xfce00000 -> 0xfce3ffff
[    3.930224] fb0: switching to amdgpudrmfb from EFI VGA
[    3.930475] [drm] initializing kernel modesetting (FIJI 0x1002:0x7300 0x1002:0x0B36 0xCA).
[    3.930486] [drm] register mmio base: 0xFCE00000
[    3.930486] [drm] register mmio size: 262144
[    3.930495] [drm] add ip block number 0 <vi_common>
[    3.930495] [drm] add ip block number 1 <gmc_v8_0>
[    3.930496] [drm] add ip block number 2 <tonga_ih>
[    3.930497] [drm] add ip block number 3 <gfx_v8_0>
[    3.930498] [drm] add ip block number 4 <sdma_v3_0>
[    3.930498] [drm] add ip block number 5 <powerplay>
[    3.930499] [drm] add ip block number 6 <dm>
[    3.930500] [drm] add ip block number 7 <uvd_v6_0>
[    3.930500] [drm] add ip block number 8 <vce_v3_0>
[    3.930715] [drm] UVD is enabled in physical mode
[    3.930715] [drm] VCE enabled in physical mode
[    3.930743] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
[    3.930751] amdgpu 0000:0a:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
[    3.930753] amdgpu 0000:0a:00.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
[    3.930758] [drm] Detected VRAM RAM=4096M, BAR=256M
[    3.930759] [drm] RAM width 512bits HBM
[    3.930838] [drm] amdgpu: 4096M of VRAM memory ready
[    3.930841] [drm] amdgpu: 4096M of GTT memory ready.
[    3.930860] [drm] GART: num cpu pages 262144, num gpu pages 262144
[    3.930928] [drm] PCIE GART of 1024M enabled (table at 0x000000F4001D5000).
[    3.934174] [drm] Chained IB support enabled!
[    3.940198] amdgpu: [powerplay] hwmgr_sw_init smu backed is fiji_smu
[    3.941748] [drm] Found UVD firmware Version: 1.91 Family ID: 12
[    3.941752] [drm] UVD ENC is disabled
[    3.943542] [drm] Found VCE firmware Version: 55.2 Binary ID: 3
[    4.009146] [drm] dce110_link_encoder_construct: Failed to get encoder_cap_info from VBIOS with error code 4!
[    4.040084] [drm] Display Core initialized with v3.2.48!
[    4.040542] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    4.040543] [drm] Driver supports precise vblank timestamp query.
[    4.067774] [drm] UVD initialized successfully.
[    4.168780] [drm] VCE initialized successfully.
[    4.170163] [drm] Cannot find any crtc or sizes
[    4.171948] [drm] Initialized amdgpu 3.35.0 20150101 for 0000:0a:00.0 on minor 0
[    7.280062] amdgpu 0000:0a:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on uvd (-110).
[    8.400365] amdgpu 0000:0a:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on vce0 (-110).
[    8.400370] [drm:process_one_work] *ERROR* ib ring test failed (-110).
Comment 26 F. Delente 2020-01-19 17:03:37 UTC
Hello, I have the same problem on a Huawei Matebook D lapop, processor is an AMD Ryzen 5 with an integrated Radeon Vega Mobile GPU.

I use Fedora 31. The problem appeared when upgrading from then 5.3.16 kernel to the 5.4.6 kernel. Reverting to 5.3.16 solved the issue.

At some moments the UI (XFCE) freezes for about 5 seconds; I can move the mouse cursor but I can't get any keyboard input (not in X, not by switching console). Each time the freeze occurs dmesg shows the messages

[   45.530374] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[   50.139408] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered

I include /proc/cpuinfo and lspci outputs.
Comment 27 F. Delente 2020-01-19 17:04:19 UTC
Created attachment 286899 [details]
/proc/cpuinfo
Comment 28 F. Delente 2020-01-19 17:04:47 UTC
Created attachment 286901 [details]
lspci output
Comment 29 Matthias Heinz 2020-01-19 17:13:00 UTC
Hi. This bug is already reported here by me https://gitlab.freedesktop.org/drm/amd/issues/953

If possible try a 5.5-rc kernel and see if it's fixed there. It's fixed - at least for me - in the drm-tree.

Best regards
Matthias

Note You need to log in before you can comment on or make changes to this bug.