Results 1 to 6 of 6
Does anyone know how to interpret the following MCE log
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 4 0 data cache TSC a4d4c13bd54b26
...
- 09-03-2009 #1Just Joined!
- Join Date
- Dec 2007
- Posts
- 6
MCE Help
Does anyone know how to interpret the following MCE log
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 4 0 data cache TSC a4d4c13bd54b26
Data cache ECC error (syndrome 2a)
bit46 = corrected ecc error
bit57 = processor context corrupt
bit61 = error uncorrected
memory/cache error 'data write mem transaction, data transaction, level 1'
STATUS b615400000000145 MCGSTATUS 4
Thanks in advance
- 09-04-2009 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
The driver has detected a hardware error in the cache memory. You need to send the board in for repair or replacement.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 09-04-2009 #3Just Joined!
- Join Date
- Dec 2007
- Posts
- 6
- 09-04-2009 #4Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
I thought the MCE error message was quite clear. CPU #4 has an unrecoverable cache memory error. Run the system diagnostics, or download them from HP and run them (you will probably need to create a bootable CD or USB drive with the diagnostic package - instructions on how to do that should be on the HP support site). My guess is that if you run the system board tests in a continuous manner, it will fail after awhile.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 09-04-2009 #5Just Joined!
- Join Date
- Dec 2007
- Posts
- 6
- 09-04-2009 #6Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
As I said. It seems perfectly clear to me - interpretation not needed. Does this happen frequently, or only once? If only once, it might have been a transient problem - cosmic rays perhaps? If it recurs, then it is likely a hardware problem. It is a CPU problem since it is a level 1 cache error (next to last line). The last line (STATUS) is probably only meaningful to the CPU manufacturer.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!


Reply With Quote
