- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- why MC_INITIATED?
Integrity Servers
1748034
Members
5427
Online
108757
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО01-13-2008 06:02 AM
тАО01-13-2008 06:02 AM
I just got this error on my rx8620:
Alert level 7: Fatal
Keyword: MC_INITIATED
Machine Check initiated
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 0
System State Change: HPMC processing
any idea why this happened? the system was working just well with about 30% CPU load and suddenly this error happened.
The rx has 4 cells with 4 CPUs on each cell, single partitioned.
Alert level 7: Fatal
Keyword: MC_INITIATED
Machine Check initiated
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 0
System State Change: HPMC processing
any idea why this happened? the system was working just well with about 30% CPU load and suddenly this error happened.
The rx has 4 cells with 4 CPUs on each cell, single partitioned.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2008 08:06 AM
тАО01-13-2008 08:06 AM
Re: why MC_INITIATED?
hi khalil;
├Д┬▒t seems that you have a hardware problem and mca occured. please contact your local support.
├Д┬▒t seems that you have a hardware problem and mca occured. please contact your local support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-14-2008 11:29 PM
тАО01-14-2008 11:29 PM
Solution
Machine Check is usually initiated by the hardware due to hardware inconsistencies or malfunctioning. MC is called MCA ( Machine Check Abort ) on Integrity systems. If the system is booted after this, check the MCA binary file under /var/tombstomes directory with appropriate timestamp. If the system is not bootable, one can collect mca information from EFI shell using following:
Shell> fsX:
fsX:> cd \EFI\HP\TOOLS
fsX:> errdump all mca > mca.txt ( or screen log)
(X is proper hard drive number)
You need to send this data to HP Support to get it analysed and know the root cause. If you want you can attach it here. MP FPL would be helpful as well.
Shell> fsX:
fsX:> cd \EFI\HP\TOOLS
fsX:> errdump all mca > mca.txt ( or screen log)
(X is proper hard drive number)
You need to send this data to HP Support to get it analysed and know the root cause. If you want you can attach it here. MP FPL would be helpful as well.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP