Integrity Servers
Showing results for 
Search instead for 
Do you mean 

Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

Highlighted
Frequent Advisor

Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

[ Edited ]

Hi, please we need help to find out what is causing our rx8640 to crash. This server is online without errors since Feb-2012 but crash occurs when a reboot is issued and then the server generate crash about 3 or 4 times and after that became online without problems.

 

08:29 Sun Feb 26 2012. Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

 

I attached the crash file.

 

Thanks

 

P.S. This thread has been moved from  HP-UX>General to Servers > Integrity. -HP Forum Moderator

 

9 REPLIES
Acclaimed Contributor Acclaimed Contributor

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

MCA indicates a hardware problems.

Honored Contributor Honored Contributor

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

As Dennis said, MCA (Machine Check Abort) usually means a hardware problem somewhere - I don't think anyone on the forums here is going to decode a full crash dump for you (but I guess you never know!), you'll need to get a call logged with HP support for that. They have experts, who in my experience will pinpoint the issue fairly quickly for most panics.

 

And if you don't have a support contract? Well, now you know why you need one...


HTH

Duncan
Regular Advisor

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

Good Morning,

 

I'm only following my nose here, and make no claim to read registers, etc.  However, crashinfo.txt contains the following.

 

=======================================
  = Global Error Counters / kmem_writes =
  =======================================

scsi_bioerrors                    = 15
scsi_bioerrors_logged             = 0
scsi_async_write_bioerrors        = 0
scsi_async_write_bioerrors_logged = 0
sd_strategy_bioerrors             = 3
sd_strategy_async_write_bioerrors = 0
sd_epowerf_bioerrors              = 0
sd_epowerf_async_write_bioerrors  = 0

Note: There are scsi_bioerrors !
Please contact HP support referencing CRASHINFO_NOTE_SCSI1.

 

This confirms the likelihood of a hardware problem that other respondents have noted.  Best of luck!

Joe S.

Honored Contributor Honored Contributor

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

crashinfo is a hp support tool. The right place to interpret it is hp support.

 

At the beginning of crashinfo output you have:

 

Note: HP CONFIDENTIAL

 

 

 

Frequent Advisor

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

Hi,

 

I also had the same problem with my BL860 server so i got the solution below, Please see this it may help you :

 

http://expertisenpuru.com/reboot-after-panic-server-rebooted-automatically-in-hp-ux/

Acclaimed Contributor Acclaimed Contributor

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

[ Edited ]

>Please see this it may help you:

 

Your URL isn't working.

 

edit:

nslookup can't find your FQDN: www.expertisenpuru.com

Name resolution for the name expertisenpuru.com timed out after none of the configured DNS servers responded.

Frequent Advisor

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

Acclaimed Contributor Acclaimed Contributor

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

>It worked for me

 

Yes now it does but not way back then.

HPE Pro

Re: Help with crashinfo 11.23 Reboot after panic: MCA, IIP:0xe000000000664ae0 IFA:0x0000000000000045

Hi 

 

The link is guding/Leading  tocontacting HP Support As it is a hardware related Event.

 

I work for HPE

If you feel this solution was helpful please click the KUDOS! thumb below!