| Bug ID | 98276 |
|---|---|
| Summary | Kernel Panic on shutdown caused by "drm/amdgpu: always a= pply 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 p= ointed me to=20 00ea8cba5ef7b783f11cb1a0b900b7c18d2ce0b6 is the first bad commit commit 00ea8cba5ef7b783f11cb1a0b900b7c18d2ce0b6 Author: Alex Deucher <a= lexander.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.
If you can't get them during a reboot/shutdown, you can reprod=
uce it my
unloading the module as they use the same code. E.g., modprobe -r amdgpu
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 remo= ve the driver cause the module is in use.
| What | Removed | Added |
|---|---|---|
| CC | mike@fireburn.co.uk |
(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.
You can also unbind the console before unloading the module. sudo bash -c "echo 0 > /sys/class/vtconsole/vtcon1/bind" sudo modprobe -r amdgpu
(In reply to Alex Deucher from comment #6) > You can also unbind the console before unloading= the module. >=20 > sudo bash -c "echo 0 > /sys/class/vtconsole/vtcon1/bind"<= /span > First time this resulted in a black screen with a panic, next time the syst= em hung, but reboot via SysReq Keys worked. Always happened on the unbind.
Created a=
ttachment 127488 [details]
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.
Is this fixed somewhere now also? Related to https://bugs.freedesktop.org/show_bug.c= gi?id=3D98200 I guess?
(In reply to Ernst Sj=C3=B6strand from comment #9) > Is this fixed somewhere now also? still happens with 4.9-rc2 as well as 4.10-wip
As the dmesg shows a problem in the ACP code, I've just disabl= ed it now and it works. Don't know what's the real problem, but without ACP my system reboot fine.
Created attachment 127736 = [details] [review] possible fix This should fix it.
(In reply to Alex Deucher from comment #12) > Created attachment 12= 7736 [details] [review] [review] > possible fix >=20 > This should fix it. Yes, this fixes the panic on reboot/unloading the driver.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- 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.