AW: [REGRESSION] x86/microcode: boot hangs bringing up first secondary CPU on i7-6700HQ, avoided by dis_ucode_ldr
From: Dario Ackermann
Date: Wed Nov 11 2026 - 04:49:33 EST
> Ok, so I don't understand: which kernel did work fine, without any cmdline
> switches?
>
> Pls send full dmesg from that one. IOW, did any kernel at all load microcode
> successfully on your machine?
6.1, and yes. I had only tested the Manjaro build before. Vanilla 6.1.189
also updates early to 0xf0 and brings up all eight CPUs
https://drop.ackd.xyz/n552vx/dmesg-6.1.189.txt
Not perfect either: ~1 boot in 10 black-screens, as in my first mail.
Second case, from that same mail: 6.18.55 with maxcpus=1, then onlining
CPUs 1-7 from sysfs, leaves all eight on 0xf0. Log for that:
https://drop.ackd.xyz/n552vx/dmesg-6.18.55-maxcpus1.txt
> Also, send one from 7.4 with dis_ucode_ldr on the cmdline.
https://drop.ackd.xyz/n552vx/dmesg-7.4.0-rc2-dis_ucode_ldr.txt
Boots all eight CPUs on the firmware revision:
[ 0.000000] x86/CPU: Running old microcode
> Also, check whether you're running the latest microcode packages by updating
> your distro blobs.
intel-ucode 20260925-1, newest available for manjaro at that point. 0xf0
(2021-11-12) is the latest for signature 0x506e3, pf 0x20.
> And put your reply under the text you're replying to, like I just did.
Done.
Both kernels are vanilla (v7.4-rc2 at 7475ea8b5861, 6.1.189 from
kernel.org), rebuilt with NVMe, ext4 and console built in so they reach
userspace.
My best suspicion at the current time is that it is related to SMP startup and
that disabling the microcode loader prevents a (firmware?) race there.
Dario