- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- rx7640
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
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
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
тАО11-18-2009 01:54 PM
тАО11-18-2009 01:54 PM
rx7640
Has anyone seen these errors before? If so do you know what they mean?
For example, selecting an alert level threshold of 3
selects all events with alert levels of 3 or higher.
Please select alert level threshold: 3
Switching to alert level 3 filter.
[vmhint02-c1] MP:VWR (
Log Entry 17178: 11/18/2009 20:23:32
Alert level 7: Fatal
Keyword: MC_INITIATED
Machine Check initiated
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 8
System State Change: HPMC processing
0xf480009818e008db 0x000000000000000b
0xeb00009818e008dc 0x010000004b0457c4
Log Entry 17165: 11/18/2009 20:23:31
Alert level 7: Fatal
Keyword: MC_INITIATED
Machine Check initiated
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 12
System State Change: HPMC processing
0xf48000981ce008c4 0x000000000000000b
0xeb0000981ce008c5 0x010000004b0457c3
[vmhint02-c1] MP:VWR (
Log Entry 17164: 11/18/2009 20:23:31
Alert level 7: Fatal
Keyword: MC_INITIATED
Machine Check initiated
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 13
System State Change: HPMC processing
0xf48000981de008c2 0x000000000000000b
0xeb0000981de008c3 0x010000004b0457c3
Log Entry 17163: 11/18/2009 20:23:30
Alert level 7: Fatal
Keyword: MC_INITIATED
Machine Check initiated
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 9
System State Change: HPMC processing
0xf480009819e008c0 0x000000000000000b
0xeb00009819e008c1 0x010000004b0457c2
[vmhint02-c1] MP:VWR (
Log Entry 17150: 11/18/2009 20:22:00
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 0
0x6b00000200e008ab 0x010000004b045768
Log Entry 17145: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 4
0x6b00000204e008a2 0x010000004b045767
Log Entry 17144: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 9
0x6b00000209e008a1 0x010000004b045767
[vmhint02-c1] MP:VWR (
Log Entry 17143: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 8
0x6b00000208e008a0 0x010000004b045767
Log Entry 17141: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 1
0x6b00000201e0089d 0x010000004b045767
Log Entry 17139: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 12
0x6b0000020ce0089a 0x010000004b045767
[vmhint02-c1] MP:VWR (
Log Entry 17137: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 5
0x6b00000205e00897 0x010000004b045767
Log Entry 17136: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 13
0x6b0000020de00896 0x010000004b045767
Log Entry 17129: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 8
0x6b00000218e00889 0x010000004b045767
[vmhint02-c1] MP:VWR (
Log Entry 17128: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 1
0x6b00000211e00888 0x010000004b045767
Log Entry 17127: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 9
0x6b00000219e00887 0x010000004b045767
Log Entry 17125: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 12
0x6b0000021ce00884 0x010000004b045767
[vmhint02-c1] MP:VWR (
Log Entry 17123: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 13
0x6b0000021de00881 0x010000004b045767
Log Entry 17122: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 5
0x6b00000215e00880 0x010000004b045767
Log Entry 17121: 11/18/2009 20:21:59
Alert level 3: Warning
Keyword: BAD_OS_MCA_CHECKSUM
Bad OS MCA checksum
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 4
0x6b00000214e0087f 0x010000004b045767
thanks
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2009 03:45 PM
тАО11-18-2009 03:45 PM
Re: rx7640
These entries are part of the forward progess log (FPL). The recommended action given for the event "BAD_OS_MCA_CHECKSUM" is "Reboot system to allow vector to be re-registered"
http://h71000.www7.hp.com/doc/83final/wbem/wbemproviders_fpl.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2009 09:18 PM
тАО11-18-2009 09:18 PM
Re: rx7640
It is HPMC. Restart your machine and check.
Contact HP response centre.
Regards,
Sooraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-19-2009 04:14 AM
тАО11-19-2009 04:14 AM
Re: rx7640
I guess you had an machine check abort (MCA) before the operating system was loaded (maybe during reboot).
Thus there was no OS handler available and the system should have reset.
You did not write what OS you have. For HPUX, you should have now new binary MCA logfiles in /var/tombstones that can be analyzed by HP support (if you want to know the reason for the MCA).
The MCA log can also be collected in EFI shell with
errdump all mca
in ASCII format.
Best regards
Stefan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-19-2009 04:21 AM
тАО11-19-2009 04:21 AM
Re: rx7640
thanks
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-22-2009 07:51 AM
тАО11-22-2009 07:51 AM
Re: rx7640
can open a case with HP so as to get the actual reasons analysed. This is for sure a MC that is Machine Check Alert from the Hardware.
This can be checked with the HP support.
regards
sujit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2009 01:03 PM
тАО12-28-2009 01:03 PM
Re: rx7640
Thanks
Jon