Issue #631 has been updated by Sebastian Müller.

I've pushed three changes for this to Gerrit, grouped under the topic 
topton-x2e-stability:

https://review.coreboot.org/q/topic:topton-x2e-stability

CB:94028 mb/topton/adl: detach IT8625E hardware monitor from the ACPI SCI
Declares the IT8625E EC (LDN 0x04) with no IRQ. Your dump showed it enabled on 
IRQ 9, which is the ACPI SCI on Alder Lake-N; on a fanless box the empty fan 
header makes the HWM assert IRQ 9 forever ("irq 9: nobody cared"). This is the 
main root cause of the lag/timer trouble.

CB:94029 mb/topton/adl: pin SA-GV to a fixed point
Pins the DRAM to SaGv_FixedPoint3. SA-GV frequency switching on non-ECC memory 
can cause the random spinlock-timeout/hang instability.

CB:94030 mb/topton/adl: disable ASPM/L1 substates on the NVMe root port
Completes the existing "fixes wonky NVME" DMI-ASPM workaround on the port side, 
so a DRAM-less NVMe doesn't drop off the bus over L1.2 latency.

Could you build master with all three (same topic, so you can cherry-pick the 
topic) and check whether the IRQ 9 storm, the instability and the NVMe 
detection are resolved? If it holds up I'll add your Tested-by. Thanks for the 
detailed report and the superiotool dump - that's what made this diagnosable.

----------------------------------------
Bug #631: Topton X2E (N150) instabilities/timer issues
https://ticket.coreboot.org/issues/631#change-2344

* 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]

Reply via email to