<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" in amdgpu_vm_cpu_set_ptes at amdgpu_vm.c:921" href="https://bugs.freedesktop.org/show_bug.cgi?id=107065#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - "BUG: unable to handle kernel paging request at 0000000000002000" in amdgpu_vm_cpu_set_ptes at amdgpu_vm.c:921" 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#c21">comment #21</a>) > I found the offending patch - drm: Stop updating plane->crtc/fb/old_fb on > atomic drivers > Not sure yet what's going on there and not sure it will fix you issue with > amdgpu_vm_cpu_set_ptes page fault after S3 since I haven't observe it here. > Still worth a try on your side to revert it and see what happens. Reverting the commit "drm: Stop updating plane->crtc/fb/old_fb on atomic drivers" for me only changes that after S3 resume, the very picture that was visible before S3 sleep is displayed again - but the kernel crash at "amdgpu_vm_cpu_set_ptes+0x76" still happenes, so the "resumed picture" is as frozen as the system is dead.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>