Issue #631 has been updated by Alicja Michalska.
Sebastian Müller wrote in #note-7:
> @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.)
I've tested it and you're right. I wonder how stock firmware gets rid of it
(since this is exactly how stock firmware configured it). Probably something
cursed...
Feel free to pull other changes from CB:94042 into your patchset, I will
rubber-stamp it :)
```
home:~# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
4: 0 0 266 0 IR-IO-APIC 4-edge
ttyS0
8: 1 0 0 0 IR-IO-APIC 8-edge rtc0
9: 0 0 0 0 IR-IO-APIC 9-fasteoi acpi
14: 0 0 0 0 IR-IO-APIC 14-fasteoi
INTC1057:00
20: 1 0 0 0 IR-IO-APIC 20-fasteoi
i801_smbus
120: 0 0 0 0 DMAR-MSI 0-edge dmar0
121: 0 0 0 0 DMAR-MSI 1-edge dmar1
122: 0 0 0 1 IR-PCI-MSI-0000:00:1c.0
0-edge PCIe PME, PCIe bwctrl
123: 1 0 0 0 IR-PCI-MSI-0000:00:1c.1
0-edge PCIe PME, PCIe bwctrl
124: 0 1 0 0 IR-PCI-MSI-0000:00:1c.2
0-edge PCIe PME, PCIe bwctrl
125: 0 0 1 0 IR-PCI-MSI-0000:00:1c.6
0-edge PCIe PME, PCIe bwctrl
126: 0 0 0 1 IR-PCI-MSI-0000:00:1d.0
0-edge PCIe PME, PCIe bwctrl
127: 0 51 0 0 IR-PCI-MSI-0000:00:16.0
0-edge mei_me
128: 0 0 0 3109 IR-PCI-MSI-0000:00:17.0
0-edge ahci[0000:00:17.0]
129: 261 0 0 0 IR-PCI-MSI-0000:00:14.0
0-edge xhci_hcd
134: 0 0 3561 0 IR-PCI-MSI-0000:05:00.0
0-edge mt7921e
135: 0 0 1 0 IR-PCI-MSIX-0000:01:00.0
0-edge eth0
136: 0 0 0 96989 IR-PCI-MSIX-0000:01:00.0
1-edge eth0-TxRx-0
137: 2981 0 0 0 IR-PCI-MSIX-0000:01:00.0
2-edge eth0-TxRx-1
138: 0 4309 0 0 IR-PCI-MSIX-0000:01:00.0
3-edge eth0-TxRx-2
139: 0 0 2108 0 IR-PCI-MSIX-0000:01:00.0
4-edge eth0-TxRx-3
140: 1 0 0 0 IR-PCI-MSIX-0000:02:00.0
0-edge eth1
141: 0 5455 0 0 IR-PCI-MSIX-0000:02:00.0
1-edge eth1-TxRx-0
142: 0 0 13677 0 IR-PCI-MSIX-0000:02:00.0
2-edge eth1-TxRx-1
143: 0 0 0 5969 IR-PCI-MSIX-0000:02:00.0
3-edge eth1-TxRx-2
144: 6248 0 0 0 IR-PCI-MSIX-0000:02:00.0
4-edge eth1-TxRx-3
150: 0 0 0 0 IR-PCI-MSIX-0000:04:00.0
0-edge eth3
151: 0 0 0 0 IR-PCI-MSIX-0000:04:00.0
1-edge eth3-TxRx-0
152: 0 0 0 0 IR-PCI-MSIX-0000:04:00.0
2-edge eth3-TxRx-1
153: 0 0 0 0 IR-PCI-MSIX-0000:04:00.0
3-edge eth3-TxRx-2
154: 0 0 0 0 IR-PCI-MSIX-0000:04:00.0
4-edge eth3-TxRx-3
155: 0 0 0 27 IR-PCI-MSI-0000:00:02.0
0-edge i915
156: 0 271 0 0 IR-PCI-MSI-0000:00:1f.3
0-edge snd_hda_intel:card0
NMI: 1 0 1 2 Non-maskable interrupts
LOC: 70420 62936 66178 78385 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 1 0 1 2 Performance monitoring
interrupts
IWI: 3 2 0 7 IRQ work interrupts
RTR: 0 0 0 0 APIC ICR read retries
RES: 195 240 203 191 Rescheduling interrupts
CAL: 11815 19203 16211 21532 Function call interrupts
TLB: 248 162 419 684 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 Deferred Error APIC
interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 7 8 8 8 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 Posted-interrupt
notification event
NPI: 0 0 0 0 Nested posted-interrupt
event
PIW: 0 0 0 0 Posted-interrupt wakeup
event
```
----------------------------------------
Bug #631: Topton X2E (N150) instabilities/timer issues
https://ticket.coreboot.org/issues/631#change-2353
* 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]
