From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107065] "BUG: unable to handle kernel paging request at 0000000000002000" in amdgpu_vm_cpu_set_ptes at amdgpu_vm.c:921 Date: Wed, 11 Jul 2018 22:23:05 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0055556337==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 7A5B66EE25 for ; Wed, 11 Jul 2018 22:23:05 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0055556337== Content-Type: multipart/alternative; boundary="15313477851.52792.22821" Content-Transfer-Encoding: 7bit --15313477851.52792.22821 Date: Wed, 11 Jul 2018 22:23:05 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D107065 --- Comment #20 from dwagner --- (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 res= ume issue that was partially resolved - https://bugs.freedesktop.org/show_bug.cgi?id=3D103277 - I did once find the regression caused by the "drm/amd/display: Match actual state during S3 res= ume" 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 oc= curs if I use the option "drm.edid_firmware=3Dedid/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. --=20 You are receiving this mail because: You are the assignee for the bug.= --15313477851.52792.22821 Date: Wed, 11 Jul 2018 22:23:05 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 20 on bug 10706= 5 from dwagner

(In reply to Andrey Grodzovsky from comment #19)
> I was able to reproduce this instantly without e=
ven 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 res=
ume
issue that was partially resolved -
https://bugs.freedesktop.org/show_bug.=
cgi?id=3D103277 - I did once find the
regression caused by the "drm/amd/display: Match actual state during S=
3 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 oc=
curs
if I use the option "drm.edid_firmware=3Dedid/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.

= --15313477851.52792.22821-- --===============0055556337== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0055556337==--