- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- EDAC i5000 MC0: NON-FATAL ERRORS Found!!!
ProLiant Servers (ML,DL,SL)
1822148
Members
4112
Online
109640
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2009 07:03 AM
11-09-2009 07:03 AM
EDAC i5000 MC0: NON-FATAL ERRORS Found!!!
Hello!
I administer a ProLiant ML350 G5 server which is running Debian Lenny AMD64 (Linux filerpri 2.6.26-2-amd64 #1 SMP Thu Nov 5 02:23:12 UTC 2009 x86_64 GNU/Linux). A few days ago some strange messages writes on the console and to the syslog too.
Examples:
Nov 8 06:25:02 filerpri kernel: [160849.062055] EDAC i5000 MC0: NON-FATAL ERRORS Found!!! 1st NON-FATAL Err Reg= 0x2000
Nov 8 06:25:02 filerpri kernel: [160849.062108] EDAC MC0: CE row 0, channel 0, label "": (Branch=0 DRAM-Bank=3 RDWR=Read RAS=6421 CAS=112, CE Err=0x2000)
Nov 8 07:07:22 filerpri kernel: [163491.047139] EDAC i5000 MC0: NON-FATAL ERRORS Found!!! 1st NON-FATAL Err Reg= 0x10000
Nov 8 07:07:22 filerpri kernel: [163491.047187] EDAC MC0: CE row 0, channel 0, label "": (Branch=0 DRAM-Bank=3 RDWR=Read RAS=6144 CAS=0, CE Err=0x10000)
The console is totally unusable because of them: about 1-3 seconds a new message appears with various RAS/CAS values. Mostly the "Reg" value is 0x2000, but sometimes it is 0x10000.
I did some research on this messages and found no exact solution. Is it a hardware (memory) failure or just an annoying kernel bug? How can I fix it or get rid of them?
Thanks for all help!
Sincerely,
Endre
I administer a ProLiant ML350 G5 server which is running Debian Lenny AMD64 (Linux filerpri 2.6.26-2-amd64 #1 SMP Thu Nov 5 02:23:12 UTC 2009 x86_64 GNU/Linux). A few days ago some strange messages writes on the console and to the syslog too.
Examples:
Nov 8 06:25:02 filerpri kernel: [160849.062055] EDAC i5000 MC0: NON-FATAL ERRORS Found!!! 1st NON-FATAL Err Reg= 0x2000
Nov 8 06:25:02 filerpri kernel: [160849.062108] EDAC MC0: CE row 0, channel 0, label "": (Branch=0 DRAM-Bank=3 RDWR=Read RAS=6421 CAS=112, CE Err=0x2000)
Nov 8 07:07:22 filerpri kernel: [163491.047139] EDAC i5000 MC0: NON-FATAL ERRORS Found!!! 1st NON-FATAL Err Reg= 0x10000
Nov 8 07:07:22 filerpri kernel: [163491.047187] EDAC MC0: CE row 0, channel 0, label "": (Branch=0 DRAM-Bank=3 RDWR=Read RAS=6144 CAS=0, CE Err=0x10000)
The console is totally unusable because of them: about 1-3 seconds a new message appears with various RAS/CAS values. Mostly the "Reg" value is 0x2000, but sometimes it is 0x10000.
I did some research on this messages and found no exact solution. Is it a hardware (memory) failure or just an annoying kernel bug? How can I fix it or get rid of them?
Thanks for all help!
Sincerely,
Endre
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP