Good morning all,
I have recently installed Proxom on top of a valilla Debian Buster installation, following the article https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster.
I have noticed that whilst before installing Proxmox, the
Basically the output looks like this:
Instead of looking like this:
Upon checking
I am running Proxmox VE (fully updated) on a HPE DL380 Gen. 8, with 2 * Xeon E5-2450L (Sandy Bridge) and 12 * 16GB Sasung M393B2G70BH0-YH9 PC3l-10600R-09.
I am using the PVE-NO-SUBSCRIPTION repository.
I have seen few threads stating that with the latest kernel this issue is affecting Ryzen CPUs such as https://forum.proxmox.com/threads/patch-x570-ryzen-edac-support-into-pve-6-1.63744/, https://forum.proxmox.com/threads/no-more-ecc-since-kernel-5-3.64047/#post-290931 and https://forum.proxmox.com/threads/linux-kernel-5-3-for-proxmox-ve.59398/page-3#post-284619.
Is this something that is affecting other CPUs or is this an issue specific to Ryzen?
Are other people on Sandy Bridge facing this same problem? If so, how could it be overcome?
Thank you!
I have recently installed Proxom on top of a valilla Debian Buster installation, following the article https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster.
I have noticed that whilst before installing Proxmox, the
edac-utils -v
command was showing information about all the memory modules, since I installed Proxmox, I can no loner see information for each memory module; basically it lacks all the csrow* entries.Basically the output looks like this:
Code:
# edac-util -v
mc0: 0 Uncorrected Errors with no DIMM info
mc0: 0 Corrected Errors with no DIMM info
mc1: 0 Uncorrected Errors with no DIMM info
mc1: 0 Corrected Errors with no DIMM info
Instead of looking like this:
Code:
# edac-util -v
mc0: 0 Uncorrected Errors with no DIMM info
mc0: 0 Corrected Errors with no DIMM info
mc0: csrow0: 0 Uncorrected Errors
mc0: csrow0: ch0: 0 Corrected Errors
mc0: csrow0: ch1: 0 Corrected Errors
mc0: csrow1: 0 Uncorrected Errors
mc0: csrow1: ch0: 0 Corrected Errors
mc0: csrow1: ch1: 0 Corrected Errors
mc0: csrow2: 0 Uncorrected Errors
mc0: csrow2: ch0: 0 Corrected Errors
mc0: csrow2: ch1: 0 Corrected Errors
mc0: csrow3: 0 Uncorrected Errors
mc0: csrow3: ch0: 0 Corrected Errors
mc0: csrow3: ch1: 0 Corrected Errors
mc0: csrow4: 0 Uncorrected Errors
mc0: csrow4: ch0: 0 Corrected Errors
mc0: csrow4: ch1: 0 Corrected Errors
mc0: csrow5: 0 Uncorrected Errors
mc0: csrow5: ch0: 0 Corrected Errors
mc0: csrow5: ch1: 0 Corrected Errors
mc1: 0 Uncorrected Errors with no DIMM info
mc1: 0 Corrected Errors with no DIMM info
mc1: csrow0: 0 Uncorrected Errors
mc1: csrow0: ch0: 0 Corrected Errors
mc1: csrow0: ch1: 0 Corrected Errors
mc1: csrow1: 0 Uncorrected Errors
mc1: csrow1: ch0: 0 Corrected Errors
mc1: csrow1: ch1: 0 Corrected Errors
mc1: csrow2: 0 Uncorrected Errors
mc1: csrow2: ch0: 0 Corrected Errors
mc1: csrow2: ch1: 0 Corrected Errors
mc1: csrow3: 0 Uncorrected Errors
mc1: csrow3: ch0: 0 Corrected Errors
mc1: csrow3: ch1: 0 Corrected Errors
mc1: csrow4: 0 Uncorrected Errors
mc1: csrow4: ch0: 0 Corrected Errors
mc1: csrow4: ch1: 0 Corrected Errors
mc1: csrow5: 0 Uncorrected Errors
mc1: csrow5: ch0: 0 Corrected Errors
mc1: csrow5: ch1: 0 Corrected Errors
Upon checking
/sys/devices/system/edac/mc/mc*/
I can see that there are no csrow* entries anymore.I am running Proxmox VE (fully updated) on a HPE DL380 Gen. 8, with 2 * Xeon E5-2450L (Sandy Bridge) and 12 * 16GB Sasung M393B2G70BH0-YH9 PC3l-10600R-09.
I am using the PVE-NO-SUBSCRIPTION repository.
I have seen few threads stating that with the latest kernel this issue is affecting Ryzen CPUs such as https://forum.proxmox.com/threads/patch-x570-ryzen-edac-support-into-pve-6-1.63744/, https://forum.proxmox.com/threads/no-more-ecc-since-kernel-5-3.64047/#post-290931 and https://forum.proxmox.com/threads/linux-kernel-5-3-for-proxmox-ve.59398/page-3#post-284619.
Is this something that is affecting other CPUs or is this an issue specific to Ryzen?
Are other people on Sandy Bridge facing this same problem? If so, how could it be overcome?
Thank you!
Last edited: