Feb 7, 2025, 04:19 by qiuxu.zhuo@intel.com:

> Thanks for the report.
>
>> From: Ramses <>> ramses@well-founded.dev>> >
>> Sent: Friday, February 7, 2025 6:29 AM
>> To: Linux Edac <>> linux-edac@vger.kernel.org>> >
>> Subject: Flood of edac-related errors since 6.13
>>
>> Hi
>>
>> Since 6.13, I get a flood of the following messages in the logs of my intel n100
>> machine, always with the exact same memory address:
>>
>> jan 20 12:40:57 beelink kernel: EDAC MC: Ver: 3.0.0 jan 20 12:40:57 beelink
>> kernel: caller igen6_probe+0x1b2/0x83b [igen6_edac] mapping multiple BARs
>> jan 20 12:40:57 beelink kernel: EDAC MC0: Giving out device to module
>> igen6_edac controller Intel_client_SoC MC#0: DEV 0000:00:00.0 (POLLED) jan
>> 20 12:40:57 beelink kernel: EDAC igen6 MC0: HANDLING IBECC MEMORY
>> ERROR jan 20 12:40:57 beelink kernel: EDAC igen6 MC0: ADDR 0x7fffffffe0 jan
>> [...]
>> I assume this change is because of
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6
>> .13.1&id=e14232afa94445e03fc3a0291b07a68f3408c120
>>
>> The system works perfectly fine otherwise and I've had the message at boot
>> for as long as the logs go back (until mid october 2024). I didn't actually notice
>> it before, so I'm only know questioning what's its significance.
>>
>> Is there a possibility that this is a false positive, or is this definitely an
>> indication that something is wrong with the system's memory and I should
>> replace the DIMM?
>>
>
> It seemed like it was a false positive.
> I guess the readout ECC log was 0xffffffffffffffff. Do you have the opportunity to build
> the kernel with the 'CONFIG_EDAC_DEBUG=y' option enabled and then help to take
> the log?
>
> Thanks
>
> -Qiuxu
>

Thanks for your reply!

I recompiled the kernel with that option enabled, and attached the dmesg output to this email. Let me know if I can do anything else to help debug this.

Cheers, Ramses