SysadminNews

Linux 7.3: AMD ATL loads only when needed

On this page
  1. Follow the loading dependency
  2. What to check on a running machine
  3. Other EDAC changes in this cycle
  4. Sources

Linux’s AMD Address Translation Library no longer tries to load indiscriminately on Zen systems. EDAC requests it after checking the platform, avoiding an unnecessary initialization message where DRAM ECC is not enabled.

The merged change moves the ATL loading request after the AMD64 EDAC checks. An absent module is not enough to determine whether ECC is enabled or memory is healthy.
The merged change moves the ATL loading request after the AMD64 EDAC checks. An absent module is not enough to determine whether ECC is enabled or memory is healthy. Chart : PeopleAreGeek. Data source.
View full-size image

Follow the loading dependency

The merged ATL change removes its automatic module dependency table. The AMD64 EDAC driver requests the library after its system checks. The commit explicitly concerns systems with DRAM ECC enabled, which is more precise than saying that an ECC-capable memory module is installed.

That distinction matters when diagnosing a workstation. Memory capability, motherboard and firmware support, active configuration, and kernel reporting are separate parts of the chain. A missing ATL initialization message does not by itself prove that memory is healthy or that ECC is active.

What to check on a running machine

Use your system’s hardware documentation to establish the expected ECC configuration, then compare it with the firmware setting and operating-system reporting. The kernel’s EDAC documentation describes the memory-controller hierarchy and corrected/uncorrected error reporting exposed through sysfs.

For an initial read-only inspection on Linux:

uname -r
ls /sys/devices/system/edac/mc/
journalctl -k -b --no-pager | grep -Ei 'EDAC|ECC|AMD.*ATL'

These commands inspect version, available EDAC controllers and kernel messages; they are not a memory test. A missing directory or log entry can also reflect driver support, configuration or access restrictions. Compare expected controller coverage before treating quieter logs as a successful monitoring setup.

Other EDAC changes in this cycle

The maintainer’s request for v7.3-rc2 also lists Intel Starfire support, detection of Intel client memory-controller counts at boot, and fixes to address decoding. It marks ThunderX and MPC85XX EDAC drivers orphaned. Orphaned means a maintenance gap, not that the drivers have already been deleted.

For an administrator, the priority depends on the machine. On an ordinary non-ECC desktop, this is primarily cleanup. On an ECC server, verify that error reporting remains visible after the update. On an orphaned platform, preserve the working kernel and check maintainer discussions before assuming continued coverage. None of these changes alone establishes a speed improvement or substitutes for a tested backup and monitoring plan.

Sources

Checked the actual ATL commit; clarified enabled ECC versus installed RAM and removed unsupported claims about Starfire and driver removal.