pnv_eeh_next_error(9)
β¨ NAME β¨
okay so this is pnv_eeh_next_error(9) from the Kernel API Manual, bestie π«Ά β the NAME is pnv_eeh_next_error and it's literally Retrieve next EEH error to handle π
.
π¦ SYNOPSIS π¦
the function signature is giving kernel-core realness, and it is exactly:
int pnv_eeh_next_error (struct eeh_pe **pe );
π ARGUMENTS π
peβ Affected PE, no cap π«Ά
π DESCRIPTION π
The function is expected to be called by EEH core while it gets special EEH event (without binding PE). Periodt. It calls to OPAL APIs for next error to handle, and the informational error is handled internally by platform β that part is platform's moment β¨.
But the dead IOC, dead PHB, fenced PHB and frozen PE? Those should be handled by EEH core eventually, bestie β yes, all of those ππ .
π SEE ALSO π
- Kernel file
./arch/powerpc/platforms/powernv/eeh-powernv.cβ the source file, go peek π pnv_eeh_post_init(9)β related function π¦pnv_eeh_probe(9)β related function π¦pnv_eeh_set_option(9)β related function π¦pnv_eeh_get_state(9)β related function π¦pnv_eeh_reset(9)β related function π¦pnv_eeh_get_log(9)β related function π¦pnv_eeh_configure_bridge(9)β related function π¦eeh_powernv_init(9)β related function π¦
mwah π source/version energy: ./arch/powerpc/platforms/powernv β’ date energy: October 2026 β’ that's the whole page, periodt π
π¦ 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