From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205147] New: Unable to shut down - radeon_drv.c - radeon_suspend_kms()
Date: Wed, 09 Oct 2019 18:07:13 +0000 [thread overview]
Message-ID: <bug-205147-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205147
Bug ID: 205147
Summary: Unable to shut down - radeon_drv.c -
radeon_suspend_kms()
Product: Drivers
Version: 2.5
Kernel Version: 5.3.5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: rherbert@sympatico.ca
Regression: No
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.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-10-09 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 18:07 bugzilla-daemon [this message]
2019-10-09 18:16 ` [Bug 205147] Unable to shut down - radeon_drv.c - radeon_suspend_kms() bugzilla-daemon
2019-10-17 9:44 ` bugzilla-daemon
2019-10-17 12:38 ` bugzilla-daemon
2019-10-18 13:25 ` bugzilla-daemon
2020-12-15 2:07 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-205147-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.