Actions
Bug #631
open
VB
Topton X2E (N150) instabilities/timer issues
Bug #631:
Topton X2E (N150) instabilities/timer issues
Start date:
02/23/2026
Due date:
% Done:
0%
Estimated time:
Affected versions:
Needs backport to:
Affected hardware:
Topton X2E
Affected OS:
Linux, BSD
Description
Image built from master (c9578eac246) as 25.12 does not support iPXE with SecureBoot in edk2 payload.
After flashing the image a few bugs were discovered (all may be related to the same root cause)
- Some USB drives and NVMes may be not detected in edk2 on boot - setting port speed to Gen3 manually and turning off power saving mostly helps with NVMes, however some flash drives may still need to be unplugged and re-plugged back
- Booting from Ventoy USB mostly doesn't work - some linux images wait for mount and then fail with timout, others will just hang. Ventoy itself boots quickly and reliably.
- USB booting from images written directly to flash mostly works, however BSD may still hang or panic out with spinlock timeout panic (OpnSense/FreeBSD)
- Linux kernel reports about broken IRQ 9 (acpi_sci=low seemingly removes the message from dmesg)
- After several tries to boot, BSD system got installed without any issues, however after rebooting into it the system became extremely laggy (even printing to the console worked word-by-word, high LA without any userspace CPU-loading process), switching the timer from LAPIC to HPET on running system seemingly resolved all the laginess instantly
- Linux kernel reports that HPET is dysfunctional in PC10 (shouldn't it be fine on Alder Lake?)
Build config (I tried both with default xApic and x2Apic - doesn't seem to change anything):
CONFIG_VENDOR_TOPTON=y
# CONFIG_POST_DEVICE is not set
# CONFIG_POST_IO is not set
CONFIG_TPM_MEASURED_BOOT=y
CONFIG_BOARD_TOPTON_X2E_N150=y
# CONFIG_FSP_HYPERTHREADING is not set
CONFIG_X2APIC_ONLY=y
CONFIG_TPM2=y
CONFIG_TPM_MEASURE_MRC_CACHE=y
CONFIG_DEFAULT_CONSOLE_LOGLEVEL_6=y
CONFIG_PAYLOAD_EDK2=y
CONFIG_EDK2_ENABLE_IPXE=y
The majority of these problems can be explained by faulty timer - the reason for a single ticket
I'm also attaching the patch suggested in Discord channel for reference - doesn't seem to solve the issue
Files
No data to display
Actions