[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 Martin Peres changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #90 from jeroenimo --- I managed to run glmark2 without crashing the system with By running the card manual at lowest frequency from root shell: echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level echo 0 >

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #89 from jeroenimo --- I found a way to crash the system with glmark2 It almost instantly crashes it. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #88 from jeroenimo --- Found this thread while googling the error from the log. AMD Ryzen 3600 Asrock B350 motherboard ASrock RX560 Radeon GPU Ubuntu and Xubuntu 18.04 and 19.04 both lockups so not useable, after login almost

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #86 from Paul Ezvan --- I was also impacted by this bug (amdgpu hangs on random conditions with similar messages as the one exposed) with any kernel/mesa version combination other than the ones on Debian Stretch (any other distro or

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #85 from dwagner --- (In reply to Wilko Bartels from comment #84) > nevermind. it crashed on 60hz as well (once) yesterday It sure does. This bug is now about two years old, during which amdgpu has never been stable, got worse, and

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #84 from Wilko Bartels --- (In reply to Wilko Bartels from comment #83) > (In reply to Jaap Buurman from comment #81) > > issue seems to be using a setup that requires higher engine clocks in idle > > AFAIK. Either high refresh

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #83 from Wilko Bartels --- (In reply to Jaap Buurman from comment #81) > issue seems to be using a setup that requires higher engine clocks in idle > AFAIK. Either high refresh displays, or in my case, multiple monitors. Could >

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #82 from Matt Coffin --- I am also experiencing this issue. * Kernel: 5.1.3-arch2-1-ARCH * LLVM 8.0.0 * AMDVLK (dev branch pulled 20190602) * Mesa 19.0.4 * Card: XFX Radeon RX 590 I've seen this error, bug 105733, bug 105152, bug

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #81 from Jaap Buurman --- (In reply to Alex Deucher from comment #14) > (In reply to dwagner from comment #13) > > > > Much lower shader clocks are used only if I lower the refresh rate of the > > screen. Is there a reason why the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #80 from dwagner --- (In reply to Jaap Buurman from comment #79) > I am also running into the same issue. I have two questions that might help > tracking down why we are having issues, but not all people that are running > a Vega

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #79 from Jaap Buurman --- I am also running into the same issue. I have two questions that might help tracking down why we are having issues, but not all people that are running a Vega graphics card. 1) What is the output of the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #78 from Mauro Gaspari --- Hi, I am affected by similar issues too using AMDGPU drivers on linux, and I have opened another bug, before finding this. You can have a look at my findings and the workarounds I am applying. So far I had

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #77 from dwagner --- Since another month has passed: I can still reproduce the crash with today's git head of amd-staging-drm-next (and an up-to-date Arch Linux) within minutes by replaying a video at 3 fps. Additional new bonus

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #76 from dwagner --- Just for the record, since another month has passed: I can still reproduce the crash with today's git head of amd-staging-drm-next within minutes. As a bonus bug, with today's git head I also get unexplainable

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #75 from dwagner --- Audio is unrelated to this bug. In my reproduction scripts, I do not output any audio at all. The video-at-3-fps replay that I use for reproduction seems to just trigger a certain pattern of the memory- and

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #74 from fin4...@hotmail.com --- The Firefox browser requires the pulseaudio driver. Use the Alsa audio and the chrome/chromium browser. Disable hardware acceleration in browser settings. -- You are receiving this mail because: You

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #73 from Jānis Jansons --- Someone suggested I buy Ryzen 2400G APU, but almost every time some network lag happens while watching TV stream through Kodi and FPS of that video goes to 0, display just freezes and you have to power

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #72 from dwagner --- Just for the record, since another month has passed: I can still reproduce the crash with today's git head of amd-staging-drm-next within minutes. (Also using the very latest firmware files from

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #71 from dwagner --- Created attachment 142484 --> https://bugs.freedesktop.org/attachment.cgi?id=142484=edit gpu_debug4_output.txt.gz -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #70 from dwagner --- Created attachment 142483 --> https://bugs.freedesktop.org/attachment.cgi?id=142483=edit test script -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #69 from dwagner --- As promised in above comment, today I ran my debug script "gpu_debug4.sh" to obtain the diagnostic output after the crash as requested above. This output is in attached "gpu_debug4_output.txt". Since the trace

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #68 from dwagner --- Tested today's current amd-staging-drm-next git head, to see if there has been any improvement over the last two months. The bad news: The 3-fps-video-replay test still crashes the driver reproducably after few

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #67 from Roshless --- Tried on 4.19-rc5, still crashes for me after about 2-3 days (of 6-12h use) -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #66 from Anthony Ruhier --- (In reply to dwagner from comment #65) > (In reply to Anthony Ruhier from comment #63) > > FYI, I also had this bug under linux 4.17 and 4.18, but it seems to have > > been fixed in 4.19-rc3. The

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #65 from dwagner --- (In reply to Anthony Ruhier from comment #63) > FYI, I also had this bug under linux 4.17 and 4.18, but it seems to have > been fixed in 4.19-rc3. The suspend/hibernate issue has also been fixed. Unluckily, I

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #63 from Anthony Ruhier --- FYI, I also had this bug under linux 4.17 and 4.18, but it seems to have been fixed in 4.19-rc3. The suspend/hibernate issue has also been fixed. -- You are receiving this mail because: You are the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #64 from Anthony Ruhier --- (In reply to Anthony Ruhier from comment #63) > FYI, I also had this bug under linux 4.17 and 4.18, but it seems to have > been fixed in 4.19-rc3. The suspend/hibernate issue has also been fixed. Forgot

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #62 from dwagner --- Created attachment 141243 --> https://bugs.freedesktop.org/attachment.cgi?id=141243=edit crash trace with amdgpu.vm_update_mode=3 -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #61 from dwagner --- > Please use amdgpu.vm_update_mode=3 to get back to VM_FAULTs issue. The "good" news is that reproduction of the crashes with 3-fps-video-replay is very quick when using amdgpu.vm_update_mode=3. But the bad

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #60 from Andrey Grodzovsky --- (In reply to dwagner from comment #58) > Here comes another trace log, with your info2.patch applied. > > Something must have changed since the last test, as it took pretty long this > time to

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #59 from dwagner --- Created attachment 141228 --> https://bugs.freedesktop.org/attachment.cgi?id=141228=edit latest crash trace output, without gpu_reset -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #58 from dwagner --- Here comes another trace log, with your info2.patch applied. Something must have changed since the last test, as it took pretty long this time to reproduce the crash. Could that have been caused by

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #57 from Andrey Grodzovsky --- (In reply to dwagner from comment #56) > (In reply to Andrey Grodzovsky from comment #55) > > > In above attached file "xz-compressed output of gpu_debug3.sh" there is > > > umr > > > output at the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #56 from dwagner --- (In reply to Andrey Grodzovsky from comment #55) > > In above attached file "xz-compressed output of gpu_debug3.sh" there is umr > > output at the time of the crash (238 seconds after the reboot): > > > >

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #55 from Andrey Grodzovsky --- (In reply to dwagner from comment #54) > (In reply to Andrey Grodzovsky from comment #53) > > Created attachment 141198 [details] [review] [review] > > add_debug_info2.patch > > > > Try this patch

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #54 from dwagner --- (In reply to Andrey Grodzovsky from comment #53) > Created attachment 141198 [details] [review] > add_debug_info2.patch > > Try this patch instead, i might be missing some prints in the first one. Can try that

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #53 from Andrey Grodzovsky --- Created attachment 141198 --> https://bugs.freedesktop.org/attachment.cgi?id=141198=edit add_debug_info2.patch Try this patch instead, i might be missing some prints in the first one. In the last

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #52 from dwagner --- One other experiment I made: I wrote a script to quickly toggle pp_dpm_mclk and pp_dpm_sclk while playing a 3 fps video with power_dpm_force_performance_level=manual. Could not reproduce the crashes that happen

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 dwagner changed: What|Removed |Added Attachment #141190|0 |1 is obsolete|

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #50 from dwagner --- Created attachment 141190 --> https://bugs.freedesktop.org/attachment.cgi?id=141190=edit dmesg / trace / umr output from gpu_debug3.sh -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #49 from dwagner --- Created attachment 141189 --> https://bugs.freedesktop.org/attachment.cgi?id=141189=edit script used to generate the gpu_debug_3.txt (when executed via ssh -t ...) -- You are receiving this mail because: You

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #48 from dwagner --- (In reply to Andrey Grodzovsky from comment #47) > Created attachment 141174 [details] [review] > add_debug_info.patch > > A am attaching a basic debug patch, please try to apply it. Done. > It should give a

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #47 from Andrey Grodzovsky --- Created attachment 141174 --> https://bugs.freedesktop.org/attachment.cgi?id=141174=edit add_debug_info.patch A am attaching a basic debug patch, please try to apply it. It should give a bit more

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #46 from Andrey Grodzovsky --- Thanks. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #45 from dwagner --- Created attachment 141157 --> https://bugs.freedesktop.org/attachment.cgi?id=141157=edit output of umr command after 3-fps-video test crash -- You are receiving this mail because: You are the assignee for

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #44 from dwagner --- Created attachment 141156 --> https://bugs.freedesktop.org/attachment.cgi?id=141156=edit dmesg from boot to after the 3-fps-video test crash -- You are receiving this mail because: You are the assignee for

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #43 from dwagner --- Created attachment 141155 --> https://bugs.freedesktop.org/attachment.cgi?id=141155=edit trace-cmd induced output during 3-fps-video replay and crash -- You are receiving this mail because: You are the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #42 from dwagner --- Ok, did the proposed debugging session with trace-cmd, with output to a different PC over ssh. Using today's amd-staging-drm-next and btw., Arch updated the Xorg server earlier today. This time it took about 4

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #41 from dwagner --- (In reply to Andrey Grodzovsky from comment #40) > Created attachment 141112 [details] > .config > > I uploaded my .config file - maybe something in your Kconfig flags makes > this happen - you can try and

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #40 from Andrey Grodzovsky --- Created attachment 141112 --> https://bugs.freedesktop.org/attachment.cgi?id=141112=edit .config I uploaded my .config file - maybe something in your Kconfig flags makes this happen - you can try

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #39 from Andrey Grodzovsky --- (In reply to dwagner from comment #37) > In the related bug report > (https://bugs.freedesktop.org/show_bug.cgi?id=107152) I noticed that this > bug can be triggered very reliably and quickly by

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #38 from dwagner --- *** Bug 107152 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #37 from dwagner --- In the related bug report (https://bugs.freedesktop.org/show_bug.cgi?id=107152) I noticed that this bug can be triggered very reliably and quickly by playing a video with a deliberately lowered frame rate: "mpv

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 Roshless changed: What|Removed |Added CC||roshl...@gmail.com --- Comment #36 from

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #35 from Andrey Grodzovsky --- (In reply to dwagner from comment #30) > (In reply to Andrey Grodzovsky from comment #29) > > > (If that is a Mesa issue, no more than user processes / X11 should have > > > crashed - but not the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #34 from dwagner --- (In reply to Doctor from comment #32) > Just cherry picking the code > back to the last 4.16 and no problems Heres the working 4.16 . I chased > this rabbit for awhile and it pops up like the dam wood chuck in

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #33 from Doctor --- I think it may be something as stupid as a var too. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #32 from Doctor --- I ended up due to working on a live dev cd for codexl since all my machines are memory based and use no magnetic media. Just cherry picking the code back to the last 4.16 and no problems Heres the working 4.16 .

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #31 from Doctor --- I got that one too and was able to track the problem down a bit further. Chrome and video with the gpu enabled will blow it up too. Interesting I was able to reproduce it consistantly with my rtl8188eu usb driver

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #30 from dwagner --- (In reply to Andrey Grodzovsky from comment #29) > > (If that is a Mesa issue, no more than user processes / X11 should have > > crashed - but not the kernel amdgpu driver... right?) > > Not exactly, MESA could

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #29 from Andrey Grodzovsky --- (In reply to dwagner from comment #28) > (In reply to Michel Dänzer from comment #27) > > That could be a Mesa issue, anyway it should probably be tracked separately > > from this report. > > Created

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #28 from dwagner --- (In reply to Michel Dänzer from comment #27) > That could be a Mesa issue, anyway it should probably be tracked separately > from this report. Created separate bug report

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #27 from Michel Dänzer --- (In reply to dwagner from comment #26) > Today for the first time I had a sudden "crash while just browsing with > Firefox" [...] That could be a Mesa issue, anyway it should probably be tracked

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #26 from dwagner --- Today for the first time I had a sudden "crash while just browsing with Firefox" while using the amggpu.vm_update_mode=3 parameter with the current-as-of-today amd-staging-drm-next

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #25 from dwagner --- (In reply to Michel Dänzer from comment #24) > Can you try bisecting between 4.13 and 4.17 to find where stability went > downhill for you? A bisect like that is not likely to converge in any reasonable time,

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #24 from Michel Dänzer --- Can you try bisecting between 4.13 and 4.17 to find where stability went downhill for you? -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #23 from dwagner --- Just for the record: At this point, I can say that with amggpu.vm_update_mode=3 4.17.2-ARCH runs at least for hours, not only the minutes it runs without this option before crashing. I cannot, however, say that

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #22 from Andrey Grodzovsky --- (In reply to dwagner from comment #21) > (I meant to write "I guess those register values are NOT retained over a > reboot, right?") Yes, my assumption was that at least some times you still have SSH

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #21 from dwagner --- (I meant to write "I guess those register values are NOT retained over a reboot, right?") -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #20 from dwagner --- (In reply to Andrey Grodzovsky from comment #19) > No need to recompile, just need to see what is the content of SDMA ring > buffer when the hang occurs. > > Clone and build our register analyzer from here - >

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #19 from Andrey Grodzovsky --- Can you use addr2line or gdb with 'list' command to give the line number matching (In reply to dwagner from comment #18) > The good news: So far no crashes during normal uptime with >

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #18 from dwagner --- The good news: So far no crashes during normal uptime with amdgpu.vm_update_mode=3 The bad news: System crashes immediately upon S3 resume (with messages quite different from the ones I saw with earlier

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #17 from Andrey Grodzovsky --- (In reply to Alex Deucher from comment #16) > (In reply to Andrey Grodzovsky from comment #15) > > I think it just means systems with large VRAM so it will require large BAR > > for mapping. But I am

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #16 from Alex Deucher --- (In reply to Andrey Grodzovsky from comment #15) > I think it just means systems with large VRAM so it will require large BAR > for mapping. But I am not sure on that point. That's correct. the updates

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #15 from Andrey Grodzovsky --- (In reply to dwagner from comment #13) > (In reply to Andrey Grodzovsky from comment #12) > > Can you load the kernel with grub command line amdgpu.vm_update_mode=3 to > > force CPU VM update mode and

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #14 from Alex Deucher --- (In reply to dwagner from comment #13) > > Much lower shader clocks are used only if I lower the refresh rate of the > screen. Is there a reason why the shader clocks should stay high even in the > absence

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #13 from dwagner --- (In reply to Andrey Grodzovsky from comment #12) > Can you load the kernel with grub command line amdgpu.vm_update_mode=3 to > force CPU VM update mode and see if this helps ? Sure. Too early yet to say

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #12 from Andrey Grodzovsky --- (In reply to dwagner from comment #2) > Just to mention this once again: These system crashes still occur, and way > too frequently to consider the amdgpu driver stable enough for professional > use.

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #11 from Michel Dänzer --- (In reply to Andrey Grodzovsky from comment #8) > The kernel and MESA seems new enough, LLVM is 6 so maybe you should try 7. LLVM 6 is fine. -- You are receiving this mail because: You are the assignee

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #10 from dwagner --- (In reply to Andrey Grodzovsky from comment #8) > The kernel and MESA seems new enough, LLVM is 6 so maybe you should try 7. LLVM 7 has not been released, and replacing LLVM 6 with the current subversion head

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #9 from Andrey Grodzovsky --- Created attachment 140345 --> https://bugs.freedesktop.org/attachment.cgi?id=140345=edit Deadlock fix -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #8 from Andrey Grodzovsky --- (In reply to dwagner from comment #7) > (In reply to Andrey Grodzovsky from comment #6) > > Verify you are using latest AMD firmware and up to date MESA/LLVM > > Firmware: > > pacman -Q linux-firmware

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #7 from dwagner --- (In reply to Andrey Grodzovsky from comment #6) > Verify you are using latest AMD firmware and up to date MESA/LLVM Firmware: pacman -Q linux-firmware linux-firmware 20180606.d114732-1 ll

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #6 from Andrey Grodzovsky --- Verify you are using latest AMD firmware and up to date MESA/LLVM Firmware here (amdgpu folder) - https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ Andrey -- You are

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #5 from dwagner --- Just for the record: To rule out my personally compiled kernels are somehow "more buggy than what others compile", I tried the current Arch-Linux-supplied Linux 4.17.2-1-ARCH kernel. Survives about 5 minutes of

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #4 from dwagner --- I was asked in https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/1027705-amdgpu-on-linux-4-18-to-offer-greater-vega-power-savings-displayport-1-4-fixes?p=1027933#post1027933

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #3 from dwagner --- Just for the record, others have reported similar symptoms - here is a recent example: https://bugs.freedesktop.org/show_bug.cgi?id=10 -- You are receiving this mail because: You are the assignee for the

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #2 from dwagner --- Just to mention this once again: These system crashes still occur, and way too frequently to consider the amdgpu driver stable enough for professional use. Sample dmesg output from today:

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 --- Comment #1 from dwagner --- Sadly, not only did this bug not attract any attention, it also still occurs, and seemingly even more frequent than before, on current bleeding-edge kernels from amd-staging-drm-next, and

[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

https://bugs.freedesktop.org/show_bug.cgi?id=102322 Bug ID: 102322 Summary: System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung! Product: DRI Version: DRI git Hardware: x86