Knowledge Base Article
Why does the Linux* EDAC driver report "Previous Boot UE detected[0x40000]" on Agilex® 7 FPGA F and I-Series SoC FPGA devices?
Description
The Linux* EDAC driver (drivers/edac/altera_edac.c) in the SoCFPGA Linux 6.12.11-lts (and earlier versions) may print a false Uncorrectable Error (UE) message during driver probe on Agilex® 7 F/I series SoC FPGA platform, as shown below.
EDAC Altera: Previous Boot UE detected[0x40000] @ 0x0
The EDAC driver maps BOOT_SCRATCH_COLD8 (offset address0x220in System Manager, absolute address 0xFFD12220) to S10_SYSMGR_UE_VAL_OFST and treats any non-zero value as evidence of a previous boot UE event. At probe time, the driver checks:
if (dberror) { ... }
instead of properly masking with:
if (dberror & AGX7F_I_DBE_IRQ_MASK) { ... }
The valid UE sticky mask AGX7F_I_DBE_IRQ_MASK(0x30002) covers bits 1/16/17 only. When the value of BOOT_SCRATCH_COLD8 is 0x40000 in which bit 18 represents the SDM ACF DDR data rate per the Agilex 7 F/I SoC FPGA register definition, but it’s reported as a DDR UE/DBE by Linux EDAC driver by mistake.
The driver does not account for the differences among the various Agilex 7 device series or for future device families.
BOOT_SCRATCH_COLD8 bit definitions:
|
Bit field |
Agilex 7 F/I-Series |
Agilex 7 M-Series |
Values / description |
Usage or source |
|---|---|---|---|---|
|
[31] |
Available as scratch memory |
DBE Triggered Flag |
M-Series:0: DDR DBE not triggered; 1: DDR DBE triggered |
U-Boot ddr_ecc_dbe_status(): evaluates DDR ECC DBE status |
|
[30] |
Available as scratch memory |
DDR Init in progress |
M-Series:0: DDR initialization not performed or completed successfully; 1: DDR initialization in progress |
U-Boot is_ddr_init_hang() checks the bit; ddr_init_inprogress() sets or clears it |
|
[29] |
Available as scratch memory |
OCRAM_DBE Error Flag |
M-Series:0: error did not occur; 1: error occurred |
U-Boot hps_ocram_dbe_status() returns OCRAM DBE status; ddr_init_inprogress() sets or clears it |
|
[28:27] |
Available as scratch memory |
Number of IO96B instances assigned to HPS |
M-Series:Written during DDR handoff data population |
U-Boot update_io96b_assigned_to_hps() |
|
[19] |
Flag indicating that a CPU power domain is about to be turned on; value 1 |
Flag indicating that a CPU power domain is about to be turned on; value 1 |
F/I/M-Series:A value of 1 indicates that the CPU power domain is about to be turned on |
ATF socfpga_pwr_domain_on() |
|
[18] |
ACF DDR data rate set by SDM |
Available as scratch memory |
F/I-Series: 0 = half-rate; 1 = quarter-rate |
U-Boot sdram_mmr_init_full() uses the value to configure DDRIOCTRL |
|
[17] |
ECC_DBE_DDR1 Error Flag |
ECC_DBE_DDR1 Error Flag |
F/I/M-Series:0: error did not occur; 1: error occurred |
ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler |
|
[16] |
ECC_DBE_DDR0 Error Flag |
ECC_DBE_DDR0 Error Flag |
F/I/M-Series:0: error did not occur; 1: error occurred |
ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler |
|
[1] |
ECC_DBE_OCRAM Error Flag |
ECC_DBE_OCRAM Error Flag |
F/I/M-Series:0: error did not occur; 1: error occurred |
ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler |
Impact:
- No actual DDR UE event is indicated by 0x40000.
- The false-positive log does not trigger kernel panic, reboot, or EDAC fault handling.
- However, the driver executes a full register write of zero to both BOOT_SCRATCH_COLD8 and BOOT_SCRATCH_COLD9 after printing the message, which may clear other valid scratch data (ATF, SDM, DDR progress bits) used by boot software on subsequent resets.
- Real DDR ECC uncorrectable errors continue to be reported correctly through the runtime ECC interrupt path (ECC_INTSTATUS_DERR @ sysmgr +0xA0).
Resolution
A patch has been applied to remove the incorrect previous DBE check using the BOOT_SCRATCH_COLD8 register during EDAC driver probe.