linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: repeating [Hardware Error]: Corrected error, no action required.
Date: Wed, 9 Jun 2021 20:27:26 +0200	[thread overview]
Message-ID: <cba1f224-7a21-7a1f-3f82-6f7e98a274d0@gmx.de> (raw)

My syslog messages show at a hardened Gentoo

# uname -a
Linux mr-fox 5.12.9 #8 SMP Thu Jun 3 17:59:32 CEST 2021 x86_64 AMD Ryzen
9 5950X 16-Core Processor AuthenticAMD GNU/Linux
mr-fox ~ #

repeating entries every 5 mins like (always same address
0x000000031fb566e0):

Jun  9 16:21:24 mr-fox kernel: mce: [Hardware Error]: Machine check
events logged
Jun  9 16:21:24 mr-fox kernel: [Hardware Error]: Corrected error, no
action required.
Jun  9 16:21:24 mr-fox kernel: [Hardware Error]: CPU:0 (19:21:0)
MC17_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc2040000000011b
Jun  9 16:21:24 mr-fox kernel: [Hardware Error]: Error Addr:
0x000000031fb566e0
Jun  9 16:21:24 mr-fox kernel: [Hardware Error]: IPID:
0x0000009600050f00, Syndrome: 0x33fa01000a800101
Jun  9 16:21:24 mr-fox kernel: [Hardware Error]: Unified Memory
Controller Ext. Error Code: 0, DRAM ECC error.
Jun  9 16:21:24 mr-fox kernel: EDAC MC0: 1 CE on mc#0csrow#1channel#0
(csrow:1 channel:0 page:0xcaed59 offset:0x8e0 grain:64 syndrome:0x100)
Jun  9 16:21:24 mr-fox kernel: [Hardware Error]: cache level: L3/GEN,
tx: GEN, mem-tx: RD


A hw mem check by Hetzner didn't found anything.
May I asked whether I sahll worry about or not ?


--
Toralf

             reply	other threads:[~2021-06-09 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 18:27 Toralf Förster [this message]
2021-06-10  8:40 ` repeating [Hardware Error]: Corrected error, no action required Oleksandr Natalenko

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=cba1f224-7a21-7a1f-3f82-6f7e98a274d0@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).