On Mon, Jul 14, 2025 at 03:21:44PM -0700, Luck, Tony wrote:
> So what about something like:
>
> enum recovered_error_sources {
> ERR_GHES,
> ERR_MCE,
> ERR_AER,
> ...
> ERR_NUM_SOURCES
> };
>
> static struct recovered_error_info {
> int num_recovered_errors;
> time64_t last_recovered_error_timestamp;
> } recovered_error_info[ERR_NUM_SOURCES];
Too many "recovered" :-)
> A count is just a hint. A count with a timestamp that is shortly
> before a crash is a smoking gun.
All good thoughts... from where I'm standing right now, though, it looks to me
like we're wagging the dog: inventing issues and thinking of which solution
would fit them best. :-)
We have all of that info in rasdaemon. If the machine explodes, one can simply
read out its database from the core file.
And if you don't run rasdaemon, you can read out dmesg from the vmcore where
the errors should have been dumped anyway.
So there's no need to add anything new to the kernel.
IMNSVHO.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
