pseries_eeh_get_log(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– pseries_eeh_get_log(9) β€” like, the Kernel API Manual one πŸŽ€

okay bestie, buckle in, because this is the glow-up of the page for pseries_eeh_get_log β€” she lives in the Kernel API Manual and she is here to retrieve error logs. no cap. πŸ¦‹


✨ NAME ✨

pseries_eeh_get_log β€” Retrieve error log πŸ’…


🌸 SYNOPSIS 🌸

int pseries_eeh_get_log (struct eeh_pe *pe , int severity , char *drv_log , unsigned long len );

that's the whole signature, character for character, please don't @ me πŸ™ˆ


πŸŽ€ ARGUMENTS πŸŽ€

  • pe β€” EEH PE. iconic. that's the one.
  • severity β€” temporary or permanent error log 🌈 (yes, you gotta pick which vibe)
  • drv_log β€” driver log to be combined with retrieved error log 🫢 so it's like, a collab
  • len β€” length of driver log πŸ“ know your limits bestie

πŸ”₯ DESCRIPTION πŸ”₯

So what she does: she retrieves the temporary or permanent error from the PE ✨ literally the whole point.

And actually β€” and this is the detail, don't skip it β€” the error will be retrieved through the dedicated RTAS call πŸ‘‘ that's the real mechanism, iykyk.


πŸ’œ SEE ALSO πŸ’œ

the whole friend group fr fr, every single one of them, no one left out 🧚


πŸ’€ reminder that severity is either temporary or permanent and drv_log gets combined with what we retrieve β€” that's not a vibe, that's the spec πŸ“

okay that's the page πŸ’– big slay. she's from ./arch/powerpc/platforms/pseries, dated October 2026, and she's filed under pseries_eeh_get_log(9) β€” periodt. 🌟

πŸ“¦ where this page comes from