FS#67011 - [intel-ucode] freeze on boot with 20200609-2 (06-5e-03)
Attached to Project:
Arch Linux
Opened by Andrea Amorosi (AndreaA) - Monday, 15 June 2020, 21:50 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 16 June 2020, 19:22 GMT
Opened by Andrea Amorosi (AndreaA) - Monday, 15 June 2020, 21:50 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 16 June 2020, 19:22 GMT
|
Details
Description:
With the intel-ucode 20200609-2 my system freezes just after "loading initial ramdisk". This happens between 50% and 75% of the times the system is rebooted. Reverting to intel-ucode-20200520-1 solves the issue. This is the output of lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-3 Off-line CPU(s) list: 4-7 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 94 Model name: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Stepping: 3 CPU MHz: 968.499 CPU max MHz: 3500,0000 CPU min MHz: 800,0000 BogoMIPS: 5202.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache: 1 MiB L3 cache: 6 MiB NUMA node0 CPU(s): 0-3 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled Vulnerability Mds: Mitigation; Clear CPU buffers; SMT disabled Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, RSB fil ling Vulnerability Srbds: Vulnerable: No microcode Vulnerability Tsx async abort: Mitigation; Clear CPU buffers; SMT disabled Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse3 6 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb r dtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopolog y 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 3dnow prefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_s hadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle a vx2 smep bmi2 erms invpcid rtm 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 |
This task depends upon
Closed by Christian Hesse (eworm)
Tuesday, 16 June 2020, 19:22 GMT
Reason for closing: Fixed
Additional comments about closing: intel-ucode 20200616-1
Tuesday, 16 June 2020, 19:22 GMT
Reason for closing: Fixed
Additional comments about closing: intel-ucode 20200616-1
Just to make sure: This happens between 50% and 75% of the times the system is rebooted. Does it happen when system is cold booted (after power off)?
I started the pc till the sddm greeter was displayed and from them I rebooted or shut down the pc without logging in to the system.
With the latest intel-ucode the shutdown failed once every ten tests.
Reboot failed 4 times.
Is it a correct way to do the testing or do I have to log in to better simulate the normal way of doing things?
Moreover, a pair of weeks ago I had to remove the battery from my laptop and I'm waiting for a new one.
Can the absence of the battery affect the boot process at that stage (well after loading the BIOS)?
Is there a way to log what is happening so that to discover what is happening?
Can you verify?
Can I download the PKGUILD and compile it by myself or do you need me to install the one in testing?
pacman -U https://www.archlinux.org/packages/testing/any/intel-ucode/download/
I made about 10 reboots and 10 shutdowns and in both cases it only failed once and both times it was when I selected the grub choice as soon as it appeared on the screen (I do not if this is relevant or not).
So the testing package partially solves the issue, but it still happens though more rarely.
So if it fails now every now and then it also did before. Thus closing.