Reboot after panic:

[Gene Laoyan]

My server rebooted unexpectedly and here is what was in the log...

08:43 Fri Jan 05 2007. Reboot after panic: SafetyTimer expired, INIT, IIP:0xe000000000c6a260 IFA:0x200000007effe024

What does this mean? It looks all foreign to me.

Thanks

[Gene Laoyan]

I must also add this partions is a member of a ServiceGuard cluster and hosts Integrity Virtual Machines - Windows Guests but has no Serviceguard packages running on it.

[John Guster]

here is similar situation..
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=301388&admit=-682735245+1168031339629+28353475

[Gene Laoyan]

Ran the following and here's what I got...

q4> trace event 0
stack trace for event 0
crash event was a INIT
Stack unwind reached bottom at depth, 1

wait_for_lock_spinner+0xb0
wait_for_lock_spinner+0xb0
q4>

What does this mean? To my eyes it looks bad for the processor.

[Sp4admin]

Hi Gene,

Is this the message from the syslog? did you check the shutdownlog. Problems like this I give HP a call to explain to me what it all means. wish I could be more help.

sp,

[Gene Laoyan]

It came from the /etc/shutdownlog
The syslog couldn't go back far enough.

[Patrick Wallek]

To see what occurred BEFORE the reboot/panic, you need to look at /var/adm/syslog/OLDsyslog.log.

I agree with one of the other responses. In cases where the system panics, HP is really the best place to turn to. If you have a support contract on this machine, by all means CALL HP. They will request that you send them several files. Once you send those they can go through them and tell you exactly what happened and what you need to do to fix the problem.