<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c21">Comment # 21</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 <span class="vcard"><a class="email" href="mailto:andrey.grodzovsky@amd.com" title="Andrey Grodzovsky <andrey.grodzovsky@amd.com>"> <span class="fn">Andrey Grodzovsky</span></a>
</span></b>
<pre>(In reply to dwagner from <a href="show_bug.cgi?id=107065#c20">comment #20</a>)
<span class="quote">> (In reply to Andrey Grodzovsky from <a href="show_bug.cgi?id=107065#c19">comment #19</a>)
> > 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 ?
>
> Not for the exact symptom described in this report, but for an older S3
> resume issue that was partially resolved -
> <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit"
href="show_bug.cgi?id=103277">https://bugs.freedesktop.org/show_bug.cgi?id=103277</a> - I did once find the
> regression caused by the "drm/amd/display: Match actual state during S3
> resume" commit.
>
> Unluckily, the many changes that followed thereafter do no longer allow to
> bisect the symptom there to one specific commit, but given that it still
> occurs if I use the option "drm.edid_firmware=edid/LG_EG9609_edid.bin", I
> think there is still some bug in the order of things done during
> re-initialization upon S3 resumes, and setting some fixed EDID seems to
> expose it as crash.</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>