<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!" href="https://bugs.freedesktop.org/show_bug.cgi?id=102322#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!" href="https://bugs.freedesktop.org/show_bug.cgi?id=102322">bug 102322</a> from <a class="email" href="mailto:jb5sgc1n.nya@20mm.eu" title="dwagner <jb5sgc1n.nya@20mm.eu>"> dwagner</a> <pre>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 S3-resume crashes) - I filed bug report <a class="bz_bug_link bz_status_NEW " title="NEW - "BUG: unable to handle kernel paging request at 0000000000002000" at amdgpu_vm_cpu_set_ptes at S3 resume" href="show_bug.cgi?id=107065">https://bugs.freedesktop.org/show_bug.cgi?id=107065</a> on this. (In reply to Andrey Grodzovsky from <a href="show_bug.cgi?id=102322#c17">comment #17</a>) > dwagner, this is obviously just a work around and not a fix. It points to > some problem with SDMA packets, if you want to continue exploring we can try > to dump some fence traces and SDMA HW ring content to examine the latest > packets before the hang happened. If you can include some debug output into "amd-staging-drm-next" that helps finding the root cause, I might be able to provide some output - if the kernel survives long enough after the crash to write the system journal - this has not always been the case.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>