From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: linux-edac@vger.kernel.org
Subject: [ANN] Rasdaemon version 0.8.1 released
Date: Tue, 16 Jul 2024 12:08:40 +0200 [thread overview]
Message-ID: <20240716120840.73101250@sal.lan> (raw)
Hi all,
Just released today a new version of the rasdaemon with:
* Lots of new labels added;
* Added a script to check coding style;
* Detect non-x86 CPUs on MCE handler;
* Added an error injection script for QEMU;
* Allow external scripts to handle memory errors;
* Fix ARM processor compatibility with upstream;
* Add support for CXL events;
* Add support for microcode and PPIN on MCE traces;
* Add non-standard decodes for Yitian and Jaguarmicro;
* Add EmeraldRapids Intel CPU;
* Add Corrected Internal Error for aer_cor_errors;
* Add support for disable ras events in runtime;
* Improve AMD SMCA handling;
* Fix several compilation and runtime issues;
* Add option on ras-mc-ctl to exclude old events from reports;
* Other improvements at ras-mc-ctl tool;
* Documentation updates;
* Code cleanups;
* Coding style cleanups.
The main git repository is hosted at:
https://github.com/mchehab/rasdaemon
Source tarballs at:
https://www.infradead.org/~mchehab/rasdaemon/
Thanks,
Mauro
reply other threads:[~2024-07-16 10:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240716120840.73101250@sal.lan \
--to=mchehab+huawei@kernel.org \
--cc=linux-edac@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox