<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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="https://bugs.freedesktop.org/show_bug.cgi?id=107065#c7">Comment # 7</a> on <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="https://bugs.freedesktop.org/show_bug.cgi?id=107065">bug 107065</a> from <a class="email" href="mailto:jb5sgc1n.nya@20mm.eu" title="dwagner <jb5sgc1n.nya@20mm.eu>"> dwagner</a> <pre>(In reply to Andrey Grodzovsky from <a href="show_bug.cgi?id=107065#c6">comment #6</a>) > So with Arch Linux kernel it happens only during S3 but with > amd-staging-drm-next it happens once you start X ? Yes. I know it sounds strange, but it's currently 100% reproducible to me: Booting linux-4.17.2-ARCH with amdgpu.vm_update_mode=0: X11 starts fine, but system crashes after minutes of firefox browsing Booting linux-4.17.2-ARCH with amdgpu.vm_update_mode=3: X11 starts fine, system does not crash (for at least hours of use) but crashes as above if resumed from S3 sleep Booting linux compiled from amd-staging-drm-next, as of commit 527d6e839a0e52b744fd092453544e4f58977334 from yesterday, with amdgpu.vm_update_mode=0: X11 starts fine, but system crashes after minutes of firefox browsing Booting linux compiled from amd-staging-drm-next, as of commit 527d6e839a0e52b744fd092453544e4f58977334 from yesterday, with amdgpu.vm_update_mode=3: X11 does not start, crashes immediately with the same above pasted kernel BUG message and backtrace So something with CPU-based vm_update_mode is broken, but in a different way than the SDMA-based method. I will change the subject of this report to reflect that this crash is not necessarily S3-resume-related.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>