[Bug 98276] Kernel Panic on shutdown caused by "drm/amdgpu: always apply pci shutdown callbacks"
https://bugs.freedesktop.org/show_bug.cgi?id=98276
Bug ID: 98276 Summary: Kernel Panic on shutdown caused by "drm/amdgpu: always apply pci shutdown callbacks" Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: johannes.hirte@datenkhaos.de
Kernel 4.9-rc1 fails on shutdown/reboot with a panic. Bisect pointed me to
00ea8cba5ef7b783f11cb1a0b900b7c18d2ce0b6 is the first bad commit commit 00ea8cba5ef7b783f11cb1a0b900b7c18d2ce0b6 Author: Alex Deucher alexander.deucher@amd.com Date: Thu Sep 22 14:40:29 2016 -0400
drm/amdgpu: always apply pci shutdown callbacks (v2)
We can't properly detect all hypervisors and we need this to properly tear down the hardware.
v2: trivial warning fix
Signed-off-by: Alex Deucher alexander.deucher@amd.com
:040000 040000 868a00ff980f95dac82b908df0737342bf40cdc3 02bf2cf4e8797d37d454301afedf2f97735b60ca M drivers
After removing this commit, everything works again. System is a Carrizo.
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #1 from Alex Deucher alexdeucher@gmail.com --- Can you attach the panic messages?
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #2 from Alex Deucher alexdeucher@gmail.com --- If you can't get them during a reboot/shutdown, you can reproduce it my unloading the module as they use the same code. E.g., modprobe -r amdgpu
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #3 from Johannes Hirte johannes.hirte@datenkhaos.de --- I only have a black screen when the panic happens. Rebuild the kernel with amdgpu as module for the unloading module option, but this way I can't remove the driver cause the module is in use.
https://bugs.freedesktop.org/show_bug.cgi?id=98276
Mike Lothian mike@fireburn.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mike@fireburn.co.uk
--- Comment #4 from Mike Lothian mike@fireburn.co.uk --- rmmod -f amdgpu should do the trick
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #5 from Johannes Hirte johannes.hirte@datenkhaos.de --- (In reply to Mike Lothian from comment #4)
rmmod -f amdgpu should do the trick
This way I can remove the module, but I don't get the panic. The screen goes black and I have to reboot via SysReq Keys.
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #6 from Alex Deucher alexdeucher@gmail.com --- You can also unbind the console before unloading the module.
sudo bash -c "echo 0 > /sys/class/vtconsole/vtcon1/bind" sudo modprobe -r amdgpu
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #7 from Johannes Hirte johannes.hirte@datenkhaos.de --- (In reply to Alex Deucher from comment #6)
You can also unbind the console before unloading the module.
sudo bash -c "echo 0 > /sys/class/vtconsole/vtcon1/bind"
First time this resulted in a black screen with a panic, next time the system hung, but reboot via SysReq Keys worked. Always happened on the unbind.
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #8 from Johannes Hirte johannes.hirte@datenkhaos.de --- Created attachment 127488 --> https://bugs.freedesktop.org/attachment.cgi?id=127488&action=edit dmesg output after unloading amdgpu.ko
I've retried removing the module via ssh session and the second time I was successful. The dmesg output is attached.
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #9 from Ernst Sjöstrand ernstp@gmail.com --- Is this fixed somewhere now also? Related to https://bugs.freedesktop.org/show_bug.cgi?id=98200 I guess?
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #10 from Johannes Hirte johannes.hirte@datenkhaos.de --- (In reply to Ernst Sjöstrand from comment #9)
Is this fixed somewhere now also?
still happens with 4.9-rc2 as well as 4.10-wip
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #11 from Johannes Hirte johannes.hirte@datenkhaos.de --- As the dmesg shows a problem in the ACP code, I've just disabled it now and it works. Don't know what's the real problem, but without ACP my system reboot fine.
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #12 from Alex Deucher alexdeucher@gmail.com --- Created attachment 127736 --> https://bugs.freedesktop.org/attachment.cgi?id=127736&action=edit possible fix
This should fix it.
https://bugs.freedesktop.org/show_bug.cgi?id=98276
--- Comment #13 from Johannes Hirte johannes.hirte@datenkhaos.de --- (In reply to Alex Deucher from comment #12)
Created attachment 127736 [details] [review] possible fix
This should fix it.
Yes, this fixes the panic on reboot/unloading the driver.
https://bugs.freedesktop.org/show_bug.cgi?id=98276
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #14 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/106.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org