From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 111980] Rebbot and shutdown doesn't work on specific hardware
Date: Fri, 11 Oct 2019 16:05:12 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1279314725=="
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 413476EC5C
for ; Fri, 11 Oct 2019 16:05:13 +0000 (UTC)
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
--===============1279314725==
Content-Type: multipart/alternative; boundary="15708099131.DEee5bfE.26917"
Content-Transfer-Encoding: 7bit
--15708099131.DEee5bfE.26917
Date: Fri, 11 Oct 2019 16:05:13 +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=3D111980
Bug ID: 111980
Summary: Rebbot and shutdown doesn't work on specific hardware
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: not set
Priority: not set
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: lei.pero@gmail.com
When system shutdown/reboot is initiated, everything works as it should,
journal doesn't show any error and it reaches target reboot (for example),
display shuts down properly, but PC stays powered on (requiring hard reset)
indefinitely.
This happened after kernel upgrade, after bisectiing, commit that was to bl=
ame
was bellow, after removing just that specific commit, it would work as
expected:
894c414129a8d9ef1b2de443015e4dde6085f64f is the first bad commit
commit 894c414129a8d9ef1b2de443015e4dde6085f64f
Author: KyleMahlkuch
Date: Wed Jul 31 17:10:14 2019 -0500
drm/radeon: Fix EEH during kexec
[ Upstream commit 6f7fe9a93e6c09bf988c5059403f5f88e17e21e6 ]
During kexec some adapters hit an EEH since they are not properly
shut down in the radeon_pci_shutdown() function. Adding
radeon_suspend_kms() fixes this issue.
Signed-off-by: KyleMahlkuch
Signed-off-by: Alex Deucher
Signed-off-by: Sasha Levin
drivers/gpu/drm/radeon/radeon_drv.c | 8 ++++++++
1 file changed, 8 insertions(+)
Issue is described here, seems like others have similar issue that might be
connected with this as well:
https://bbs.archlinux.org/viewtopic.php?id=3D249787
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15708099131.DEee5bfE.26917
Date: Fri, 11 Oct 2019 16:05:13 +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
| Bug ID |
111980
|
| Summary |
Rebbot and shutdown doesn't work on specific hardware
|
| Product |
DRI
|
| Version |
XOrg git
|
| Hardware |
x86-64 (AMD64)
|
| OS |
Linux (All)
|
| Status |
NEW
|
| Severity |
not set
|
| Priority |
not set
|
| Component |
DRM/Radeon
|
| Assignee |
dri-devel@lists.freedesktop.org
|
| Reporter |
lei.pero@gmail.com
|
When system shutdown/reboot is initiated, everything works as =
it should,
journal doesn't show any error and it reaches target reboot (for example),
display shuts down properly, but PC stays powered on (requiring hard reset)
indefinitely.
This happened after kernel upgrade, after bisectiing, commit that was to bl=
ame
was bellow, after removing just that specific commit, it would work as
expected:
894c414129a8d9ef1b2de443015e4dde6085f64f is the first bad commit
commit 894c414129a8d9ef1b2de443015e4dde6085f64f
Author: KyleMahlkuch <kmahlkuc@linux.vnet.ibm.com>
Date: Wed Jul 31 17:10:14 2019 -0500
drm/radeon: Fix EEH during kexec
[ Upstream commit 6f7fe9a93e6c09bf988c5059403f5f88e17e21e6 ]
During kexec some adapters hit an EEH since they are not properly
shut down in the radeon_pci_shutdown() function. Adding
radeon_suspend_kms() fixes this issue.
Signed-off-by: KyleMahlkuch <kmahlkuc@linux.vnet.ibm.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/gpu/drm/radeon/radeon_drv.c | 8 ++++++++
1 file changed, 8 insertions(+)
Issue is described here, seems like others have similar issue that might be
connected with this as well:
https://bbs=
.archlinux.org/viewtopic.php?id=3D249787
You are receiving this mail because:
- You are the assignee for the bug.
=
--15708099131.DEee5bfE.26917--
--===============1279314725==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs
--===============1279314725==--