[Bug 107065] "BUG: unable to handle kernel paging request at 0000000000002000" in amdgpu_vm_cpu_set_ptes at amdgpu_vm.c:921

[bugzilla-daemon@freedesktop.org]

[-- Attachment #1.1: Type: text/plain, Size: 1123 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107065

--- Comment #20 from dwagner <jb5sgc1n.nya@20mm.eu> ---
(In reply to Andrey Grodzovsky from comment #19)
> 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 -
https://bugs.freedesktop.org/show_bug.cgi?id=103277 - 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2386 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel