FS#63860 - linux-5.3arch1-1 hangs at loading initial ramdisk

Attached to Project: Arch Linux
Opened by kursu (kursu) - Friday, 20 September 2019, 12:19 GMT
Last edited by freswa (frederik) - Tuesday, 18 February 2020, 21:54 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details


linux-5.14-arch2-1 works just fine, however upgrading to 5.3-arch1-1 makes system unable to boot. Hangs at "Loading Inital Ramdisk..."


Downgrading to 5.14-arch2-1 again as a temporary solution
This task depends upon

Closed by  freswa (frederik)
Tuesday, 18 February 2020, 21:54 GMT
Reason for closing:  Fixed
Comment by kursu (kursu) - Friday, 20 September 2019, 13:22 GMT
Typo, 5.2.14-arch2-1 not 5.14 lol
Comment by daimonion (demon) - Friday, 20 September 2019, 13:35 GMT
I can confirm this, all I know from Xorg log is that radeon driver is not loaded.
   Xorg.log (5.2 KiB)
Comment by kursu (kursu) - Friday, 20 September 2019, 14:12 GMT
Ok, I tried module_blacklist=amdgpu as kernel parameter and removed "quite" but with no success in even booting, I get no screen output at all after "Loading initial ramdisk"
Comment by kursu (kursu) - Friday, 20 September 2019, 22:03 GMT
Downloaded the 5.3 source, and configured a minimal kernel and recompiled. 10 reboots later and now it works. Was suspicious about he new navi code but navi seems to work also. Will dig deeper into the 5.3arch1-1 config tomorrow
Comment by kursu (kursu) - Saturday, 21 September 2019, 21:50 GMT
Found the solution.

AMD IOMMU Version 2 driver cant be compiled as module. must be included in kernel
Comment by loqs (loqs) - Saturday, 21 September 2019, 22:02 GMT Comment by daimonion (demon) - Sunday, 22 September 2019, 11:49 GMT
@loqs This is not a solution as I am experiencing same problem on my laptop with Intel graphics.
Comment by loqs (loqs) - Sunday, 22 September 2019, 12:00 GMT
@demon I was not suggesting it was a solution. I responding to kurso's post above mine
pointing out the conclusion did not match with the facts I provided.
Comment by daimonion (demon) - Sunday, 20 October 2019, 13:21 GMT
Tried 5.3.7.arch1-1 now and the same issue happens.
Comment by Snarpix (Snarpix) - Wednesday, 23 October 2019, 10:57 GMT
Same issue. Last working kernel linux-5.2.14.arch2-1. Hangs at random place, no errors in log. LTS kernel works with no issues.
I have managed to boot 5.3 kernel by appending acpi_osi="Windows 2018" to kernel command line, but after hibernate\suspend any mouse or keyboard stops working, shutdown button works(shuts down nicely).
Also hang during boot still happens sometimes with acpi_osi.
I stick to LTS kernel, for now.
Comment by kursu (kursu) - Friday, 08 November 2019, 22:24 GMT
5.3.8-arch1 fixes the issue for me
Comment by daimonion (demon) - Sunday, 10 November 2019, 16:07 GMT
Neither `5.3.8.1-1` or `5.3.10.1-1` from testing fixes the bug for me. This is becoming quite frustrating.
Comment by Snarpix (Snarpix) - Tuesday, 12 November 2019, 11:14 GMT
Same, 5.3.10.1-1 don't make a difference. Still hangs randomly at boot.
Comment by Konstantin Goncharik (botanegg) - Wednesday, 13 November 2019, 06:44 GMT
5.3.10-arch1-1 on ASUS ROG GL702ZC with bios 306 the same issue happens.
My hdd-led indicated high IO while that time
Comment by Trevor Nierman (HeWhoWearsPants) - Thursday, 21 November 2019, 04:52 GMT
Same issue with ASUS ZenBook Q326FA and all 5.3.* kernels. Also experienced fairly extreme heating if left hanging for too long, which (I guess?) confirms @botanegg's experience with high IO
Comment by daimonion (demon) - Thursday, 12 December 2019, 11:39 GMT
Installed 5.4.2-arch1-1 and all is okay! So whatever it was, it seems it was fixed in 4.2. At least in my case (i7 6500U integrated graphics).
Comment by Antonio Giustino (Superjolly002) - Tuesday, 14 January 2020, 10:39 GMT
This morning I had a similar issue to this, after the last update (5.4.11-arch1-1) kernel failed to load because of a failed initializing Ramdisk.
I solved by reinstalling kernel via chroot with a live os
Comment by Snarpix (Snarpix) - Saturday, 15 February 2020, 14:43 GMT
After LTS kernel was updated to 5.3+ branch I can't boot my system without acpi=off parameter.
I manually downgraded to 4.19, which still works really stable. Problem started with 5.3 kernel version, 5.2 worked.
Since ACPI=off helps maybe there is a guide how to debug ACPI problems?
Comment by Snarpix (Snarpix) - Tuesday, 18 February 2020, 20:41 GMT
I have figured it out. My issue was with bbswitch and https://bugzilla.kernel.org/show_bug.cgi?id=156341
I have removed bbswitch and everything boots fine.

Loading...