From: Orion Poplawski <orion@nwra.com>
To: linux-edac@vger.kernel.org
Subject: EDAC igen6 error messages at boot
Date: Fri, 21 Oct 2022 10:08:10 -0600 [thread overview]
Message-ID: <11240651-e924-8d8b-c2f7-c6e031e6b95a@nwra.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
We have a Dell XPS 15 9520 running 5.15.0-52-generic (Ubuntu 20.04) and get
the following at boot:
[ 0.981641] EDAC MC: Ver: 3.0.0
[ 31.801126] caller igen6_probe+0x176/0x7b0 [igen6_edac] mapping multiple BARs
[ 31.805272] EDAC MC0: Giving out device to module igen6_edac controller
Intel_client_SoC MC#0: DEV 0000:00:00.0 (INTERRUPT)
[ 31.810599] EDAC MC1: Giving out device to module igen6_edac controller
Intel_client_SoC MC#1: DEV 0000:00:00.0 (INTERRUPT)
[ 31.810616] EDAC igen6 MC1: HANDLING IBECC MEMORY ERROR
[ 31.810617] EDAC igen6 MC1: ADDR 0x7fffffffe0
[ 31.810619] EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
[ 31.810620] EDAC igen6 MC0: ADDR 0x7fffffffe0
[ 31.811957] EDAC igen6: v2.5
logwatch triggers on the ERROR and reports them.
However, from some searching around this seems to be fairly common, so I'm
guessing they are somewhat spurious. Unfortunately the messages seem to be
similar to what you would see with an actual memory error so don't want to
completely ignore them.
Could anyone shed some more light here?
Thanks!
--
Orion Poplawski
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@nwra.com
Boulder, CO 80301 https://www.nwra.com/
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3847 bytes --]
next reply other threads:[~2022-10-21 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 16:08 Orion Poplawski [this message]
2022-10-25 2:46 ` EDAC igen6 error messages at boot Zhuo, Qiuxu
2022-10-25 2:58 ` Orion Poplawski
2022-10-25 3:13 ` Zhuo, Qiuxu
2022-10-25 15:28 ` Orion Poplawski
2022-10-26 5:58 ` Zhuo, Qiuxu
2022-11-02 14:36 ` Orion Poplawski
2022-11-04 5:07 ` Zhuo, Qiuxu
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=11240651-e924-8d8b-c2f7-c6e031e6b95a@nwra.com \
--to=orion@nwra.com \
--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