Issue #631 has been updated by Sebastian Müller.
@Victor — one quick practical note at the end of this discussion so the IRQ 9 storm (#4) and the lag (#5) come out conclusively in your test: CB:94042 declares the EC but keeps irq 0x70 = 0x09 — that's IRQ 9 = the ACPI SCI on this board, the exact line the HWM is storming on, so that path stays armed. CB:92369 doesn't change the EC IRQ either (as noted above). The one that actually detaches it is my CB:94028 (irq 0x70 = 0, no IRQ routed → the HWM can't assert the SCI). And that is the way the stock firmware deals with this. So for the storm/lag specifically, that's the change to test. Easy to verify directly: superiotool -d (LDN 0x04, reg 0x70) before/after, and watch the acpi line in grep -i acpi /proc/interrupts under load. Your board is the final arbiter — happy to adjust to whatever it shows. @Alicja — I did have a look at CB:94042. For the interrupt storm specifically it won't resolve it: it keeps the EC on irq 0x70 = 0x09, which is IRQ 9 = the ACPI SCI — the exact line the HWM is storming on. So that path stays armed rather than detached. (CB:92369 doesn't touch the EC IRQ either, as you noted.) ---------------------------------------- Bug #631: Topton X2E (N150) instabilities/timer issues https://ticket.coreboot.org/issues/631#change-2349 * Author: Victor Bessonov * Status: New * Priority: Normal * Target version: none * Start date: 2026-02-23 * Affected versions: main * Affected hardware: Topton X2E * Affected OS: Linux, BSD ---------------------------------------- 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) 1. 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 2. 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. 3. USB booting from images written directly to flash mostly works, however BSD may still hang or panic out with spinlock timeout panic (OpnSense/FreeBSD) 4. Linux kernel reports about broken IRQ 9 (acpi_sci=low seemingly removes the message from dmesg) 5. 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 6. 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): ``` shell 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-------------------------------- coreboot.log (63.9 KB) linux-boot.log (274 KB) gpio.patch (3.1 KB) SuperIODump.txt (1.48 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
