Bad Memory - Revision history

Leo: Added categories and navbox

2021-12-30T01:21:17Z

Added categories and navbox

← Older revision		Revision as of 01:21, 30 December 2021
Line 109:		Line 109:

	This is not an HP product-specific issue but rather a behavior of the Intel Xeon Processor E7 family\|sign=HP Support Center\|source=https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03282091}}One resolution is to go into the BIOS and set the <code>Minimum Processor Idle Power Package State</code> from <code>Package C3 State</code> to <code>No Package State</code>.		This is not an HP product-specific issue but rather a behavior of the Intel Xeon Processor E7 family\|sign=HP Support Center\|source=https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03282091}}One resolution is to go into the BIOS and set the <code>Minimum Processor Idle Power Package State</code> from <code>Package C3 State</code> to <code>No Package State</code>.

			{{Navbox Hardware}}
			[[Category:Hardware]]

Leo at 20:13, 14 September 2020

2020-09-14T20:13:24Z

@@ Line 1: / Line 1: @@
-== Memory Error Logs ==
+==Memory Error Logs==
-=== Generic undefined request ===
+=== Memory Scrubbing Error ===
 This is on a ProLiant DL580 G7. The system logs show the following machine check exception errors:
 {{Highlight
@@ Line 36: / Line 104: @@
 | lang = text
 }}
-After some searching, this appears to be a known issue for HPs with this particular CPU. HP has an advisory on this issue:
+After some searching, this appears to be a known issue for this model of HPs with this particular CPU. The CPU of the server above is a <code>Intel(R) Xeon(R) CPU E7- 4830  @ 2.13GHz</code>. The Intel Xeon E7 family is known to have this issue and HP has an advisory about this:{{Quote|quote=Certain ProLiant servers utilizing Intel Xeon E7 Family processors may experience Correctable Machine Check (CMC) Memory Errors. These CMC errors are not operating system-dependent and may occur with any operating system. With high-speed processor busses, it is normal for a low occurrence of CMC memory error events to occur. However, on rare occasions, a higher than expected number of CMC memory errors may be logged in the IA32_MC8_Status Model-Specific Register (MSR) or IA32_MC9_Status MSR of the processors across a single processor package.
-* https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03282091
+This is not an HP product-specific issue but rather a behavior of the Intel Xeon Processor E7 family|sign=HP Support Center|source=https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03282091}}One resolution is to go into the BIOS and set the <code>Minimum Processor Idle Power Package State</code> from <code>Package C3 State</code> to <code>No Package State</code>.

Leo: Created page with "== Memory Error Logs == === Generic undefined request === This is on a ProLiant DL580 G7. The system logs show the following machine check exception errors: {{Highlight | cod..."

2020-09-14T18:33:31Z

Created page with "== Memory Error Logs == === Generic undefined request === This is on a ProLiant DL580 G7. The system logs show the following machine check exception errors: {{Highlight | cod..."

New page

== Memory Error Logs ==

=== Generic undefined request ===
This is on a ProLiant DL580 G7. The system logs show the following machine check exception errors:
{{Highlight
| code = Sep 10 00:31:09 galaxy kernel: [31916012.191742] mce: [Hardware Error]: Machine check events logged
Sep 10 00:31:09 galaxy kernel: mce: [Hardware Error]: Machine check events logged
Sep 10 00:31:09 galaxy mcelog: Hardware event. This is not a software error.
Sep 10 00:31:09 galaxy mcelog: MCE 0
Sep 10 00:31:09 galaxy mcelog: CPU 24 BANK 9
Sep 10 00:31:09 galaxy mcelog: TIME 1599719469 Thu Sep 10 00:31:09 2020
Sep 10 00:31:09 galaxy mcelog: MCG status:
Sep 10 00:31:09 galaxy mcelog: MCi status:
Sep 10 00:31:09 galaxy mcelog: Error overflow
Sep 10 00:31:09 galaxy mcelog: Corrected error
Sep 10 00:31:09 galaxy mcelog: Error enabled
Sep 10 00:31:09 galaxy mcelog: MCA: MEMORY CONTROLLER GEN_CHANNEL0_ERR
Sep 10 00:31:09 galaxy mcelog: Transaction: Generic undefined request
Sep 10 00:31:09 galaxy mcelog: STATUS d000014000310080 MCGSTATUS 0
Sep 10 00:31:09 galaxy mcelog: MCGCAP 1000c18 APICID c0 SOCKETID 3
Sep 10 00:31:09 galaxy mcelog: CPUID Vendor Intel Family 6 Model 47
Sep 10 00:31:09 galaxy mcelog: Hardware event. This is not a software error.
Sep 10 00:31:09 galaxy mcelog: MCE 1
Sep 10 00:31:09 galaxy mcelog: CPU 24 BANK 9
Sep 10 00:31:09 galaxy mcelog: TIME 1599719469 Thu Sep 10 00:31:09 2020
Sep 10 00:31:09 galaxy mcelog: MCG status:
Sep 10 00:31:09 galaxy mcelog: MCi status:
Sep 10 00:31:09 galaxy mcelog: Error overflow
Sep 10 00:31:09 galaxy mcelog: Corrected error
Sep 10 00:31:09 galaxy mcelog: Error enabled
Sep 10 00:31:09 galaxy mcelog: MCA: MEMORY CONTROLLER GEN_CHANNELunspecified_ERR
Sep 10 00:31:09 galaxy mcelog: Transaction: Generic undefined request
Sep 10 00:31:09 galaxy mcelog: STATUS d0000780000a008f MCGSTATUS 0
Sep 10 00:31:09 galaxy mcelog: MCGCAP 1000c18 APICID c0 SOCKETID 3
Sep 10 00:31:09 galaxy mcelog: CPUID Vendor Intel Family 6 Model 47
| lang = text
}}
After some searching, this appears to be a known issue for HPs with this particular CPU. HP has an advisory on this issue:

* https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03282091
{{Quote|quote=Certain ProLiant servers utilizing Intel Xeon E7 Family processors may experience Correctable Machine Check (CMC) Memory Errors. These CMC errors are not operating system-dependent and may occur with any operating system. With high-speed processor busses, it is normal for a low occurrence of CMC memory error events to occur. However, on rare occasions, a higher than expected number of CMC memory errors may be logged in the IA32_MC8_Status Model-Specific Register (MSR) or IA32_MC9_Status MSR of the processors across a single processor package.|sign=HP Support Center|source=https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03282091}}