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:04:03 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1278208098=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 863BA6EE13
for ; Wed, 11 Jul 2018 22:04:03 +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
--===============1278208098==
Content-Type: multipart/alternative; boundary="15313466430.c2d80.18744"
Content-Transfer-Encoding: 7bit
--15313466430.c2d80.18744
Date: Wed, 11 Jul 2018 22:04:03 +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 #19 from Andrey Grodzovsky ---
(In reply to Andrey Grodzovsky from comment #18)
> (In reply to dwagner from comment #17)
> > Interesting observation: If I first switch from the X11 display to the
> > console display (with Alt-F2), and then enter "echo mem >/sys/power/sta=
te"
> > on the console, above described crashes upon S3 resume do not occur, an=
d I
> > do not see the "[TTM] Buffer eviction failed" in the kernel log, neither
> > with vm_update_mode=3D0, nor with vm_update_mode=3D3.
> >=20
> > Switching back to the X11 display after a successful S3 resume to the
> > console also works fine.
> >=20
> > What could be the relevant difference here?
>=20
> Well, there is no acceleration involved when in console mode. So maybe th=
is
> has something to do with it.
>=20
> Anyway, i am sidetracked a bit by an internal requirement but once i fini=
sh
> 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 tim=
e.
Were you able to find a regression point for this ?
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15313466430.c2d80.18744
Date: Wed, 11 Jul 2018 22:04:03 +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 # 19
on bug 10706=
5
from Andrey Grodzovsky
(In reply to Andrey Grodzovsky from comment #18)
> (In reply to dwagner from comment #17)
> > Interesting observation: If I first switch from the X11 display t=
o 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 occ=
ur, and I
> > do not see the "[TTM] Buffer eviction failed" in the ke=
rnel log, neither
> > with vm_update_mode=3D0, nor with vm_update_mode=3D3.
> >=20
> > Switching back to the X11 display after a successful S3 resume to=
the
> > console also works fine.
> >=20
> > What could be the relevant difference here?
>=20
> Well, there is no acceleration involved when in console mode. So maybe=
this
> has something to do with it.
>=20
> Anyway, i am sidetracked a bit by an internal requirement but once i f=
inish
> 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 tim=
e.
Were you able to find a regression point for this ?
You are receiving this mail because:
- You are the assignee for the bug.
=
--15313466430.c2d80.18744--
--===============1278208098==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1278208098==--