Issue #631 has been updated by Alicja Michalska.
Sebastian Müller wrote in #note-4: > 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: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. Again, please, stop pushing AI-generated code - *especially* without understanding the underlying issue. Disabling advertising of ASPM capabilities has no affect if user doesn't explicitly enable ASPM in Kconfig. Since this issue was opened I already pushed a patch fixing most of them (CB:92369) but likely doesn't solve interrupt storm. NVME detection issue is caused by not knowing which GPIO controls the PCIe slot reset. If you have an oscilloscope and would like to mess with libgpiod it can be solved relatively cleanly. The real fix for this is to set clock 0 as `FREE_RUNNING`, which will enable clock at all times. Might also need to tell FSP to stop touching GPIOs like I did on my most recent port (CB:94039) I never tested/checked HPET on coreboot. Lst time I messed with it few years ago I believe some ACPI stuff was missing, but my memory might be playing tricks on me. As for USB, I suspect that USB3 ports are re-used TCSS-as-type_A, so it needs appropriate mapping. If it works fine with a USB2 stick then it'll be 100% confirmed. Personally I haven't had any USB issues (but I know only USB2 is working) and I've been running this system in production for over 2 years at this point. That being said, port definitely could use some improvement. I ported this router in few hours I spent on DB Regio heading from Strasbourg to Dortmund, so it was done within ~4 hours in total. > Hangs / spinlock panics / instability (3). If your DIMM is a Micron or > Crucial DDR5-4800 single-rank, that is the known N100/Topton instability. > Pins the DRAM to SaGv_FixedPoint3. SA-GV frequency switching on non-ECC > memory can cause the random spinlock-timeout/hang instability. "Where's the source? The source is that I made it the [censored] up"... ``` home:~# uptime 23:22:43 up 49 days, 9:31, 0 users, load average: 0.00, 0.00, 0.00 home:~# dmidecode -t memory # dmidecode 3.7 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Handle 0x0009, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 64 GiB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x000A, DMI type 17, 40 bytes Memory Device Array Handle: 0x0009 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 16 GiB Form Factor: SODIMM Set: None Locator: Channel-0-DIMM-0 Bank Locator: BANK 0 Type: DDR5 Type Detail: Unknown Synchronous Speed: 4800 MT/s Manufacturer: Unknown (0) Serial Number: 00000000 Asset Tag: Channel-0-DIMM-0-AssetTag Part Number: None Rank: 1 Configured Memory Speed: 4800 MT/s Minimum Voltage: 1.1 V Maximum Voltage: 1.1 V Configured Voltage: 1.1 V ``` Please try: CB:94042 ---------------------------------------- Bug #631: Topton X2E (N150) instabilities/timer issues https://ticket.coreboot.org/issues/631#change-2347 * 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]
