Skip to content

Conversation

@pmenzel
Copy link
Contributor

@pmenzel Paul Menzel (pmenzel) commented Oct 11, 2026 •

Claude Code prompt:

Please add the new EDAC modules to the kmod whitelist:

2026-10-09T14:35:44.362482+02:00 sigusr2 modprobe: kmod whitelist: module 'ie31200_edac' not in whitelist, denied

Also fixes warning on dose:

2026-10-11T12:22:25.756298+02:00 dose (udev-worker): kmod whitelist: module 'sb_edac' not in whitelist, denied

Linux 6.18.55.mx64.499 builds the EDAC memory controller drivers as
modules (CONFIG_EDAC=y, CONFIG_EDAC_{AMD64,IE31200,SBRIDGE,SKX}=m),
while 6.12.98.mx64.492 does not build EDAC at all. As none of them is
whitelisted, loading is denied, for example on *sigusr2* (Coffee Lake S,
8086:3e30):

    2026-10-09T14:35:44.362482+02:00 sigusr2 modprobe: kmod whitelist: module 'ie31200_edac' not in whitelist, denied

Whitelist all EDAC modules shipped with 6.18.55.mx64.499:

    amd64_edac
    ie31200_edac
    sb_edac
    skx_edac
    skx_edac_common (dependency of skx_edac)

Take the comments from `modinfo -F description`.

Assisted-by: claude-opus-5.5 (Claude Code)
@donald
Copy link
Collaborator

If maintaining the whitelist becomes to much burden: Should we allow any modules during boot, then switch to whitelist-only mode just before user controlled software is allowd to run?

@pmenzel Paul Menzel (pmenzel) merged commit 2750ae4 into master Oct 11, 2026
@pmenzel
Copy link
Contributor Author

If maintaining the whitelist becomes to much burden: Should we allow any modules during boot, then switch to whitelist-only mode just before user controlled software is allowed to run?

I think it’s the current approach is still bearable, and would not change it yet.

@pmenzel Paul Menzel (pmenzel) deleted the kmod-whitelist-add-edac-modules branch October 11, 2026 20:50
Sign in to join this conversation on GitHub.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants