Re: too late to the party?
According to the upstream documentation, rasdaemon particularly has to do with ECC errors (not all of which are correctable).
https://github.com/alexandrelimassantana/rasdaemon
On August 27, 2024 2:12:10 PM MST, DdB <debianlist@potentially-spam.de-bruyn.de> wrote:
>Am 27.08.2024 um 18:17 schrieb Soren Stoutner:
>> Google indicates rasdaemon has to do with hardware memory errors. If I
>> were you I would scan the system with Memtest86+.
>>
>Wow! That seems extremely unlikely to me, because my hardware has lots
>of ECC RAM, which means, RAM errors should
>
>1. self correct
>and
>2. produce a different kind of message
>
>from dmesg: ECC is properly recognized and EDAC is running
>
>> [ 8.334662] EDAC MC0: Giving out device to module amd64_edac controller F17h_M30h: DEV 0000:00:18.3 (INTERRUPT)
>> [ 8.335358] EDAC amd64: Node 1: DRAM ECC enabled.
>
>That is why i dont think, memtest would even work as expected.
>
>Will consider it anyhow, once the machine is less busy.
>
--
Soren Stoutner
soren@stoutner.com
Reply to: