<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#c19">Comment # 19</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:andrey.grodzovsky@amd.com" title="Andrey Grodzovsky <andrey.grodzovsky@amd.com>"> Andrey Grodzovsky</a> <pre>(In reply to Andrey Grodzovsky from <a href="show_bug.cgi?id=107065#c18">comment #18</a>) > (In reply to dwagner from <a href="show_bug.cgi?id=107065#c17">comment #17</a>) > > Interesting observation: If I first switch from the X11 display to the > > console display (with Alt-F2), and then enter "echo mem >/sys/power/state" > > on the console, above described crashes upon S3 resume do not occur, and I > > do not see the "[TTM] Buffer eviction failed" in the kernel log, neither > > with vm_update_mode=0, nor with vm_update_mode=3. > > > > Switching back to the X11 display after a successful S3 resume to the > > console also works fine. > > > > What could be the relevant difference here? > > Well, there is no acceleration involved when in console mode. So maybe this > has something to do with it. > > Anyway, i am sidetracked a bit by an internal requirement but once i finish > I will get back to this issue especially because I got another report with > the same failure as you describe. I was able to reproduce this instantly without even using page tables CPU update mode. Looks like a regression since S3 was working fine for long time. Were you able to find a regression point for this ?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>