edac_raw_mc_handle_error(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… edac_raw_mc_handle_error β€” the kernel API manual, but make it make sense

okay bestie, welcome to edac_raw_mc_handle_error(9) πŸ’– this is a page from the Kernel API Manual (section 9, the fun one) and we're gonna get into it. no cap, it's short but she's important.


✨ NAME ✨

edac_raw_mc_handle_error β€” reports a memory event to userspace without doing anything to discover the error location 🫢

like, she's literally just the messenger. no detective work, no vibes-based investigation of where the error came from. she reports and leaves. main character energy but make it minimal πŸ”₯


🌸 SYNOPSIS 🌸

void edac_raw_mc_handle_error (struct edac_raw_error_desc *e );

πŸŽ€ ARGUMENTS πŸŽ€

  • e β€” error description πŸ’œ that's the whole thing. one argument. she's low maintenance like that.

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” this raw function is used internally by edac_mc_handle_error. bestie, it's an inside job.

it should only be called directly when the hardware error comes directly from BIOS β€” like in the case of the APEI GHES driver ✨ iykyk.

fr fr: don't just call this because it looks cute. it's meant to be reached through edac_mc_handle_error, except for that BIOS-direct situation. respect the pipeline πŸ™ˆ

πŸ” SEE ALSO πŸ”

the whole squad, gathered for you 🫢 these all live in the kernel file ./drivers/edac/edac_mc.h:

go read them. all of them. it's giving study group πŸ“šπŸ’…


and that's the whole page, bestie 🌈 this little icon dropped from ./drivers/edac back in October 2026, sitting pretty in section 9 of the Kernel API Manual β€” slay, periodt πŸ‘‘πŸ’–

πŸ“¦ where this page comes from