All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramses <ramses@well-founded.dev>
To: Linux Edac <linux-edac@vger.kernel.org>
Subject: Flood of edac-related errors since 6.13
Date: Thu, 6 Feb 2025 23:28:55 +0100 (CET)	[thread overview]
Message-ID: <OISL8Rv--F-9@well-founded.dev> (raw)

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 20 12:40:57 beelink kernel: EDAC igen6: v2.5.1
jan 20 12:40:59 beelink kernel: EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
jan 20 12:40:59 beelink kernel: EDAC igen6 MC0: ADDR 0x7fffffffe0
jan 20 12:41:00 beelink kernel: EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
jan 20 12:41:00 beelink kernel: EDAC igen6 MC0: ADDR 0x7fffffffe0
jan 20 12:41:01 beelink kernel: EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
jan 20 12:41:01 beelink kernel: EDAC igen6 MC0: ADDR 0x7fffffffe0
jan 20 12:41:02 beelink kernel: EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
jan 20 12:41:02 beelink kernel: EDAC igen6 MC0: ADDR 0x7fffffffe0
jan 20 12:41:03 beelink kernel: EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
jan 20 12:41:04 beelink kernel: EDAC igen6 MC0: ADDR 0x7fffffffe0
jan 20 12:41:04 beelink kernel: EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
jan 20 12:41:05 beelink kernel: EDAC igen6 MC0: ADDR 0x7fffffffe0

On previous kernels, I only got this single message right after booting:

jan 20 03:17:45 beelink kernel: EDAC MC: Ver: 3.0.0
jan 20 03:17:45 beelink kernel: caller igen6_probe+0x191/0x810 [igen6_edac] mapping multiple BARs
jan 20 03:17:45 beelink kernel: EDAC MC0: Giving out device to module igen6_edac controller Intel_client_SoC MC#0: DEV 0000:00:00.0 (INTERRUPT)
jan 20 03:17:45 beelink kernel: EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
jan 20 03:17:45 beelink kernel: EDAC igen6 MC0: ADDR 0x7fffffffe0
jan 20 03:17:45 beelink kernel: EDAC igen6: v2.5.1

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?
I ran memtest for about two hours earlier and it didn't report any failure.

I'd like to hear your thoughts on this.

Cheers,
Ramses


             reply	other threads:[~2025-02-06 22:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 22:28 Ramses [this message]
2025-02-07  3:18 ` Flood of edac-related errors since 6.13 Zhuo, Qiuxu
2025-02-07  9:25   ` Ramses
2025-02-10  8:04     ` Zhuo, Qiuxu
2025-02-10  8:49       ` Ramses
2025-02-11  1:55         ` Zhuo, Qiuxu
2025-02-11 19:47           ` John
2025-02-12  8:35             ` Zhuo, Qiuxu
  -- strict thread matches above, loose matches on Subject: below --
2025-02-09 11:50 John

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=OISL8Rv--F-9@well-founded.dev \
    --to=ramses@well-founded.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.