dasharo-issues
dasharo-issues copied to clipboard
Dasharo
Hangs during microcode update
Component
Dasharo firmware
Device
Protectli VP4670
Dasharo version
v1.2.0
Dasharo Tools Suite version
No response
Test case ID
No response
Brief summary
Trying to boot to Qubes OS on Protectli VP4670 sometimes fails. In few attempts I haven't noticed any correlation between boots from S5, G3 or reboots, each of them can boot and each of them can hang. The platform automatically reboots after 5 minutes or so (watchdog?), after which it may hang again.
How reproducible
30-40% (or 100% with Ubuntu, see next comment)
How to reproduce
Install Qubes OS (tested with version 4.2.3), try to boot few times.
Expected behavior
System boots every time.
Actual behavior
Every now and then, Xen hangs during microcode updates, between the cores, always on CPU#4 (output with cpuinfo sync_console appended to Xen cmdline):
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) alt table ffff82d040423f50 -> ffff82d0404333c4
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 12288K
(XEN) CPU1: Thermal monitoring enabled (TM1)
(XEN) CPU1: Intel(R) Core(TM) i7-10810U CPU @ 1.10GHz stepping 00
(XEN) Booting processor 2/2 eip 90000
(XEN) Initializing CPU#2
(XEN) microcode: CPU2 updated from revision 0xf8 to 0xfe, date = 2024-02-01
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 12288K
(XEN) CPU2: TSC: ratio: 134 / 2
(XEN) CPU2: bus: 100 MHz base: 1600 MHz max: 4900 MHz
(XEN) CPU2: 400 ... 1600 MHz
(XEN) CPU2: Thermal monitoring enabled (TM1)
(XEN) CPU2: Intel(R) Core(TM) i7-10810U CPU @ 1.10GHz stepping 00
(XEN) Booting processor 3/3 eip 90000
(XEN) Initializing CPU#3
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 12288K
(XEN) CPU3: Thermal monitoring enabled (TM1)
(XEN) CPU3: Intel(R) Core(TM) i7-10810U CPU @ 1.10GHz stepping 00
(XEN) Booting processor 4/4 eip 90000
(XEN) Initializing CPU#4
Screenshots
No response
Additional context
If it boots, there are many AER errors reported periodically for Atheros WiFi card:
[ 359.976231] pcieport 0000:00:1d.3: AER: Corrected error message received from 0000:07:00.0
[ 359.985797] pciback 0000:07:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
[ 359.985803] pciback 0000:07:00.0: device [168c:003e] error status/mask=00000080/00006000
[ 359.985810] pciback 0000:07:00.0: [ 7] BadDLLP
[ 377.551307] pcieport 0000:00:1d.3: AER: Multiple Corrected error message received from 0000:07:00.0
[ 377.561712] pciback 0000:07:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 377.572575] pciback 0000:07:00.0: device [168c:003e] error status/mask=00000001/00006000
[ 377.582115] pciback 0000:07:00.0: [ 0] RxErr (First)
[ 392.169316] pcieport 0000:00:1d.3: AER: Corrected error message received from 0000:07:00.0
[ 392.178804] pciback 0000:07:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
[ 392.189736] pciback 0000:07:00.0: device [168c:003e] error status/mask=00000080/00006000
[ 392.189738] pciback 0000:07:00.0: [ 7] BadDLLP
We've had issues with this card earlier, but it is unclear if this may be related.
Solutions you've tried
ucode=no-scan seems to help. I haven't tried changing smp option.
Removing that WiFi card didn't help, other than making AER logs disappear.
The same happens with Ubuntu 24.04.2, but with 100% reproduction rate, as far as I can tell. Adding dis_ucode_ldr to the command line allows the platform to boot. I've updated the title since it is clearly independent of Xen.
Do we know when this ucode was released / added to the OSes? I am wondering if there are no issues since no one has hit it yet due to it's being too recent, or other factos.
This would be https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/main/releasenote.md#microcode-20240813. There is an interesting entry in the links pointing to 341079-021:
According to the revision history, it was added in May 2024, but there is no information whether it was added as fixed or changed later. In my case it hangs on update from 0xf8 to 0xfe, but in logs provided by @miczyg1 the same happens when updating from 0xfa.
Related issue: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/70
This would be https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/main/releasenote.md#microcode-20240813. There is an interesting entry in the links pointing to 341079-021:
According to the revision history, it was added in May 2024, but there is no information whether it was added as fixed or changed later. In my case it hangs on update from 0xf8 to 0xfe, but in logs provided by @miczyg1 the same happens when updating from 0xfa.
Related issue: intel/Intel-Linux-Processor-Microcode-Data-Files#70
OMG. So basically OS update (containing new microcode) can blow everything up...
@krystian-hebel it may mean that updating the microcode to the latest version on firmware side is the only workaround for this problem (not our fault it seems).
Do we need any input from @andyhhp and/or @marmarek. Maybe they can suggest how we should deal with such situations?
To confirm, this a Core i7-10810U Comet Lake 6-core system. Revision 0xf8 is the one in FIT, and attempting to load 0xfa or 0xfe is unstable (with varying incident rates) and for both Xen and Linux, disabling early microcode loading mitigates the hang?
The hang being reliably on core 4 (if it occurs) is certainly bizarre.
What's the exact model/stepping? Xen prints it earlier on boot, or you can get it from head /proc/cpuinfo.
This is a Comet Lake. You want the other documented called "10th Generation Core Processor Specification Update", because the screenshots are from IceLake and are not applicable here (yes, there are two different things called 10th Generation Core, for reasons best explained by the Intel marketing department). Anyway, it's doc #613849 I think.
Are you sure 0xfe is a revision used here? I can't find any such revision for CML, and 0xfc would make more sense in this context. Nevertheless, I can't find an errata which seems to match ICL088 == TGL068 == ADL075 here, so I'm not sure the identified issue#70 is relevant.
To confirm, this a
Core i7-10810UComet Lake 6-core system. Revision0xf8is the one in FIT, and attempting to load0xfaor0xfeis unstable (with varying incident rates) and for both Xen and Linux, disabling early microcode loading mitigates the hang?The hang being reliably on core 4 (if it occurs) is certainly bizarre.
What's the exact model/stepping? Xen prints it earlier on boot, or you can get it from
head /proc/cpuinfo.
It will be either 0x000A0661 or 0x000A0660, depending on the VP4670 HW revision. The production switched from CML-U62 V1 to CML-U62 V2 I think or vice versa. I can't remember now. That said, the log may come from either of those two versions of CPU, because we have old and new revisions of the HW.
This is a Comet Lake. You want the other documented called "10th Generation Core Processor Specification Update", because the screenshots are from IceLake and are not applicable here (yes, there are two different things called 10th Generation Core, for reasons best explained by the Intel marketing department). Anyway, it's doc #613849 I think.
Yes, I checked the CML spec update and there is no such issue/errata. But can we be 100% sure that it is not affecting CML? I have been running the Xen with AEM just fine, till I updated the AEM packages to newer version. Firmware was not changed at all.
Are you sure
0xfeis a revision used here? I can't find any such revision for CML, and0xfcwould make more sense in this context. Nevertheless, I can't find an errata which seems to matchICL088 == TGL068 == ADL075here, so I'm not sure the identified issue#70 is relevant.
coreboot should be built with 0xf8, that's for sure. However, I have no idea what is attempted to be loaded. Simply pasted the log from serial. I can check later what microcode lies on the rootfs.
BTW there is 0xfe ucode: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240813 (for the CPUID 0x000A0660)
(with varying incident rates) and for both Xen and Linux
For me it failed 100% of times with Linux, but maybe I was just lucky.
The hang being reliably on core 4 (if it occurs) is certainly bizarre.
Indeed, I was suspecting something fishy with ACPI/APIC core IDs, but they seem to match and be in correct order. Maybe it hangs reliably on core 4 because earlier core (first non-BSP updated) hangs on some further instruction (mwait or another hlt)? The point of hang doesn't change with or without additional output printed by use of cpuinfo, though.
That said, the log may come from either of those two versions of CPU, because we have old and new revisions of the HW.
Are we seeing the same behaviour on both, or just one? Are they running the same firmware, or different?
It's very important that we separate testing to narrow this down.
BTW there is 0xfe ucode
Great, that's not in the relevant document.
But can we be 100% sure that it is not affecting CML?
No, but Comet Lake is a Skylake-derived core design. Ice Lake is a different "tock", and has Sunny Cove cores. Despite both being branded 10th Generation, they're quite different in ways that will be relevant for microcode.
till I updated the AEM packages to newer version
What exactly changed? I'm guessing the microcode package at a minimum?
If you've not read it already, https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/best-practices/microcode-update-guidance.html is interesting, but what it doesn't say very well is that behaviours change wildly based on ACMs such as MCHECK.
Microcodes in Intel-Linux-Processor-Microcode-Data-Files ought to be safe for OS loading, but that doesn't mean they're bug free.
Maybe it hangs reliably on core 4 because earlier core (first non-BSP updated) hangs on some further instruction (mwait or another hlt)? The point of hang doesn't change with or without additional output printed by use of cpuinfo, though.
I don't know what you mean by core 4 being the first non-BSP core. Xen should bring CPUs up in APIC_ID order, after having undone the DOS-isms in the MADT.
But, you're saying that other cores hang on different instructions? Do you have any more info on that?
I don't know what you mean by core 4 being the first non-BSP core. Xen should bring CPUs up in APIC_ID order, after having undone the DOS-isms in the MADT.
No, no, what I meant was that it hangs after printing a line about CPU 4, but that doesn't necessarily mean that it is core 4 that causes the hang, it could be one of the final "go to sleep" instructions on CPU 2. IIUC CPU 2 gives go ahead signal to BSP before it goes fully idle, maybe this is just enough time for it to print the next line. Then again, this is UART, so it is unlikely that full line would be printed in the time it takes the other core to halt.
Are we seeing the same behaviour on both, or just one? Are they running the same firmware, or different?
The firmware binary is the same, but there are slight differences in the initialization flow. One is the microcode, obviously. Second is that CML v1 and v2 have a bit different memory controllers. Because of that they use a separate FSP binary to handle whole Intel-specific silicon initialization. We have two FSP binaries inside one firmware image to handle any of those two CPU versions.
I have confirmed that the issue was initially created based on results from CPU 0x000a0660 (which also worked flawlessly before)
What exactly changed? I'm guessing the microcode package at a minimum?
Not sure if this will help but I simply installed these packages (with AEM modifications):
python3-xen \
xen \
xen-hypervisor \
xen-libs \
xen-licenses \
xen-runtime \
grub2-common \
grub2-pc \
grub2-pc-modules \
grub2-tools \
grub2-tools-minimal
During testing of various firmware versions on Ubuntu 24.04.02 (6.11.0.19-generic) and 24.04.01(6.8.0-41-generic) I consistently got boot hangs with the 1.2.0 release, which contains 0xF8 version of microcode. Dasharo built from https://github.com/Dasharo/coreboot/actions/runs/13904286942 with 0xFE ucode seems to boot, but it is unstable and crashes randomly after few minutes.
With AMI FW, which holds older version 0xE0, no hangs occur when updating, and builing custom dasharo rom with this ucode also boots into mentioned OSes.
What was surprising, updating Ubuntu 24.04.02 or 24.04.02 with 6.11.0.21-generic kernel no longer hangs the OS on with the 1.2.0 version of dasharo, with 0xF8 microcode.
Dasharo FW on 6.11.0.21-generic kernel
ubuntu@3mdeb:~$ sudo dmesg | grep microcode
[sudo] password for ubuntu:
[ 3.079318] microcode: Current revision: 0x000000fc
[ 3.084242] microcode: Updated early from: 0x000000f8
AMI FW
[ 5.202841] microcode: Current revision: 0x000000fc
[ 5.207758] microcode: Updated early from: 0x000000c6
During testing of various firmware versions on Ubuntu 24.04.02 (6.11.0.19-generic) and 24.04.01(6.8.0-41-generic) I consistently got boot hangs with the 1.2.0 release, which contains 0xF8 version of microcode. Dasharo built from https://github.com/Dasharo/coreboot/actions/runs/13904286942 with 0xFE ucode seems to boot, but it is unstable and crashes randomly after few minutes.
With AMI FW, which holds older version 0xE0, no hangs occur when updating, and builing custom dasharo rom with this ucode also boots into mentioned OSes.
What was surprising, updating Ubuntu 24.04.02 or 24.04.02 with 6.11.0.21-generic kernel no longer hangs the OS on with the 1.2.0 version of dasharo, with 0xF8 microcode.
Dasharo FW on 6.11.0.21-generic kernel
ubuntu@3mdeb:~$ sudo dmesg | grep microcode [sudo] password for ubuntu: [ 3.079318] microcode: Current revision: 0x000000fc [ 3.084242] microcode: Updated early from: 0x000000f8AMI FW
[ 5.202841] microcode: Current revision: 0x000000fc [ 5.207758] microcode: Updated early from: 0x000000c6
Something is not right here. If AMI has ucode 0xE0, then why Linux prints 0xC6?
Something is not right here. If AMI has ucode 0xE0, then why Linux prints 0xC6?
I am not sure. All these codes where verified with CPU-Z, and uefiextract. For Dasharo branded firmware, CPU-Z, uefiextract, and dmesg show consistent revision. For AMI, CPU-Z differs from what Linux and UEFI Extract show, but what is the reason for this I am not sure. 0xE0 seems consistent with Microsoft's distribution too
@SebastianCzapla CPU-Z is run on Windows, so it may update with different microcode than Linux... Also why did we even check Windows in the first place?
If you cannot provide provide precise and consistent information I will be forced to repeat evrything you have done so far and gather informatiom myself...
@BeataZdunczyk cc
Dasharo with AMI UCode transplant
Build from dasharo branch of coreboot
(last commit ce6bf5a0d6bf145d2cae55758b2853e3d8c4caf5)
Platform v4670 v2, cpuid: eax=0x000a0661 (ucode 0xc6)
6.11.0-21:
Coldboot after flashing: Hangs for next 3 boot attempts
Loading Linux 6.11.0-21-generic ...Loading Linux 6.11.0-21-generic ...
Loading initial ramdisk ...Loading initial ramdisk ...
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
Reboot into recovery mode, then proceed with normal boot: no hang, no microcode update in dmesg
ubuntu@3mdeb:~$ sudo dmesg | grep microcode
[sudo] password for ubuntu:
[ 1.802653] MMIO Stale Data: Vulnerable: Clear CPU buffers attempted, no microcode
[ 1.803649] SRBDS: Vulnerable: No microcode
[ 1.804649] GDS: Vulnerable: No microcode
Did not hang for 5 next reboots, dmesg shows UCode update
ubuntu@3mdeb:~$ sudo dmesg | grep microcode
[sudo] password for ubuntu:
[ 3.367761] microcode: Current revision: 0x000000fc
[ 3.372682] microcode: Updated early from: 0x000000c6
Occasionally hangs after reboot in the same fashion as it did after coldboot, with low repro rate, ~15%
6.11.0-19:
After coldboot: every time hangs or fails, no successful boot (log below) More or less 50/50 split over 8 runs I think
Loading Linux 6.11.0-19-generic ...Loading Linux 6.11.0-19-generic ...
Loading initial ramdisk ...Loading initial ramdisk ...
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
Or manages to get past only to get stuck on:
boot log
Loading Linux 6.11.0-19-generic ...Loading Linux 6.11.0-19-generic ...Loading initial ramdisk ...Loading initial ramdisk ...
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
[ 0.000000] Linux version 6.11.0-19-generic (buildd@lcy02-amd64-014) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #19~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Feb 17 11:51:52 UTC 2 (Ubuntu 6.11.0-19.19~24.04.1-generic 6.11.11)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic root=UUID=bbe39a81-c156-427b-a416-ffc6690acd3d ro console=ttyS0,115200n8 console=ttyS0,115200n8
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Hygon HygonGenuine
[ 0.000000] Centaur CentaurHauls
[ 0.000000] zhaoxin Shanghai
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000001000-0x000000000009ffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000096a50fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000096a51000-0x0000000096a5ffff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x0000000096a60000-0x0000000096d5afff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000096d5b000-0x0000000096da8fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000096da9000-0x0000000096dabfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x0000000096dac000-0x0000000096dadfff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000096dae000-0x0000000096daefff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000096daf000-0x0000000097ffbfff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000097ffc000-0x0000000097ffcfff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000097ffd000-0x000000009801dfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000009801e000-0x000000009801ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000098020000-0x0000000098123fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098124000-0x0000000098133fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000098134000-0x0000000098152fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098153000-0x0000000098162fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000098163000-0x0000000098a05fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098a06000-0x0000000098a0dfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000098a0e000-0x0000000098a88fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098a89000-0x0000000098a8bfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x0000000098a8c000-0x0000000098acbfff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098acc000-0x0000000098ad1fff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x0000000098ad2000-0x0000000098adffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098ae0000-0x0000000098ae4fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000098ae5000-0x0000000098aeafff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098aeb000-0x0000000098b03fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000098b04000-0x0000000098b2efff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098b2f000-0x0000000098b3ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000098b40000-0x0000000098b92fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098b93000-0x0000000098b93fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000098b94000-0x0000000098bdcfff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098bdd000-0x0000000098bdefff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000098bdf000-0x0000000098c5afff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000098c5b000-0x0000000098c5efff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000098c5f000-0x00000000992adfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000992ae000-0x00000000993f1fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000993f2000-0x00000000993f5fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000993f6000-0x00000000993fdfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000993fe000-0x000000009983efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000009983f000-0x000000009f7fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff620000-0x00000000ff65ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000085e7fffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] APIC: Static calls initialized
[ 0.000000] efi: EFI v2.8 by EDK II
[ 0.000000] efi: SMBIOS=0x9932e000 SMBIOS 3.0=0x98bdd000 ACPI=0x993fd000 ACPI 2.0=0x993fd014 TPMFinalLog=0x98a06000 MEMATTR=0x96ecf698 MOKvar=0x96dae000 INITRD=0x96db2698 RNG=0x96dab018 TPMEventLog=0x96a51018
[ 0.000000] random: crng init done
[ 0.000000] efi: Remove mem117: MMIO range=[0xff620000-0xff65ffff] (0MB) from e820 map
[ 0.000000] SMBIOS 3.3.0 present.
[ 0.000000] DMI: Protectli VP4670/VP4670, BIOS Dasharo (coreboot+UEFI) v1.2.0 04/10/2025
[ 0.000000] DMI: Memory slots populated: 2/2
[ 0.000000] secureboot: Secure boot disabled
[ 0.000000] tsc: Detected 1600.000 MHz processor
[ 0.000000] tsc: Detected 1599.960 MHz TSC
[ 0.000024] last_pfn = 0x85e800 max_arch_pfn = 0x400000000
[ 0.000027] MTRR map: 6 entries (3 fixed + 3 variable; max 23), built from 10 variable MTRRs
[ 0.000029] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
[ 0.000426] last_pfn = 0x9983f max_arch_pfn = 0x400000000
[ 0.006094] Using GB pages for direct mapping
[ 0.010392] secureboot: Secure boot disabled
[ 0.010393] RAMDISK: [mem 0x8c35c000-0x8ecf4fff]
[ 0.010481] ACPI: Early table checksum verification disabled
[ 0.010484] ACPI: RSDP 0x00000000993FD014 000024 (v02 COREv4)
[ 0.010487] ACPI: XSDT 0x00000000993FC0E8 000074 (v01 COREv4 COREBOOT 00000000 01000013)
[ 0.010492] ACPI: FACP 0x00000000993F8000 000114 (v06 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010497] ACPI: DSDT 0x00000000993F9000 00237F (v02 COREv4 COREBOOT 20110725 INTL 20230628)
[ 0.010499] ACPI: FACS 0x00000000993F5000 000040
[ 0.010501] ACPI: FACS 0x00000000993F5000 000040
[ 0.010504] ACPI: SSDT 0x0000000098ACC000 002971 (v02 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010506] ACPI: MCFG 0x00000000993F7000 00003C (v01 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010509] ACPI: TPM2 0x00000000993F6000 00004C (v04 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010511] ACPI: LPIT 0x0000000098AD1000 000094 (v00 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010513] ACPI: APIC 0x0000000098AD0000 0000B2 (v03 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010516] ACPI: SPCR 0x0000000098ACF000 000058 (v04 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010519] ACPI: WDAT 0x0000000098A8B000 000104 (v01 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010521] ACPI: DMAR 0x0000000098A8A000 000088 (v01 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010524] ACPI: HPET 0x0000000098A89000 000038 (v01 COREv4 COREBOOT 00000000 CORE 20230628)
[ 0.010526] ACPI: Reserving FACP table memory at [mem 0x993f8000-0x993f8113]
[ 0.010527] ACPI: Reserving DSDT table memory at [mem 0x993f9000-0x993fb37e]
[ 0.010528] ACPI: Reserving FACS table memory at [mem 0x993f5000-0x993f503f]
[ 0.010529] ACPI: Reserving FACS table memory at [mem 0x993f5000-0x993f503f]
[ 0.010529] ACPI: Reserving SSDT table memory at [mem 0x98acc000-0x98ace970]
[ 0.010530] ACPI: Reserving MCFG table memory at [mem 0x993f7000-0x993f703b]
[ 0.010531] ACPI: Reserving TPM2 table memory at [mem 0x993f6000-0x993f604b]
[ 0.010532] ACPI: Reserving LPIT table memory at [mem 0x98ad1000-0x98ad1093]
[ 0.010532] ACPI: Reserving APIC table memory at [mem 0x98ad0000-0x98ad00b1]
[ 0.010533] ACPI: Reserving SPCR table memory at [mem 0x98acf000-0x98acf057]
[ 0.010534] ACPI: Reserving WDAT table memory at [mem 0x98a8b000-0x98a8b103]
[ 0.010535] ACPI: Reserving DMAR table memory at [mem 0x98a8a000-0x98a8a087]
[ 0.010535] ACPI: Reserving HPET table memory at [mem 0x98a89000-0x98a89037]
[ 0.010784] No NUMA configuration found
[ 0.010785] Faking a node at [mem 0x0000000000000000-0x000000085e7fffff]
[ 0.010793] NODE_DATA(0) allocated [mem 0x85e7d5000-0x85e7fffff]
[ 0.010966] Zone ranges:
[ 0.010967] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.010969] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
[ 0.010970] Normal [mem 0x0000000100000000-0x000000085e7fffff]
[ 0.010971] Device empty
[ 0.010972] Movable zone start for each node
[ 0.010974] Early memory node ranges
[ 0.010974] node 0: [mem 0x0000000000001000-0x000000000009ffff]
[ 0.010976] node 0: [mem 0x0000000000100000-0x0000000096a50fff]
[ 0.010977] node 0: [mem 0x0000000096d5b000-0x0000000096da8fff]
[ 0.010977] node 0: [mem 0x0000000096dac000-0x0000000096dadfff]
[ 0.010978] node 0: [mem 0x0000000096daf000-0x0000000097ffbfff]
[ 0.010979] node 0: [mem 0x0000000097ffd000-0x000000009801dfff]
[ 0.010980] node 0: [mem 0x0000000098020000-0x0000000098123fff]
[ 0.010980] node 0: [mem 0x0000000098134000-0x0000000098152fff]
[ 0.010981] node 0: [mem 0x0000000098163000-0x0000000098a05fff]
[ 0.010982] node 0: [mem 0x0000000098a0e000-0x0000000098a88fff]
[ 0.010983] node 0: [mem 0x0000000098a8c000-0x0000000098acbfff]
[ 0.010983] node 0: [mem 0x0000000098ad2000-0x0000000098adffff]
[ 0.010984] node 0: [mem 0x0000000098ae5000-0x0000000098aeafff]
[ 0.010985] node 0: [mem 0x0000000098b04000-0x0000000098b2efff]
[ 0.010985] node 0: [mem 0x0000000098b40000-0x0000000098b92fff]
[ 0.010986] node 0: [mem 0x0000000098b94000-0x0000000098bdcfff]
[ 0.010987] node 0: [mem 0x0000000098bdf000-0x0000000098c5afff]
[ 0.010987] node 0: [mem 0x0000000098c5f000-0x00000000992adfff]
[ 0.010988] node 0: [mem 0x00000000993fe000-0x000000009983efff]
[ 0.010989] node 0: [mem 0x0000000100000000-0x000000085e7fffff]
[ 0.010992] Initmem setup node 0 [mem 0x0000000000001000-0x000000085e7fffff]
[ 0.010997] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.011014] On node 0, zone DMA: 96 pages in unavailable ranges
[ 0.013882] On node 0, zone DMA32: 778 pages in unavailable ranges
[ 0.013883] On node 0, zone DMA32: 3 pages in unavailable ranges
[ 0.013902] On node 0, zone DMA32: 1 pages in unavailable ranges
[ 0.013903] On node 0, zone DMA32: 1 pages in unavailable ranges
[ 0.013905] On node 0, zone DMA32: 2 pages in unavailable ranges
[ 0.013906] On node 0, zone DMA32: 16 pages in unavailable ranges
[ 0.013914] On node 0, zone DMA32: 16 pages in unavailable ranges
[ 0.013916] On node 0, zone DMA32: 8 pages in unavailable ranges
[ 0.013916] On node 0, zone DMA32: 3 pages in unavailable ranges
[ 0.013917] On node 0, zone DMA32: 6 pages in unavailable ranges
[ 0.013918] On node 0, zone DMA32: 5 pages in unavailable ranges
[ 0.013919] On node 0, zone DMA32: 25 pages in unavailable ranges
[ 0.013920] On node 0, zone DMA32: 17 pages in unavailable ranges
[ 0.013921] On node 0, zone DMA32: 1 pages in unavailable ranges
[ 0.013922] On node 0, zone DMA32: 2 pages in unavailable ranges
[ 0.013929] On node 0, zone DMA32: 4 pages in unavailable ranges
[ 0.013937] On node 0, zone DMA32: 336 pages in unavailable ranges
[ 0.044830] On node 0, zone Normal: 26561 pages in unavailable ranges
[ 0.044885] On node 0, zone Normal: 6144 pages in unavailable ranges
[ 0.044901] Reserving Intel graphics memory at [mem 0x9b800000-0x9f7fffff]
[ 0.045171] ACPI: PM-Timer IO Port: 0x1808
[ 0.045177] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[ 0.045224] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-119
[ 0.045226] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[ 0.045228] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.045231] ACPI: Using ACPI (MADT) for SMP configuration information
[ 0.045232] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.045235] ACPI: SPCR: console: uart,io,0x3f8
[ 0.045236] TSC deadline timer available
[ 0.045239] CPU topo: Max. logical packages: 1
[ 0.045240] CPU topo: Max. logical dies: 1
[ 0.045241] CPU topo: Max. dies per package: 1
[ 0.045244] CPU topo: Max. threads per core: 2
[ 0.045245] CPU topo: Num. cores per package: 6
[ 0.045246] CPU topo: Num. threads per package: 12
[ 0.045246] CPU topo: Allowing 12 present CPUs plus 0 hotplug CPUs
[ 0.045281] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.045284] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[ 0.045286] PM: hibernation: Registered nosave memory: [mem 0x96a51000-0x96a5ffff]
[ 0.045286] PM: hibernation: Registered nosave memory: [mem 0x96a60000-0x96d5afff]
[ 0.045288] PM: hibernation: Registered nosave memory: [mem 0x96da9000-0x96dabfff]
[ 0.045290] PM: hibernation: Registered nosave memory: [mem 0x96dae000-0x96daefff]
[ 0.045292] PM: hibernation: Registered nosave memory: [mem 0x97ffc000-0x97ffcfff]
[ 0.045294] PM: hibernation: Registered nosave memory: [mem 0x9801e000-0x9801ffff]
[ 0.045296] PM: hibernation: Registered nosave memory: [mem 0x98124000-0x98133fff]
[ 0.045297] PM: hibernation: Registered nosave memory: [mem 0x98153000-0x98162fff]
[ 0.045299] PM: hibernation: Registered nosave memory: [mem 0x98a06000-0x98a0dfff]
[ 0.045301] PM: hibernation: Registered nosave memory: [mem 0x98a89000-0x98a8bfff]
[ 0.045303] PM: hibernation: Registered nosave memory: [mem 0x98acc000-0x98ad1fff]
[ 0.045305] PM: hibernation: Registered nosave memory: [mem 0x98ae0000-0x98ae4fff]
[ 0.045307] PM: hibernation: Registered nosave memory: [mem 0x98aeb000-0x98b03fff]
[ 0.045309] PM: hibernation: Registered nosave memory: [mem 0x98b2f000-0x98b3ffff]
[ 0.045311] PM: hibernation: Registered nosave memory: [mem 0x98b93000-0x98b93fff]
[ 0.045313] PM: hibernation: Registered nosave memory: [mem 0x98bdd000-0x98bdefff]
[ 0.045315] PM: hibernation: Registered nosave memory: [mem 0x98c5b000-0x98c5efff]
[ 0.045317] PM: hibernation: Registered nosave memory: [mem 0x992ae000-0x993f1fff]
[ 0.045318] PM: hibernation: Registered nosave memory: [mem 0x993f2000-0x993f5fff]
[ 0.045318] PM: hibernation: Registered nosave memory: [mem 0x993f6000-0x993fdfff]
[ 0.045320] PM: hibernation: Registered nosave memory: [mem 0x9983f000-0x9f7fffff]
[ 0.045321] PM: hibernation: Registered nosave memory: [mem 0x9f800000-0xffffffff]
[ 0.045322] [mem 0x9f800000-0xffffffff] available for PCI devices
[ 0.045324] Booting paravirtualized kernel on bare hardware
[ 0.045325] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[ 0.045332] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:12 nr_cpu_ids:12 nr_node_ids:1
[ 0.045929] percpu: Embedded 88 pages/cpu s237568 r8192 d114688 u524288
[ 0.045972] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic root=UUID=bbe39a81-c156-427b-a416-ffc6690acd3d ro console=ttyS0,115200n8 console=ttyS0,115200n8
[ 0.046017] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic", will be passed to user space.
[ 0.048085] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
[ 0.049122] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[ 0.049260] Fallback order for Node 0: 0
[ 0.049263] Built 1 zonelists, mobility grouping on. Total pages: 8354582
[ 0.049264] Policy zone: Normal
[ 0.049269] mem auto-init: stack:all(zero), heap alloc:on, heap free:off
[ 0.049275] software IO TLB: area num 16.
[ 0.113335] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=1
[ 0.113375] ftrace: allocating 59199 entries in 232 pages
[ 0.121709] ftrace: allocated 232 pages with 4 groups
[ 0.122345] Dynamic Preempt: voluntary
[ 0.122418] rcu: Preemptible hierarchical RCU implementation.
[ 0.122419] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=12.
[ 0.122420] Trampoline variant of Tasks RCU enabled.
[ 0.122420] Rude variant of Tasks RCU enabled.
[ 0.122421] Tracing variant of Tasks RCU enabled.
[ 0.122421] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[ 0.122422] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=12
[ 0.122431] RCU Tasks: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=12.
[ 0.122433] RCU Tasks Rude: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=12.
[ 0.122434] RCU Tasks Trace: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=12.
[ 0.124934] NR_IRQS: 524544, nr_irqs: 2152, preallocated irqs: 16
[ 0.125234] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.125579] Console: colour dummy device 80x25
[ 0.125619] printk: legacy console [ttyS0] enabled
[ 1.623200] ACPI: Core revision 20240322
[ 1.627402] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns
[ 1.636694] APIC: Switch to symmetric I/O mode setup
[ 1.641801] DMAR: Host address width 39
[ 1.645759] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 1.651223] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
[ 1.659808] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 1.665253] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 1.673323] DMAR: RMRR base: 0x0000009b000000 end: 0x0000009f7fffff
[ 1.679729] DMAR-IR: IOAPIC id 0 under DRHD base 0xfed91000 IOMMU 1
[ 1.686228] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 1.691754] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 1.703647] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 1.709082] x2apic enabled
[ 1.711925] APIC: Switched APIC routing to: cluster x2apic
[ 1.725001] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 1.736073] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x170fff30cc4, max_idle_ns: 440795237869 ns
[ 1.746654] Calibrating delay loop (skipped), value calculated using timer frequency.. 3199.92 BogoMIPS (lpj=1599960)
[ 1.747671] x86/cpu: SGX disabled by BIOS.
[ 1.748657] CPU0: Thermal monitoring enabled (TM1)
[ 1.749698] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[ 1.750653] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[ 1.751654] process: using mwait in idle threads
[ 1.752654] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[ 1.753654] Spectre V2 : Spectre BHI mitigation: SW BHB clearing on syscall and VM exit
[ 1.754653] Spectre V2 : Mitigation: Enhanced / Automatic IBRS
[ 1.755653] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[ 1.756653] Spectre V2 : Spectre v2 / PBRSB-eIBRS: Retire a single CALL on VMEXIT
[ 1.757653] RETBleed: Mitigation: Enhanced IBRS
[ 1.758653] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[ 1.759653] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
[ 1.760656] MMIO Stale Data: Mitigation: Clear CPU buffers
[ 1.761653] SRBDS: Mitigation: Microcode
[ 1.762653] GDS: Mitigation: Microcode
[ 1.763657] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 1.764653] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 1.765653] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 1.766653] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ 1.767653] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 1.768653] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
[ 1.769653] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 1.770653] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 1.771653] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 1.772653] x86/fpu: xstate_offset[9]: 960, xstate_sizes[9]: 8
[ 1.773653] x86/fpu: Enabled xstate features 0x21f, context size is 968 bytes, using 'compacted' format.
[ 1.798262] Freeing SMP alternatives memory: 48K
[ 1.798654] pid_max: default: 32768 minimum: 301
[ 1.801570] LSM: initializing lsm=lockdown,capability,landlock,yama,apparmor,ima,evm
[ 1.801663] landlock: Up and running.
[ 1.802653] Yama: becoming mindful.
[ 1.803682] AppArmor: AppArmor initialized
[ 1.804716] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 1.805678] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 1.806916] smpboot: CPU0: Intel(R) Core(TM) i7-10810U CPU @ 1.10GHz (family: 0x6, model: 0xa6, stepping: 0x1)
[ 1.807797] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
[ 1.808654] ... version: 4
[ 1.809653] ... bit width: 48
[ 1.810653] ... generic registers: 4
[ 1.811653] ... value mask: 0000ffffffffffff
[ 1.812653] ... max period: 00007fffffffffff
[ 1.813653] ... fixed-purpose events: 3
[ 1.814653] ... event mask: 000000070000000f
[ 1.815739] signal: max sigframe size: 3632
[ 1.816662] Estimated ratio of average max frequency by base frequency (times 1024): 2752
[ 1.818928] rcu: Hierarchical SRCU implementation.
[ 1.819653] rcu: Max phase no-delay instances is 400.
[ 1.820681] Timer migration: 2 hierarchy levels; 8 children per group; 2 crossnode level
[ 1.822174] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[ 1.822734] smp: Bringing up secondary CPUs ...
[ 1.823722] smpboot: x86: Booting SMP configuration:
[ 1.824655] .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11
[ 1.831660] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
[ 1.833714] smp: Brought up 1 node, 12 CPUs
[ 1.834654] smpboot: Total of 12 processors activated (38399.04 BogoMIPS)
[ 1.836736] Memory: 32652888K/33418328K available (22528K kernel code, 4518K rwdata, 14876K rodata, 5096K init, 4528K bss, 740832K reserved, 0K cma-reserved)
[ 1.838557] devtmpfs: initialized
[ 1.838683] x86/mm: Memory block size: 128MB
[ 1.841563] ACPI: PM: Registering ACPI NVS region [mem 0x98124000-0x98133fff] (65536 bytes)
[ 1.841655] ACPI: PM: Registering ACPI NVS region [mem 0x98153000-0x98162fff] (65536 bytes)
[ 1.842653] ACPI: PM: Registering ACPI NVS region [mem 0x98a06000-0x98a0dfff] (32768 bytes)
[ 1.843653] ACPI: PM: Registering ACPI NVS region [mem 0x993f2000-0x993f5fff] (16384 bytes)
[ 1.844687] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[ 1.845666] futex hash table entries: 4096 (order: 6, 262144 bytes, linear)
[ 1.846710] pinctrl core: initialized pinctrl subsystem
[ 1.847922] PM: RTC time: 13:08:12, date: 2025-04-16
[ 1.849023] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 1.849917] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations
[ 1.850851] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 1.851841] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 1.852666] audit: initializing netlink subsys (disabled)
[ 1.853678] audit: type=2000 audit(1744808890.129:1): state=initialized audit_enabled=0 res=1
[ 1.853761] thermal_sys: Registered thermal governor 'fair_share'
[ 1.854654] thermal_sys: Registered thermal governor 'bang_bang'
[ 1.855653] thermal_sys: Registered thermal governor 'step_wise'
[ 1.856653] thermal_sys: Registered thermal governor 'user_space'
[ 1.857653] thermal_sys: Registered thermal governor 'power_allocator'
[ 1.858659] EISA bus registered
[ 1.860657] cpuidle: using governor ladder
[ 1.861654] cpuidle: using governor menu
[ 1.862681] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 1.863747] PCI: ECAM [mem 0xe0000000-0xefffffff] (base 0xe0000000) for domain 0000 [bus 00-ff]
[ 1.864662] PCI: Using configuration type 1 for base access
[ 1.865722] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[ 1.866751] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 1.867655] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
[ 1.868653] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 1.869653] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
[ 1.870728] ACPI: Added _OSI(Module Device)
[ 1.871657] ACPI: Added _OSI(Processor Device)
[ 1.872653] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 1.873653] ACPI: Added _OSI(Processor Aggregator Device)
[ 1.876034] ACPI: 2 ACPI AML tables successfully acquired and loaded
[ 1.877762] ACPI: Interpreter enabled
[ 1.878662] ACPI: PM: (supports S0 S3 S4 S5)
[ 1.879654] ACPI: Using IOAPIC for interrupt routing
[ 1.880780] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 1.881653] PCI: Ignoring E820 reservations for host bridge windows
[ 1.886466] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 1.892660] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[ 1.901681] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR DPC]
[ 1.912110] PCI host bridge to bus 0000:00
[ 1.915655] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
[ 1.922653] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
[ 1.929653] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000fffff window]
[ 1.936653] pci_bus 0000:00: root bus resource [mem 0x9f800000-0xdfffffff window]
[ 1.944653] pci_bus 0000:00: root bus resource [mem 0x85e800000-0x7fffffffff window]
[ 1.952653] pci_bus 0000:00: root bus resource [mem 0xfc800000-0xfe7fffff window]
[ 1.959653] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed47fff window]
[ 1.967653] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 1.972677] pci 0000:00:00.0: [8086:9b51] type 00 class 0x060000 conventional PCI endpoint
[ 1.980742] pci 0000:00:02.0: [8086:9bcc] type 00 class 0x030000 PCIe Root Complex Integrated Endpoint
[ 1.990659] pci 0000:00:02.0: BAR 0 [mem 0xb0000000-0xb0ffffff 64bit]
[ 1.996657] pci 0000:00:02.0: BAR 2 [mem 0xa0000000-0xafffffff 64bit pref]
[ 2.003655] pci 0000:00:02.0: BAR 4 [io 0x1000-0x103f]
[ 2.009665] pci 0000:00:02.0: DMAR: Disabling IOMMU for graphics on this chipset
[ 2.016654] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[ 2.024749] pci 0000:00:08.0: [8086:1911] type 00 class 0x088000 conventional PCI endpoint
[ 2.033662] pci 0000:00:08.0: BAR 0 [mem 0x00000000-0x00000fff 64bit]
[ 2.039772] pci 0000:00:12.0: [8086:02f9] type 00 class 0x118000 conventional PCI endpoint
[ 2.048673] pci 0000:00:12.0: BAR 0 [mem 0xb1e16000-0xb1e16fff 64bit]
[ 2.054794] pci 0000:00:14.0: [8086:02ed] type 00 class 0x0c0330 conventional PCI endpoint
[ 2.062669] pci 0000:00:14.0: BAR 0 [mem 0xb1e00000-0xb1e0ffff 64bit]
[ 2.069710] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 2.075736] pci 0000:00:14.2: [8086:02ef] type 00 class 0x050000 conventional PCI endpoint
[ 2.083669] pci 0000:00:14.2: BAR 0 [mem 0x00000000-0x00001fff 64bit]
[ 2.090664] pci 0000:00:14.2: BAR 2 [mem 0x00000000-0x00000fff 64bit]
[ 2.096786] pci 0000:00:17.0: [8086:02d3] type 00 class 0x010601 conventional PCI endpoint
[ 2.105664] pci 0000:00:17.0: BAR 0 [mem 0xb1e14000-0xb1e15fff]
[ 2.111659] pci 0000:00:17.0: BAR 1 [mem 0xb1e1b000-0xb1e1b0ff]
[ 2.116659] pci 0000:00:17.0: BAR 2 [io 0x1060-0x1067]
[ 2.122659] pci 0000:00:17.0: BAR 3 [io 0x1068-0x106b]
[ 2.127659] pci 0000:00:17.0: BAR 4 [io 0x1040-0x105f]
[ 2.132659] pci 0000:00:17.0: BAR 5 [mem 0xb1e1a000-0xb1e1a7ff]
[ 2.138690] pci 0000:00:17.0: PME# supported from D3hot
[ 2.143726] pci 0000:00:1a.0: [8086:02c4] type 00 class 0x080501 conventional PCI endpoint
[ 2.152669] pci 0000:00:1a.0: BAR 0 [mem 0xb1e18000-0xb1e18fff 64bit]
[ 2.158829] pci 0000:00:1c.0: [8086:02bc] type 01 class 0x060400 PCIe Root Port
[ 2.166673] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 2.171657] pci 0000:00:1c.0: bridge window [mem 0x9fa00000-0x9fcfffff]
[ 2.178716] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 2.184679] pci 0000:00:1c.0: PTM enabled (root), 4ns granularity
[ 2.190772] pci 0000:00:1c.5: [8086:02bd] type 01 class 0x060400 PCIe Root Port
[ 2.197672] pci 0000:00:1c.5: PCI bridge to [bus 02]
[ 2.202656] pci 0000:00:1c.5: bridge window [mem 0x9fd00000-0x9fffffff]
[ 2.209714] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[ 2.215679] pci 0000:00:1c.5: PTM enabled (root), 4ns granularity
[ 2.221746] pci 0000:00:1c.6: [8086:02be] type 01 class 0x060400 PCIe Root Port
[ 2.229672] pci 0000:00:1c.6: PCI bridge to [bus 03]
[ 2.234656] pci 0000:00:1c.6: bridge window [mem 0xb1000000-0xb12fffff]
[ 2.241715] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
[ 2.247679] pci 0000:00:1c.6: PTM enabled (root), 4ns granularity
[ 2.253743] pci 0000:00:1c.7: [8086:02bf] type 01 class 0x060400 PCIe Root Port
[ 2.260675] pci 0000:00:1c.7: PCI bridge to [bus 04]
[ 2.265656] pci 0000:00:1c.7: bridge window [mem 0xb1300000-0xb15fffff]
[ 2.272714] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
[ 2.278679] pci 0000:00:1c.7: PTM enabled (root), 4ns granularity
[ 2.285743] pci 0000:00:1d.0: [8086:02b0] type 01 class 0x060400 PCIe Root Port
[ 2.292672] pci 0000:00:1d.0: PCI bridge to [bus 05]
[ 2.297656] pci 0000:00:1d.0: bridge window [mem 0xb1600000-0xb18fffff]
[ 2.304715] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 2.310679] pci 0000:00:1d.0: PTM enabled (root), 4ns granularity
[ 2.316744] pci 0000:00:1d.1: [8086:02b1] type 01 class 0x060400 PCIe Root Port
[ 2.323672] pci 0000:00:1d.1: PCI bridge to [bus 06]
[ 2.328656] pci 0000:00:1d.1: bridge window [mem 0xb1900000-0xb1bfffff]
[ 2.335714] pci 0000:00:1d.1: PME# supported from D0 D3hot D3cold
[ 2.341679] pci 0000:00:1d.1: PTM enabled (root), 4ns granularity
[ 2.348747] pci 0000:00:1d.3: [8086:02b3] type 01 class 0x060400 PCIe Root Port
[ 2.355672] pci 0000:00:1d.3: PCI bridge to [bus 07]
[ 2.360656] pci 0000:00:1d.3: bridge window [mem 0x9f800000-0x9f9fffff]
[ 2.367715] pci 0000:00:1d.3: PME# supported from D0 D3hot D3cold
[ 2.373679] pci 0000:00:1d.3: PTM enabled (root), 4ns granularity
[ 2.379743] pci 0000:00:1d.4: [8086:02b4] type 01 class 0x060400 PCIe Root Port
[ 2.387672] pci 0000:00:1d.4: PCI bridge to [bus 08]
[ 2.392656] pci 0000:00:1d.4: bridge window [mem 0xb1c00000-0xb1cfffff]
[ 2.398714] pci 0000:00:1d.4: PME# supported from D0 D3hot D3cold
[ 2.405679] pci 0000:00:1d.4: PTM enabled (root), 4ns granularity
[ 2.411769] pci 0000:00:1f.0: [8086:0284] type 00 class 0x060100 conventional PCI endpoint
[ 2.419909] pci 0000:00:1f.3: [8086:02c8] type 00 class 0x040300 conventional PCI endpoint
[ 2.428685] pci 0000:00:1f.3: BAR 0 [mem 0xb1e10000-0xb1e13fff 64bit]
[ 2.434700] pci 0000:00:1f.3: BAR 4 [mem 0xb1d00000-0xb1dfffff 64bit]
[ 2.441729] pci 0000:00:1f.3: PME# supported from D3hot D3cold
[ 2.446783] pci 0000:00:1f.4: [8086:02a3] type 00 class 0x0c0500 conventional PCI endpoint
[ 2.455675] pci 0000:00:1f.4: BAR 0 [mem 0xb1e1c000-0xb1e1c0ff 64bit]
[ 2.461678] pci 0000:00:1f.4: BAR 4 [io 0xefa0-0xefbf]
[ 2.467754] pci 0000:00:1f.5: [8086:02a4] type 00 class 0x0c8000 conventional PCI endpoint
[ 2.475670] pci 0000:00:1f.5: BAR 0 [mem 0xfe010000-0xfe010fff]
[ 2.481816] pci 0000:01:00.0: [8086:15f3] type 00 class 0x020000 PCIe Endpoint
[ 2.488674] pci 0000:01:00.0: BAR 0 [mem 0x9fa00000-0x9fafffff]
[ 2.494683] pci 0000:01:00.0: BAR 3 [mem 0x9fc00000-0x9fc03fff]
[ 2.500684] pci 0000:01:00.0: ROM [mem 0x9fb00000-0x9fbfffff pref]
[ 2.507745] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[ 2.513826] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 2.518718] pci 0000:02:00.0: [8086:15f3] type 00 class 0x020000 PCIe Endpoint
[ 2.525673] pci 0000:02:00.0: BAR 0 [mem 0x9fd00000-0x9fdfffff]
[ 2.531683] pci 0000:02:00.0: BAR 3 [mem 0x9ff00000-0x9ff03fff]
[ 2.537683] pci 0000:02:00.0: ROM [mem 0x9fe00000-0x9fefffff pref]
[ 2.543745] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[ 2.550825] pci 0000:00:1c.5: PCI bridge to [bus 02]
[ 2.555718] pci 0000:03:00.0: [8086:15f3] type 00 class 0x020000 PCIe Endpoint
[ 2.562673] pci 0000:03:00.0: BAR 0 [mem 0xb1000000-0xb10fffff]
[ 2.568684] pci 0000:03:00.0: BAR 3 [mem 0xb1200000-0xb1203fff]
[ 2.574683] pci 0000:03:00.0: ROM [mem 0xb1100000-0xb11fffff pref]
[ 2.580745] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 2.586825] pci 0000:00:1c.6: PCI bridge to [bus 03]
[ 2.591718] pci 0000:04:00.0: [8086:15f3] type 00 class 0x020000 PCIe Endpoint
[ 2.599673] pci 0000:04:00.0: BAR 0 [mem 0xb1300000-0xb13fffff]
[ 2.605683] pci 0000:04:00.0: BAR 3 [mem 0xb1500000-0xb1503fff]
[ 2.611683] pci 0000:04:00.0: ROM [mem 0xb1400000-0xb14fffff pref]
[ 2.617745] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
[ 2.623824] pci 0000:00:1c.7: PCI bridge to [bus 04]
[ 2.628720] pci 0000:05:00.0: [8086:15f3] type 00 class 0x020000 PCIe Endpoint
[ 2.636676] pci 0000:05:00.0: BAR 0 [mem 0xb1600000-0xb16fffff]
[ 2.642683] pci 0000:05:00.0: BAR 3 [mem 0xb1800000-0xb1803fff]
[ 2.648684] pci 0000:05:00.0: ROM [mem 0xb1700000-0xb17fffff pref]
[ 2.654746] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
[ 2.660824] pci 0000:00:1d.0: PCI bridge to [bus 05]
[ 2.665715] pci 0000:06:00.0: [8086:15f3] type 00 class 0x020000 PCIe Endpoint
[ 2.672673] pci 0000:06:00.0: BAR 0 [mem 0xb1900000-0xb19fffff]
[ 2.678683] pci 0000:06:00.0: BAR 3 [mem 0xb1b00000-0xb1b03fff]
[ 2.684683] pci 0000:06:00.0: ROM [mem 0xb1a00000-0xb1afffff pref]
[ 2.691745] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
[ 2.697823] pci 0000:00:1d.1: PCI bridge to [bus 06]
[ 2.702771] pci 0000:07:00.0: [168c:003e] type 00 class 0x028000 PCIe Endpoint
[ 2.709739] pci 0000:07:00.0: BAR 0 [mem 0x9f800000-0x9f9fffff 64bit]
[ 2.716945] pci 0000:07:00.0: PME# supported from D0 D3hot D3cold
[ 2.723079] pci 0000:00:1d.3: PCI bridge to [bus 07]
[ 2.728736] pci 0000:08:00.0: [144d:a80a] type 00 class 0x010802 PCIe Endpoint
[ 2.735703] pci 0000:08:00.0: BAR 0 [mem 0xb1c00000-0xb1c03fff 64bit]
[ 2.741899] pci 0000:08:00.0: 31.504 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x4 link at 0000:00:1d.4 (capable of 63.012 Gb/s with 16.0 GT/s PCIe x4 link)
[ 2.757779] pci 0000:00:1d.4: PCI bridge to [bus 08]
[ 2.763667] iommu: Default domain type: Translated
[ 2.768654] iommu: DMA domain TLB invalidation policy: lazy mode
[ 2.774774] SCSI subsystem initialized
[ 2.778672] ACPI: bus type USB registered
[ 2.782663] usbcore: registered new interface driver usbfs
[ 2.787657] usbcore: registered new interface driver hub
[ 2.792657] usbcore: registered new device driver usb
[ 2.798667] pps_core: LinuxPPS API ver. 1 registered
[ 2.803653] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 2.812654] PTP clock support registered
[ 2.816665] EDAC MC: Ver: 3.0.0
[ 2.819851] efivars: Registered efivars operations
[ 2.824826] NetLabel: Initializing
[ 2.828654] NetLabel: domain hash size = 128
[ 2.832654] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 2.838664] NetLabel: unlabeled traffic allowed by default
[ 2.843674] mctp: management component transport protocol core
[ 2.849654] NET: Registered PF_MCTP protocol family
[ 2.854659] PCI: Using ACPI for IRQ routing
[ 2.899663] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[ 2.900652] pci 0000:00:02.0: vgaarb: bridge control possible
[ 2.900652] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[ 2.900656] vgaarb: loaded
[ 2.901689] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 2.902653] hpet0: 8 comparators, 64-bit 24.000000 MHz counter
[ 2.905675] clocksource: Switched to clocksource tsc-early
[ 2.911590] VFS: Disk quotas dquot_6.6.0
[ 2.915554] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.922561] AppArmor: AppArmor Filesystem Enabled
[ 2.927316] pnp: PnP ACPI init
[ 2.930470] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
[ 2.937210] system 00:01: [mem 0xfed10000-0xfed17fff] has been reserved
[ 2.943875] system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
[ 2.950536] system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
[ 2.957189] system 00:01: [mem 0xfed90000-0xfed93fff] could not be reserved
[ 2.964193] system 00:01: [mem 0xff000000-0xffffffff] has been reserved
[ 2.970848] system 00:01: [mem 0xfee00000-0xfeefffff] has been reserved
[ 2.977501] system 00:01: [mem 0xfed00000-0xfed003ff] has been reserved
[ 2.984193] system 00:02: [mem 0xfed00000-0xfed003ff] has been reserved
[ 2.990885] system 00:03: [io 0x1800-0x18fe] could not be reserved
[ 2.997627] ACPI: IRQ 9 override to level(!), high
[ 3.002749] system 00:05: [io 0x0a40-0x0a47] has been reserved
[ 3.008714] system 00:05: [io 0x0a30-0x0a33] has been reserved
[ 3.014721] pnp: PnP ACPI: found 6 devices
[ 3.024272] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 3.033231] NET: Registered PF_INET protocol family
[ 3.038262] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[ 3.056871] tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
[ 3.065644] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 3.073520] TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[ 3.081881] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
[ 3.089486] TCP: Hash tables configured (established 262144 bind 65536)
[ 3.096210] MPTCP token hash table entries: 32768 (order: 7, 786432 bytes, linear)
[ 3.103888] UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
[ 3.110865] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
[ 3.118298] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 3.124003] NET: Registered PF_XDP protocol family
[ 3.128848] pci 0000:00:14.2: BAR 0 [mem 0x85e800000-0x85e801fff 64bit]: assigned
[ 3.136386] pci 0000:00:08.0: BAR 0 [mem 0x85e802000-0x85e802fff 64bit]: assigned
[ 3.143913] pci 0000:00:14.2: BAR 2 [mem 0x85e803000-0x85e803fff 64bit]: assigned
[ 3.151445] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 3.156450] pci 0000:00:1c.0: bridge window [mem 0x9fa00000-0x9fcfffff]
[ 3.163287] pci 0000:00:1c.5: PCI bridge to [bus 02]
[ 3.168285] pci 0000:00:1c.5: bridge window [mem 0x9fd00000-0x9fffffff]
[ 3.175113] pci 0000:00:1c.6: PCI bridge to [bus 03]
[ 3.180111] pci 0000:00:1c.6: bridge window [mem 0xb1000000-0xb12fffff]
[ 3.186943] pci 0000:00:1c.7: PCI bridge to [bus 04]
[ 3.191939] pci 0000:00:1c.7: bridge window [mem 0xb1300000-0xb15fffff]
[ 3.198771] pci 0000:00:1d.0: PCI bridge to [bus 05]
[ 3.203769] pci 0000:00:1d.0: bridge window [mem 0xb1600000-0xb18fffff]
[ 3.210600] pci 0000:00:1d.1: PCI bridge to [bus 06]
[ 3.215598] pci 0000:00:1d.1: bridge window [mem 0xb1900000-0xb1bfffff]
[ 3.222426] pci 0000:00:1d.3: PCI bridge to [bus 07]
[ 3.227423] pci 0000:00:1d.3: bridge window [mem 0x9f800000-0x9f9fffff]
[ 3.234259] pci 0000:00:1d.4: PCI bridge to [bus 08]
[ 3.239263] pci 0000:00:1d.4: bridge window [mem 0xb1c00000-0xb1cfffff]
[ 3.246094] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
[ 3.252316] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
[ 3.258536] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000fffff window]
[ 3.265451] pci_bus 0000:00: resource 7 [mem 0x9f800000-0xdfffffff window]
[ 3.272368] pci_bus 0000:00: resource 8 [mem 0x85e800000-0x7fffffffff window]
[ 3.279548] pci_bus 0000:00: resource 9 [mem 0xfc800000-0xfe7fffff window]
[ 3.286462] pci_bus 0000:00: resource 10 [mem 0xfed40000-0xfed47fff window]
[ 3.293466] pci_bus 0000:01: resource 1 [mem 0x9fa00000-0x9fcfffff]
[ 3.299771] pci_bus 0000:02: resource 1 [mem 0x9fd00000-0x9fffffff]
[ 3.306077] pci_bus 0000:03: resource 1 [mem 0xb1000000-0xb12fffff]
[ 3.312381] pci_bus 0000:04: resource 1 [mem 0xb1300000-0xb15fffff]
[ 3.318689] pci_bus 0000:05: resource 1 [mem 0xb1600000-0xb18fffff]
[ 3.324994] pci_bus 0000:06: resource 1 [mem 0xb1900000-0xb1bfffff]
[ 3.331302] pci_bus 0000:07: resource 1 [mem 0x9f800000-0x9f9fffff]
[ 3.337606] pci_bus 0000:08: resource 1 [mem 0xb1c00000-0xb1cfffff]
[ 3.344471] PCI: CLS 64 bytes, default 64
[ 3.348556] DMAR: No ATSR found
[ 3.348587] Trying to unpack rootfs image as initramfs...
[ 3.351726] DMAR: No SATC found
[ 3.351728] DMAR: dmar1: Using Queued invalidation
[ 3.351800] pci 0000:00:00.0: Adding to iommu group 0
[ 3.370268] pci 0000:00:08.0: Adding to iommu group 1
[ 3.375376] pci 0000:00:12.0: Adding to iommu group 2
[ 3.380481] pci 0000:00:14.0: Adding to iommu group 3
[ 3.385578] pci 0000:00:14.2: Adding to iommu group 3
[ 3.390684] pci 0000:00:17.0: Adding to iommu group 4
[ 3.395786] pci 0000:00:1a.0: Adding to iommu group 5
[ 3.400899] pci 0000:00:1c.0: Adding to iommu group 6
[ 3.406004] pci 0000:00:1c.5: Adding to iommu group 7
[ 3.411117] pci 0000:00:1c.6: Adding to iommu group 8
[ 3.413904] Freeing initrd memory: 42596K
[ 3.416241] pci 0000:00:1c.7: Adding to iommu group 9
[ 3.425360] pci 0000:00:1d.0: Adding to iommu group 10
[ 3.430557] pci 0000:00:1d.1: Adding to iommu group 11
[ 3.435753] pci 0000:00:1d.3: Adding to iommu group 12
[ 3.440943] pci 0000:00:1d.4: Adding to iommu group 13
[ 3.446140] pci 0000:00:1f.0: Adding to iommu group 14
[ 3.451330] pci 0000:00:1f.3: Adding to iommu group 14
[ 3.456513] pci 0000:00:1f.4: Adding to iommu group 14
[ 3.461704] pci 0000:00:1f.5: Adding to iommu group 14
[ 3.466896] pci 0000:01:00.0: Adding to iommu group 15
[ 3.472078] pci 0000:02:00.0: Adding to iommu group 16
[ 3.477272] pci 0000:03:00.0: Adding to iommu group 17
[ 3.482464] pci 0000:04:00.0: Adding to iommu group 18
[ 3.487657] pci 0000:05:00.0: Adding to iommu group 19
[ 3.492870] pci 0000:06:00.0: Adding to iommu group 20
[ 3.498069] pci 0000:07:00.0: Adding to iommu group 21
[ 3.503262] pci 0000:08:00.0: Adding to iommu group 22
[ 3.509666] DMAR: Intel(R) Virtualization Technology for Directed I/O
[ 3.516153] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 3.522631] software IO TLB: mapped [mem 0x0000000091830000-0x0000000095830000] (64MB)
[ 3.531225] Initialise system trusted keyrings
[ 3.535715] Key type blacklist registered
[ 3.539785] workingset: timestamp_bits=36 max_order=23 bucket_order=0
[ 3.546278] zbud: loaded
[ 3.548995] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 3.554928] fuse: init (API version 7.40)
[ 3.559061] integrity: Platform Keyring initialized
[ 3.563983] integrity: Machine keyring initialized
[ 3.577401] Key type asymmetric registered
[ 3.581530] Asymmetric key parser 'x509' registered
[ 3.586453] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[ 3.593923] io scheduler mq-deadline registered
[ 3.598859] pcieport 0000:00:1c.0: PME: Signaling with IRQ 121
[ 3.604783] pcieport 0000:00:1c.0: AER: enabled with IRQ 121
[ 3.610517] pcieport 0000:00:1c.0: DPC: enabled with IRQ 121
[ 3.616213] pcieport 0000:00:1c.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 3.629324] pcieport 0000:00:1c.5: PME: Signaling with IRQ 122
[ 3.635236] pcieport 0000:00:1c.5: AER: enabled with IRQ 122
[ 3.640966] pcieport 0000:00:1c.5: DPC: enabled with IRQ 122
[ 3.646664] pcieport 0000:00:1c.5: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 3.659769] pcieport 0000:00:1c.6: PME: Signaling with IRQ 123
[ 3.665688] pcieport 0000:00:1c.6: AER: enabled with IRQ 123
[ 3.671415] pcieport 0000:00:1c.6: DPC: enabled with IRQ 123
[ 3.677117] pcieport 0000:00:1c.6: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 3.690218] pcieport 0000:00:1c.7: PME: Signaling with IRQ 124
[ 3.696136] pcieport 0000:00:1c.7: AER: enabled with IRQ 124
[ 3.701867] pcieport 0000:00:1c.7: DPC: enabled with IRQ 124
[ 3.707568] pcieport 0000:00:1c.7: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 3.720672] pcieport 0000:00:1d.0: PME: Signaling with IRQ 125
[ 3.726595] pcieport 0000:00:1d.0: AER: enabled with IRQ 125
[ 3.732324] pcieport 0000:00:1d.0: DPC: enabled with IRQ 125
[ 3.738019] pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 3.751107] pcieport 0000:00:1d.1: PME: Signaling with IRQ 126
[ 3.757024] pcieport 0000:00:1d.1: AER: enabled with IRQ 126
[ 3.762749] pcieport 0000:00:1d.1: DPC: enabled with IRQ 126
[ 3.768444] pcieport 0000:00:1d.1: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 3.781531] pcieport 0000:00:1d.3: PME: Signaling with IRQ 127
[ 3.787449] pcieport 0000:00:1d.3: AER: enabled with IRQ 127
[ 3.793176] pcieport 0000:00:1d.3: DPC: enabled with IRQ 127
[ 3.798879] pcieport 0000:00:1d.3: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 3.811981] pcieport 0000:00:1d.4: PME: Signaling with IRQ 128
[ 3.817900] pcieport 0000:00:1d.4: AER: enabled with IRQ 128
[ 3.823627] pcieport 0000:00:1d.4: DPC: enabled with IRQ 128
[ 3.829330] pcieport 0000:00:1d.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 3.842251] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 3.849044] ACPI: \_SB_.CP00: Found 3 idle states
[ 3.854196] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 3.861700] ACPI: button: Power Button [PWRF]
[ 3.867327] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
�[ 3.895799] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 3.905023] Linux agpgart interface v0.103
[ 3.914105] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1A, rev-id 16)
[ 3.975031] loop: module loaded
[ 3.978679] ACPI: bus type drm_connector registered
[ 3.983940] tun: Universal TUN/TAP device driver, 1.6
[ 3.989140] PPP generic driver version 2.4.2
[ 3.993600] i8042: PNP: No PS/2 controller found.
[ 3.998487] mousedev: PS/2 mouse device common for all mice
[ 4.004194] rtc_cmos 00:04: RTC can wake from S4
[ 4.010007] rtc_cmos 00:04: registered as rtc0
[ 4.014713] rtc_cmos 00:04: setting system clock to 2025-04-16T13:08:15 UTC (1744808895)
[ 4.022872] rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram
[ 4.029613] i2c_dev: i2c /dev entries driver
[ 4.034503] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[ 4.046739] device-mapper: uevent: version 1.0.3
[ 4.051486] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: [email protected]
[ 4.060418] platform eisa.0: Probing EISA bus 0
[ 4.064989] platform eisa.0: EISA: Cannot allocate resource for mainboard
[ 4.071845] platform eisa.0: Cannot allocate resource for EISA slot 1
[ 4.078352] platform eisa.0: Cannot allocate resource for EISA slot 2
[ 4.084858] platform eisa.0: Cannot allocate resource for EISA slot 3
[ 4.091339] platform eisa.0: Cannot allocate resource for EISA slot 4
[ 4.097845] platform eisa.0: Cannot allocate resource for EISA slot 5
[ 4.104351] platform eisa.0: Cannot allocate resource for EISA slot 6
[ 4.110829] platform eisa.0: Cannot allocate resource for EISA slot 7
[ 4.117313] platform eisa.0: Cannot allocate resource for EISA slot 8
[ 4.123817] platform eisa.0: EISA: Detected 0 cards
[ 4.128756] intel_pstate: Intel P-state driver initializing
[ 4.135053] intel_pstate: HWP enabled
[ 4.139169] ledtrig-cpu: registered to indicate activity on CPUs
[ 4.145248] drop_monitor: Initializing network drop monitor service
[ 4.151628] NET: Registered PF_INET6 protocol family
[ 4.161320] Segment Routing with IPv6
[ 4.165028] In-situ OAM (IOAM) with IPv6
[ 4.169002] NET: Registered PF_PACKET protocol family
[ 4.174232] Key type dns_resolver registered
[ 4.179852] microcode: Current revision: 0x000000fc
[ 4.184788] microcode: Updated early from: 0x000000c6
[ 4.190394] IPI shorthand broadcast: enabled
[ 4.195823] sched_clock: Marking stable (2596000666, 1599191018)->(4787940040, -592748356)
[ 4.204328] registered taskstats version 1
[ 4.209462] Loading compiled-in X.509 certificates
[ 4.214743] Loaded X.509 cert 'Build time autogenerated kernel key: 81facc2b0c2c6f4a0b463946bfa0b8ef0d12a9eb'
[ 4.225055] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969'
[ 4.235239] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19'
[ 4.245290] blacklist: Loading compiled-in revocation X.509 certificates
[ 4.252046] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0'
[ 4.261938] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2017): 242ade75ac4a15e50d50c84b0d45ff3eae707a03'
[ 4.272441] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (ESM 2018): 365188c1d374d6b07c3c8f240f8ef722433d6a8b'
[ 4.283285] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2019): c0746fd6c5da3ae827864651ad66ae47fe24b3e8'
[ 4.293781] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v1): a8d54bbb3825cfb94fa13c9f8a594a195c107b8d'
[ 4.304537] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v2): 4cf046892d6fd3c9a5b03f98d845f90851dc6a8c'
[ 4.315295] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v3): 100437bb6de6e469b581e61cd66bce3ef4ed53af'
[ 4.326052] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecadfb9'
[ 4.340116] Demotion targets for Node 0: null
[ 4.344620] Key type .fscrypt registered
[ 4.348577] Key type fscrypt-provisioning registered
[ 4.353605] Key type trusted registered
[ 4.367626] Key type encrypted registered
[ 4.371672] AppArmor: AppArmor sha256 policy hashing enabled
[ 4.377577] integrity: Loading X.509 certificate: UEFI:db
[ 4.383035] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[ 4.394129] integrity: Loading X.509 certificate: UEFI:db
[ 4.399579] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[ 4.410419] integrity: Loading X.509 certificate: UEFI:db
[ 4.415866] integrity: Loaded X.509 cert 'Microsoft Corporation: Windows UEFI CA 2023: aefc5fbbbe055d8f8daa585473499417ab5a5272'
[ 4.427491] integrity: Loading X.509 certificate: UEFI:db
[ 4.432937] integrity: Loaded X.509 cert 'Microsoft UEFI CA 2023: 81aa6b3244c935bce0d6628af39827421e32497d'
[ 4.443483] Loading compiled-in module X.509 certificates
[ 4.449332] Loaded X.509 cert 'Build time autogenerated kernel key: 81facc2b0c2c6f4a0b463946bfa0b8ef0d12a9eb'
[ 4.459326] ima: Allocated hash algorithm: sha256
[ 4.511392] ima: No architecture policies found
[ 4.515975] evm: Initialising EVM extended attributes:
[ 4.521151] evm: security.selinux
[ 4.524498] evm: security.SMACK64
[ 4.527841] evm: security.SMACK64EXEC
[ 4.531544] evm: security.SMACK64TRANSMUTE
[ 4.535672] evm: security.SMACK64MMAP
[ 4.539366] evm: security.apparmor
[ 4.542796] evm: security.ima
[ 4.545794] evm: security.capability
[ 4.549398] evm: HMAC attrs: 0x1
[ 4.552912] PM: Magic number: 5:632:129
[ 4.556965] nvmem cmos_nvram0: hash matches
[ 4.561204] event_source kprobe: hash matches
[ 4.565626] acpi device:04: hash matches
[ 4.569582] acpi PNP0C02:01: hash matches
[ 4.573673] tsc: Refined TSC clocksource calibration: 1607.998 MHz
[ 4.579866] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x172da86403b, max_idle_ns: 440795249167 ns
[ 4.582925] RAS: Correctable Errors collector initialized.
[ 4.595376] clocksource: Switched to clocksource tsc
[ 4.603986] clk: Disabling unused clocks
[ 4.607925] PM: genpd: Disabling unused power domains
[ 4.614125] Freeing unused decrypted memory: 2028K
[ 4.619500] Freeing unused kernel image (initmem) memory: 5096K
[ 4.625442] Write protecting the kernel read-only data: 38912k
[ 4.631942] Freeing unused kernel image (rodata/data gap) memory: 1508K
[ 4.649076] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 4.655529] Run /init as init process
Loading, please wait...
Starting systemd-udevd version 255.4-1ubuntu8.6
[ 4.734070] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 4.739364] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 4.747949] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
[ 4.757400] ahci 0000:00:17.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[ 4.757443] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 4.765409] ahci 0000:00:17.0: 1/1 ports implemented (port mask 0x1)
[ 4.770645] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 4.777005] ahci 0000:00:17.0: flags: 64bit ncq sntf clo only pio slum part deso sadm sds apst
[ 4.784408] xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
[ 4.793470] scsi host0: ahci
[ 4.800306] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.11
[ 4.803135] ata1: SATA max UDMA/133 abar m2048@0xb1e1a000 port 0xb1e1a100 irq 137 lpm-pol 3
[ 4.811328] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.811330] usb usb1: Product: xHCI Host Controller
[ 4.831803] usb usb1: Manufacturer: Linux 6.11.0-19-generic xhci-hcd
[ 4.838167] usb usb1: SerialNumber: 0000:00:14.0
[ 4.842943] hub 1-0:1.0: USB hub found
[ 4.846745] hub 1-0:1.0: 12 ports detected
[ 4.851122] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.11
[ 4.859400] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.866635] usb usb2: Product: xHCI Host Controller
[ 4.871523] usb usb2: Manufacturer: Linux 6.11.0-19-generic xhci-hcd
[ 4.877885] usb usb2: SerialNumber: 0000:00:14.0
[ 4.882613] hub 2-0:1.0: USB hub found
[ 4.886391] hub 2-0:1.0: 6 ports detected
[ 5.086160] usb 1-6: new full-speed USB device number 2 using xhci_hcd
[ 5.130534] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 5.137055] ata1.00: supports DRM functions and may not be fully accessible
[ 5.144032] ata1.00: ATA-11: Samsung SSD 870 EVO 1TB, SVT02B6Q, max UDMA/133
[ 5.151679] ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[ 5.163568] ata1.00: Features: Trust Dev-Sleep NCQ-sndrcv
[ 5.169448] ata1.00: supports DRM functions and may not be fully accessible
[ 5.182402] ata1.00: configured for UDMA/133
[ 5.186693] ahci 0000:00:17.0: port does not support device sleep
[ 5.193021] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 870 2B6Q PQ: 0 ANSI: 5
[ 5.201327] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 5.201357] ata1.00: Enabling discard_zeroes_data
[ 5.211380] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 5.219054] sd 0:0:0:0: [sda] Write Protect is off
[ 5.223868] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5.224951] usb 1-6: New USB device found, idVendor=0cf3, idProduct=e300, bcdDevice= 0.01
[ 5.232938] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[ 5.241102] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 5.247531] ata1.00: Enabling discard_zeroes_data
[ 5.271073] sda: sda1 sda2 sda3 sda4 sda5
[ 5.277139] sd 0:0:0:0: [sda] supports TCG Opal
[ 5.281689] sd 0:0:0:0: [sda] Attached SCSI disk
[ 5.288828] nvme nvme0: pci function 0000:08:00.0
[ 5.306544] nvme nvme0: D3 entry latency set to 10 seconds
[ 5.315559] nvme nvme0: 12/0/0 default/read/poll queues
[ 5.322644] nvme0n1: p1 p2 p3 p4
[ 5.338242] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 5.363305] usb 2-2: New USB device found, idVendor=13fe, idProduct=6700, bcdDevice= 1.10
[ 5.371494] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5.378636] usb 2-2: Product: USB 3.2 gen. 1
[ 5.382915] usb 2-2: Manufacturer: Wilk
[ 5.386765] usb 2-2: SerialNumber: 071C4430E00EF407
[ 5.473180] usb 1-9: new high-speed USB device number 3 using xhci_hcd
[ 5.616317] usb 1-9: New USB device found, idVendor=05c6, idProduct=90b3, bcdDevice= 3.18
[ 5.624533] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5.631689] usb 1-9: Product: MDG200
[ 5.635294] usb 1-9: Manufacturer: Qualcomm
[ 5.655641] usb-storage 2-2:1.0: USB Mass Storage device detected
[ 5.662011] scsi host1: usb-storage 2-2:1.0
[ 5.666263] usbcore: registered new interface driver usb-storage
[ 5.673506] usbcore: registered new interface driver uas
[ 6.687854] scsi 1:0:0:0: Direct-Access Wilk USB 3.2 gen. 1 PMAP PQ: 0 ANSI: 6
[ 6.696300] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 6.698240] sd 1:0:0:0: [sdb] 60628992 512-byte logical blocks: (31.0 GB/28.9 GiB)
[ 6.710470] sd 1:0:0:0: [sdb] Write Protect is off
[ 6.716302] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
[ 6.758633] sdb: sdb1 sdb2 sdb3 sdb4.. done.
[ 6.763925] sd 1:0:0:0: [sdb] Attached SCSI removable disk
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=bbe39a81-c156-427b-a416-ffc6690acd3d does not exist. Dropping to a shell!
BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
No such hangs or bootfails happen on the AMI FW, so the microcode version does not seem to be the main issue here. Additionally, it seems that Dasharo built from the mentioned commit, reboots every few minutes.
Platform v4670 v1, cpuid: eax=0x000a0660 (ucode 0xca)
6.11.0-21:
I have not successfully booted this version of Ubuntu, only via recovery mode.
6.11.0-19:
I have not successfully booted this version of Ubuntu, only via recovery mode.
Reboot into recovery mode, then proceed with normal boot: no hang, no microcode update in dmesg
I don't understand what is happening here. No microcode update in dmesg is weird, it should always happen if the microcode version loaded by the firmware is different.
What is so special about recovery mode? And what recovery mode are we talking about. The Ubuntu recovery mode or vboot recovery mode? If it is Ubuntu recovery mode, maybe it does not load microcode.
Additionally, it seems that Dasharo built from the mentioned commit, reboots every few minutes.
Maybe you have a watchdog enabled in the setup...
ALERT! UUID=bbe39a81-c156-427b-a416-ffc6690acd3d does not exist. Dropping to a shell! No such hangs or bootfails happen on the AMI FW, so the microcode version does not seem to be the main issue here.
The OS did not find the requested disk. It may be different issue, but definitely not related to this one. Main issue is still the hang occurring even before the kernel prints dmesg. We already know that sporadically it is able to get past the early microcode loading and start printing kernel messages...
@SebastianCzapla also avoid adding such long logs. it makes hard to track the discussion. For large logs attach them as a file or through some pastebin, e.g. https://paste.dasharo.com/
@SebastianCzapla also avoid adding such long logs. it makes hard to track the discussion. For large logs attach them as a file or through some pastebin, e.g. https://paste.dasharo.com/
I've edited the comment to use <details> and <summary> tags.
@miczyg1 @krystian-hebel @BeataZdunczyk, what should we do with this bug?
@pietrushnic fix it by preparing new release(s) with newest ucode, with hope that it won't be impacted by the same issue. IIRC Xen has the option to force "updating" the ucode on boot even if the update is using the same version as currently loaded, perhaps this could be used for testing.
If this doesn't fix the problem, it should be at least listed as a known issue in all impacted releases.
Looking back over this, it now looks suspiciously like the same symptoms as xen-project/xen@4aae4452efeee3d3bba092b875e37d1e7c8f6db9
That too had a "turning off microcode loading seems to help" which in the end was unrelated. I suspect the relevant side effect is the wbinvd in the ucode loading path.
The absence of (XEN) Booting processor 4/4 eip 90000 from the log means that we hadn't got as far as SIPI-ing the final CPU, and was stuck slightly earlier.
Please can you try reproducing it using an update to date Xen. We've put a few extra diagnostics into this path to help diagnose issues.
Hmm, in some earlier AEM tests I've seen few cases where all but one APs were woken by writing to an armed address, it may also have been caused by this errata. I don't remember on which platform it happened, and since it didn't happen later, I discarded it as caused by some bug in our code, but it was the sole reason for https://github.com/Dasharo/open-source-firmware-validation/blob/develop/trenchboot/02-with-drtm.robot#L23
Please can you try reproducing it using an update to date Xen. We've put a few extra diagnostics into this path to help diagnose issues.
It was not only Xen faulting, we had problems Linux distros too.
It was not only Xen faulting, we had problems Linux distros too.
Indeed, which likely makes it a hardware or microcode issue, but it's still easier to do something about it we know what's wrong.
@pietrushnic fix it by preparing new release(s) with newest ucode, with hope that it won't be impacted by the same issue. IIRC Xen has the option to force "updating" the ucode on boot even if the update is using the same version as currently loaded, perhaps this could be used for testing.
If this doesn't fix the problem, it should be at least listed as a known issue in all impacted releases.
@macpijan @BeataZdunczyk Do we consider it something that can be escalated to the customer to justify a hot fix or a new release? I'm completely fine if we decide that this is a TrenchBoot product-related issue, and no support will be provided to the customer. However, we should still consider the costs associated with the release, so we can even consider an unvalidated Tech Preview.