Why are EDAC errors still being logged after replacing the faulty hardware?
Issue
- Why EDAC errors are coming, Even there is no hardware issue in the system ?
-
Already contacted hardware vendor and replaced hardware, Still getting below EDAC errors in messages.
kernel: EDAC MC0: CE row 0, channel 1, label "": Corrected error (Branch=0, Channel 1), DRAM-Bank=1 RD RAS=15544 CAS=696, CE Err=0x800, Syndrome=0x700a7210(Memory or FBD configuration CRC read error)) kernel: EDAC MC0: CE row 0, channel 1, label "": Corrected error (Branch=0, Channel 1), DRAM-Bank=1 RD RAS=7546 CAS=956, CE Err=0x800, Syndrome=0x700a7210(Memory or FBD configuration CRC read error)) kernel: EDAC MC0: CE row 0, channel 1, label "": Corrected error (Branch=0, Channel 1), DRAM-Bank=3 RD RAS=8780 CAS=632, CE Err=0x800, Syndrome=0x700a7210(Memory or FBD configuration CRC read error)) kernel: EDAC MC0: CE row 1, channel 1, label "": Corrected error (Branch=0, Channel 1), DRAM-Bank=2 RD RAS=1680 CAS=2, CE Err=0x800, Syndrome=0x700a7210(Memory or FBD configuration CRC read error)) kernel: EDAC MC0: CE row 1, channel 1, label "": Corrected error (Branch=0, Channel 1), DRAM-Bank=3 RD RAS=10 CAS=6, CE Err=0x800, Syndrome=0x700a7210(Memory or FBD configuration CRC read error)) kernel: EDAC MC0: CE row 0, channel 1, label "": Corrected error (Branch=0, Channel 1), DRAM-Bank=5 RD RAS=9614 CAS=3052, CE Err=0x800, Syndrome=0x700a7210(Memory or FBD configuration CRC read error))
Environment
- Red Hat Enterprise Linux All Version
- EDAC
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.