Page MenuHomeFreeBSD

mca: accumulate statistics of MCA events and export as hw.mca.stats
Needs ReviewPublic

Authored by glebius on Jan 13 2022, 7:06 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Dec 18, 10:34 PM
Unknown Object (File)
Nov 22 2024, 1:17 PM
Unknown Object (File)
Nov 20 2024, 3:31 PM
Unknown Object (File)
Nov 10 2024, 10:35 AM
Unknown Object (File)
Oct 21 2024, 4:35 AM
Unknown Object (File)
Oct 19 2024, 9:06 PM
Unknown Object (File)
Oct 7 2024, 11:58 PM
Unknown Object (File)
Oct 6 2024, 3:48 AM
Subscribers

Details

Reviewers
mav

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 43906
Build 40794: arc lint + arc unit

Event Timeline

I have doubts such statistics would be usable. Same memory error can be reported in different ways depending how it was found (read, write, scrub, etc). Same time error reported by cache may mean faulty cache or memory error just detected by cache. Excessive simplification like this would tangle things even more. If you wish to have a simple counter, I would only differentiate corrected, uncorrected recoverable and uncorrected unrecoverable (the last should actually end up in panic now, but in some cases could just kill the process). If more detailed information is needed, then some user-space tool like mcelog can get raw data via the sysctl interface.