- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Linux error message on Bl460C G1 "This is *NOT* a ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
06-06-2012 03:16 PM
06-06-2012 03:16 PM
Linux error message on Bl460C G1 "This is *NOT* a software problem!"
Hello Team,
I am having this message:
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 6 BANK 0 TSC 552b14c7e2e4
RIP !INEXACT! 10:ffffffff801a3d98
MCG status:RIPV MCIP
MCi status:
Error overflow
Uncorrected error
Error enabled
Processor context corrupt
MCA: BUS Level-0 Local-CPU-originated-request Generic Memory-access Request-timeout Error
BQ_DCU_READ_TYPE BQ_ERR_HARD_TYPE BQ_ERR_HARD_TYPE failure that caused IERR
MCE is observed
STATUS f200080020000800 MCGSTATUS 5
RIP: acpi_cstate_enter+0x10/0x19}
The IML for the suspicious blade shows:
Integrated Management Log
Class Last Update Initial Update Count Description
Icons Class Last_Update Initial_Update Count_
Network 01/08/2012 03:19 12/21/2011 16:38 3 o DNeetswcroiprkti oAnd_aopoteoroso Roedundancy Reduced (Slot 0, Port 3)
Network 01/08/2012 03:19 12/21/2011 16:38 2 Network Adapters Redundancy Reduced (Slot 2, Port 3)
Rack Infrastructure 04/06/2010 14:06 04/06/2010 14:06 1 Server Blade Enclosure Rack Name Changed (Enclosure Serial Number Unknown)
Network 07/18/2009 22:49 07/18/2009 22:47 1 Network Adapters Redundancy Reduced (Slot 0, Port 3)
Network 07/18/2009 22:49 07/18/2009 22:47 1 Network Adapters Redundancy Reduced (Slot 2, Port 3)
Maintenance 11/27/2011 05:00 03/03/2009 18:04 1 IML Cleared (iLO 2 user:OA 1236113769)
I see no hardware faiilures as the Linux message states. ¿Do I need to perform a firmware upgrade before start digging into the unknown?
Device Firmware Information
Bay Device Model ROM Version iLO Model iLO Firmware Version
3 ProLiant BL460c G1 I15 11/02/2008 iLO2 1.70 Dec 02 2008
My Onboard Admin FW is 2.41 Feb 24 2009
Thank you!
- Andrés.