2.6.9-55.ELsmp EDAC Errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Howdy,

 

I just installed RedHat 4.5 on 64 identical nodes (Dual AMD Opteron 242
with 2GB ECC RAM).

 

4 of the nodes are logging errors similar to:

 

Jul 25 11:07:30 node1.local kernel: EDAC k8 MC0: extended error code:
ECC chipkill x4 error

Jul 25 11:07:30 node1.local sshd[3027]: error: Bind to port 22 on
0.0.0.0 failed: Address already in use.

Jul 25 11:07:31 node1.local kernel: EDAC k8 MC0: general bus error:
participating processor(local node response), time-out(no timeout)
memory transaction type(generic read), mem or i/o(mem access), cache
level(generic)

Jul 25 11:07:31 node1.local kernel: EDAC k8 MC0: extended error code:
ECC chipkill x4 error

Jul 25 11:07:32 node1.local kernel: EDAC k8 MC0: general bus error:
participating processor(local node response), time-out(no timeout)
memory transaction type(generic read), mem or i/o(mem access), cache
level(generic)

 

I previously had RedHat 4.0 installed on these nodes and didn't see any
EDAC errors.

 

I've run memtest86 on the 4 nodes (100 passes) and each of them passed
without error.

 

Does anyone know if it is possible to disable the EDAC checking and
error reporting?  Primarily because, these errors are logged every
second and in a short time fill up the /var partition.

 

Thanks for any info,

 

Mike

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list


[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux