edac_mc_handle_error(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… edac_mc_handle_error(9) β€” from the Kernel API Manual ✨

okay so bestie, buckle up πŸŽ€ this is edac_mc_handle_error from the Kernel API Manual, and it's literally the function that tells userspace "hey, a memory thing happened." That's the whole vibe. Memory event reporting, main character energy, periodt. πŸ’–


✨ NAME ✨

edac_mc_handle_error β€” reports a memory event to userspace. that's it, that's the job 🫢


🌸 SYNOPSIS 🌸

void edac_mc_handle_error (const enum hw_event_mc_err_type type , struct
mem_ctl_info *mci , const u16 error_count , const unsigned long
page_frame_number , const unsigned long offset_in_page , const unsigned
long syndrome , const int top_layer , const int mid_layer , const int
low_layer , const char *msg , const char *other_detail );

like, yeah, it's a lot of args 😭 but every single one of them is doing something, i promise. no cap.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • type β€” the severity of the error, and it's one of CE/UE/Fatal πŸ’€ so like, how bad are we talking
  • mci β€” a struct mem_ctl_info pointer. yes, the struct. you know the one 🧚
  • error_count β€” the number of errors of the same type. like, how many of these bad boys we got πŸ”₯
  • page_frame_number β€” the mem page where the error occurred πŸ“„ that's literally where it happened
  • offset_in_page β€” the offset of the error inside the page. so like, where inside the page 🎯
  • syndrome β€” the ECC syndrome ⭐
  • top_layer β€” memory layer[0] position 🌈
  • mid_layer β€” memory layer[1] position 🌈
  • low_layer β€” memory layer[2] position 🌈 (yes there are three layers, keep up bestie)
  • msg β€” a message that's meaningful to the end users, explaining the event. like, human-readable, for actual people πŸ™ˆ
  • other_detail β€” technical details about the event that may help hardware manufacturers and EDAC developers analyse the event πŸ”¬ so the nerds (affectionate) can figure out what went down
lowkey important: msg is for the humans, other_detail is for the hardware manufacturers and EDAC developers. two different audiences, two different strings. don't mix them up πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./drivers/edac/edac_mc.h, and also the whole friend group:


and that's the page, bestie πŸ“ it's from ./drivers/edac, dated October 2026, and it's titled edac_mc_handle_error(9) β€” slay, go report some memory events responsibly πŸ’œβœ¨

πŸ“¦ where this page comes from