FS#66984 - [linux] 5.7.2 not loading on Intel I3 9100F

Attached to Project: Arch Linux
Opened by Vladimir (snigurmd) - Friday, 12 June 2020, 19:03 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 15:15 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
System stopped loading after recent upgrade to Linux 5.7.2-arch1-1
After BIOS logo black screen with a cursor appears for a few seconds, then throws back to BIOS setup.

Additional info:
Using EFISTUB for loading with such command:

efibootmgr -d /dev/nvme0n1p1 -p 1 -c -L "Linux nvm" -l vmlinuz-linux -u "root=/dev/nvme0n1p2 rw audit=0 ipv6.disable=1 pcie_aspm=off initrd=/initramfs-linux.img"

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.154
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
vmx flags : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple pml ept_mode_based_exec
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 7202.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

Motherboard Gigabyte B365M D3H rev.1.
Problem remains when booting from a HDD.

Steps to reproduce:
1. Upgrade to linux 5.7.2
2. Reboot
This task depends upon

Closed by  freswa (frederik)
Sunday, 13 September 2020, 15:15 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Friday, 12 June 2020, 23:29 GMT Comment by Vladimir (snigurmd) - Saturday, 13 June 2020, 09:53 GMT
Well it doesn't look this way. initrd is located in the same directory. And i'm not getting any messages. It's just the cursor blinking for a while jumping between two positions at the top left corner and that's it.
Comment by loqs (loqs) - Saturday, 13 June 2020, 11:10 GMT
Just to make sure the issue is different could you try changing the entry to:
efibootmgr -d /dev/nvme0n1p1 -p 1 -c -L "Linux nvm" -l vmlinuz-linux -u "root=/dev/nvme0n1p2 rw audit=0 ipv6.disable=1 pcie_aspm=off initrd=initramfs-linux.img"
or
efibootmgr -d /dev/nvme0n1p1 -p 1 -c -L "Linux nvm" -l vmlinuz-linux -u "root=/dev/nvme0n1p2 rw audit=0 ipv6.disable=1 pcie_aspm=off initrd=\initramfs-linux.img"
Comment by Thomas Jäger (xunil64) - Saturday, 13 June 2020, 12:59 GMT
I have a similar issue, loading linux 5.7.2 with efistub
There seems to be a error message like "couldnt open /....", but this error message appears for just some ms

Installed with:
# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "Arch Linux" --loader /vmlinuz-linux --unicode 'initrd=/intel-ucode.img initrd=/initramfs-linux.img root=/dev/nvme0n1p5 rootflags=subvol=root,noatime rw' -v

initramfs-linux.img and intel-ucode.img are both installed/located on the the EFI boot partition (together with vmlinuz-linux)

Fallback booting is done by systemd-boot which is still running/booting with the following config (at the end its the same configuration):

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=/dev/nvme0n1p5 rootflags=subvol=root,noatime rw


# efibootmgr -v
BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0000,0008,000C,0009,000A,000B,000D,000E
Boot0000* Arch Linux HD(1,GPT,d7cc26e3-277f-4ea9-906d-9bc2009dee96,0x800,0xfa000)/File(\VMLINUZ-LINUX)i.n.i.t.r.d.=./.i.n.t.e.l.-.u.c.o.d.e...i.m.g. .i.n.i.t.r.d.=./.i.n.i.t.r.a.m.f.s.-.l.i.n.u.x...i.m.g. .r.o.o.t.=./.d.e.v./.n.v.m.e.0.n.1.p.5..r.o.o.t.f.l.a.g.s.=.s.u.b.v.o.l.=.r.o.o.t.,.n.o.a.t.i.m.e. .r.w.
Boot0008* Linux Boot Manager HD(1,GPT,d7cc26e3-277f-4ea9-906d-9bc2009dee96,0x800,0xfa000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0009 Hard Drive BBS(HD,,0x0)..BO
Boot000A CD/DVD Drive BBS(CDROM,,0x0)..BO
Boot000B* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot000C* UEFI OS HD(1,GPT,d7cc26e3-277f-4ea9-906d-9bc2009dee96,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot000D UEFI: IP4 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(d8cb8a5d7e53,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot000E UEFI: IP6 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(d8cb8a5d7e53,0)/IPv6([::]:<->[::]:,0,0)..BO

Comment by Gianluca Pettinello (gianluca.pettinello) - Saturday, 13 June 2020, 13:03 GMT
Similar problem
Booting 5.7.2 with intel i915 KMS the debug stucks at switching inteldrmfb
Comment by Vladimir (snigurmd) - Saturday, 13 June 2020, 13:14 GMT
UPDATE: Removing slashes in kernel initrd option does solve the issue.
Comment by Thomas Jäger (xunil64) - Saturday, 13 June 2020, 13:14 GMT
Yes, both versions - removing slashes ("/") or replacing with backslashes ("\") for initrd - are solving the issue



Comment by Susan Thapa (suson) - Sunday, 14 June 2020, 02:09 GMT
I also have the same issue with the kernel 5.7.2, booting with ignore_loglevel is stuck at
fb0: switching to inteldrmfb from EFI VGA
I was unable to find a solution for it after searching in forums. So, I just downgraded the kernel and everything is working fine.
Comment by Gianluca Pettinello (gianluca.pettinello) - Sunday, 14 June 2020, 05:01 GMT
Same as Susan. Removed intel ucode, nothing. Having dual graphic card I activated the dedicated Nvidia and everything is fine. So it is related to i915 stack inside the kernel.

Loading...