Bug 205147 - Unable to shut down - radeon_drv.c - radeon_suspend_kms()
Summary: Unable to shut down - radeon_drv.c - radeon_suspend_kms()
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-09 18:07 UTC by Richard Herbert
Modified: 2020-12-15 02:07 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.3.5
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Richard Herbert 2019-10-09 18:07:13 UTC 
From the 5.3.5 changelog:

 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.

This commit creates a problem where I can't shut down or restart my system without pressing the Rest button.  The problem is solved by commenting out the call to radeon_suspend_kms() in radeon_pci_shutdown.

The gpu hardware is an ATI Radeon HD5770 in a PCI-E slot on an Intel DG41RQ MB.
Comment 1 Alex Deucher 2019-10-09 18:16:21 UTC 
Will revert.
Comment 2 wwa 2019-10-17 09:44:25 UTC 
Hi,

I also have same problem and 
can confirm that reverting commit 6f7fe9a93e6c09bf988c5059403f5f88e17e21e6 fixes it.

my hardware:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770], PCI-E,
on a MICRO-STAR INTERNATIONAL CO.,LTD MS-7599/770-C45 (MS-7599), BIOS V1.15 03/04/2011

(this bug kind of reminds me of https://bugs.freedesktop.org/show_bug.cgi?id=99524)
Comment 3 Alex Deucher 2019-10-17 12:38:20 UTC 
Revert queued:
https://lists.freedesktop.org/archives/amd-gfx/2019-October/041381.html
Should land this week.
Comment 5 Richard Herbert 2020-12-15 02:07:59 UTC 
Sorry for not closing a LONG time ago.
Note You need to log in before you can comment on or make changes to this bug.