edac_mc_handle_error(9)
π 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 ofCE/UE/Fatalπ so like, how bad are we talkingmciβ astruct mem_ctl_infopointer. 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 happenedoffset_in_pageβ the offset of the error inside the page. so like, where inside the page π―syndromeβ the ECC syndrome βtop_layerβ memorylayer[0]position πmid_layerβ memorylayer[1]position πlow_layerβ memorylayer[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:msgis for the humans,other_detailis 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:
edac_mc_alloc(9)edac_get_owner(9)edac_mc_free(9)edac_has_mcs(9)edac_mc_find(9)find_mci_by_dev(9)edac_mc_del_mc(9)edac_mc_find_csrow_by_page(9)edac_raw_mc_handle_error(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms