rx7640

Jon Steele — Wed, 18 Nov 2009 21:54:48 GMT

Hi,

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 (,,+,-,?,F,L,J,D,K,R,T,A,C,U,^B) > [vmhint02-c1]
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 (,,+,-,?,F,L,J,D,K,R,T,A,C,U,^B) > [vmhint02-c1]
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 (,,+,-,?,F,L,J,D,K,R,T,A,C,U,^B) > [vmhint02-c1]
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 (,,+,-,?,F,L,J,D,K,R,T,A,C,U,^B) > [vmhint02-c1]
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 (,,+,-,?,F,L,J,D,K,R,T,A,C,U,^B) > [vmhint02-c1]
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 (,,+,-,?,F,L,J,D,K,R,T,A,C,U,^B) > [vmhint02-c1]
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 (,,+,-,?,F,L,J,D,K,R,T,A,C,U,^B) > [vmhint02-c1]
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

Re: rx7640

Sameer_Nirmal — Wed, 18 Nov 2009 23:45:21 GMT

It means that there were multiple HPMC initiations (MC_INITIATED) by the respective CPUs on the system and the system tried to intimate that to the OS through an OS registered address vector. But oh well the address is bad or rather absent since the checksum match failed for some reason.

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

Re: rx7640

SoorajCleris — Thu, 19 Nov 2009 05:18:35 GMT

Hi,

It is HPMC. Restart your machine and check.

Contact HP response centre.

Regards,
Sooraj

Re: rx7640

Stefan Stechemesser — Thu, 19 Nov 2009 12:14:06 GMT

Hi,

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

Re: rx7640

Jon Steele — Thu, 19 Nov 2009 12:21:50 GMT

I Had loaded 11.i ver 2 OS. It booted up fine. I made my partition to include both cell boards. It worked fine for awhile. I then go some memory errors as well as those other errors. I replaced the memory and the machine worked fine for a couple of hours then I started getting these errors again. Any thoughts?
thanks
Jon

Re: rx7640

sujit kumar singh — Sun, 22 Nov 2009 15:51:10 GMT

Hi

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

Re: rx7640

Jon Steele — Mon, 28 Dec 2009 21:03:02 GMT

HP is going out there.
Thanks
Jon

topic Re: rx7640 in Integrity Servers

rx7640

Re: rx7640

Re: rx7640

Re: rx7640

Re: rx7640

Re: rx7640

Re: rx7640