FS#46745 - [linux] Freeze on "Triggering uevents..." with AMD
Attached to Project:
Arch Linux
Opened by Andrew Porter (link_the_programmer) - Thursday, 15 October 2015, 23:36 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 17 October 2017, 12:34 GMT
Opened by Andrew Porter (link_the_programmer) - Thursday, 15 October 2015, 23:36 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 17 October 2017, 12:34 GMT
|
Details
Description: When booting Arch Linux 10.1-dual (I used
x86_64, on laptop Toshiba Satellite C855D), linux freezes on
"Triggering uevents...". This apparently is an AMD Radeon
Driver problem. Evidence for this is at
https://bbs.archlinux.org/viewtopic.php?pid=1193312#p1193312. Apparently this has been a problem for a long time.
Suggests that this bug happens on any architecture that is
using Radeon graphics.
Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Boot Arch Linux 10.1-dual onto an AMD Radeon HD-based computer -> frozen cursor and system after "Triggering uevents", nothing special happens. |
This task depends upon
Workaround for me has been: adding "debug" to the kernel command line on boot ("acpi=off" as described by link_the_programmer also worked). "nomodeset" and "modeprobe.blacklist=radeon" as expected did not fix the hang.
This still happens with kernel 4.3
Issue is still present in Kernel 4.4.1
https://bugzilla.kernel.org/show_bug.cgi?id=87581
Sorry, I am not carefully looking for a solution. Problem solved.
tl;dr: put "blacklist sp5100_tco" in /etc/modprobe.d/blacklist.conf or disable it on the cmdline: modprobe.blacklist=sp5100_tco
upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=114201
Unfortunately, this does not fix my particular problem. :(
This looks like some race condition to me, since booting still works by just appending "debug" to the cmdline, so I think it "magically" works, because the kernel spends most time printing to the slow tty. I'm unable to find anything in the debug log (like ACPI errors).
If I find the time, I'll try downgrading the BIOS and see if that helps.