From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 107154] [drm] GPU recovery disabled.
Date: Sun, 08 Jul 2018 19:00:26 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1283323263=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id BF0556E03B
for ; Sun, 8 Jul 2018 19:00:26 +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
--===============1283323263==
Content-Type: multipart/alternative; boundary="15310764260.d8B3C2C.5576"
Content-Transfer-Encoding: 7bit
--15310764260.d8B3C2C.5576
Date: Sun, 8 Jul 2018 19:00:26 +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=3D107154
--- Comment #1 from dwagner ---
Indeed, crashes upon S3 resumes have been abundant with amdgpu.dc=3D1 for m=
any
months now, and seemingly for more than one reason.
One bug I reported in August 2017 with
https://bugs.freedesktop.org/show_bug.cgi?id=3D102323 - that one was fixed
quickly.
The next S3 resume crash I reported in October 2017 in
https://bugs.freedesktop.org/show_bug.cgi?id=3D103277, that one stayed with=
out
any resolution until April 2018, and the fix found in that report only work=
s if
no "drm.edid_firmware=3D..." kernel command line option is used.
Another crash bug with S3 resumes I reported for 4.17.2 kernels in
https://bugs.freedesktop.org/show_bug.cgi?id=3D107065 - then realized that =
4.18
pre-releases exhibit the very same kind of crash immediately upon starting =
X11.
For this crash upon X11 startup, there is a patch in the bug report, but it
does not prevent the S3 resume crash.
I currently work around S3 resume crashes by switching to the console displ=
ay
before enterin S3 sleep - but this is really an awkward work-around.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15310764260.d8B3C2C.5576
Date: Sun, 8 Jul 2018 19:00:26 +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
Commen=
t # 1
on bug 10715=
4
from dwagner
Indeed, crashes upon S3 resumes have been abundant with amdgpu=
.dc=3D1 for many
months now, and seemingly for more than one reason.
One bug I reported in August 2017 with
https://bugs.freedesktop.org/show_bug.=
cgi?id=3D102323 - that one was fixed
quickly.
The next S3 resume crash I reported in October 2017 in
https://bugs.freedesktop.org/show_bug.=
cgi?id=3D103277, that one stayed without
any resolution until April 2018, and the fix found in that report only work=
s if
no "drm.edid_firmware=3D..." kernel command line option is used.
Another crash bug with S3 resumes I reported for 4.17.2 kernels in
https://bugs.freedesktop.org/show_bug.=
cgi?id=3D107065 - then realized that 4.18
pre-releases exhibit the very same kind of crash immediately upon starting =
X11.
For this crash upon X11 startup, there is a patch in the bug report, but it
does not prevent the S3 resume crash.
I currently work around S3 resume crashes by switching to the console displ=
ay
before enterin S3 sleep - but this is really an awkward work-around.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15310764260.d8B3C2C.5576--
--===============1283323263==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1283323263==--