Operating System - HP-UX
1754380 Members
3135 Online
108813 Solutions
New Discussion юеВ

savecrash INDEX file question

 
SOLVED
Go to solution
Jack C. Mahaffey
Super Advisor

savecrash INDEX file question

I had a server reboot this morning. Boot acted like the power cord to the UPS was pulled. e.g. no shutdown messages in /etc/rc.log or /var/adm/syslogd/syslog.log.

A savecrash crash directory was created. A copy of the INDEX file is at the end of this post.

Any idea what 'panic , isr.ior = 0'4000c.0'5415b60' represents? A memory error?

Jack....

===================================================================================

1 comment savecrash crash dump INDEX file
2 version 2
3 hostname freoptp2
4 modelname 9000/800/K380
5 panic , isr.ior = 0'4000c.0'5415b60
6 dumptime 1147081598 Mon May 8 05:46:38 EDT 2006
7 savetime 1147082377 Mon May 8 05:59:37 EDT 2006
8 release @(#)B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov 5 22:38:19 PST 1997
9
10 memsize 2147471360
11 chunksize 134217728
12 module /stand/vmunix vmunix 18146152 3504616177
13 warning savecrash: savecrash running in the background
14
15 image image.1.1 0x0000000000000000 0x0000000007ff8000 0x0000000000000000 0x000000000000874f 506461392
16 image image.1.2 0x0000000000000000 0x0000000007ff8000 0x0000000000008750 0x0000000000012cbf 628126545
17 image image.1.3 0x0000000000000000 0x0000000007ff9000 0x0000000000012cc0 0x000000000001acb7 759612475
18 image image.1.4 0x0000000000000000 0x0000000007ff9000 0x000000000001acb8 0x0000000000022caf 516927602
19 image image.1.5 0x0000000000000000 0x0000000007ffb000 0x0000000000022cb0 0x000000000002eba7 55579016
20 image image.1.6 0x0000000000000000 0x0000000007ff3000 0x000000000002eba8 0x00000000000779d7 2883153380
21 image image.1.7 0x0000000000000000 0x0000000000c31000 0x00000000000779d8 0x000000000007fffc 24396717
4 REPLIES 4
melvyn burnard
Honored Contributor
Solution

Re: savecrash INDEX file question

This type of panic (panic , isr.ior = 0'4000c.0'5415b60) is usually caused by:
1) Hardware failure
2) Someone issuing a TOC
3) Serviceguard issuing a TOC.

I would recommend you get the dump analysed by the HP Response Centre
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Steven E. Protter
Exalted Contributor

Re: savecrash INDEX file question

Shalom,

Processing a crash dump with q4:
http://www.google.com/url?sa=t&ct=res&cd=3&url=http%3A%2F%2Fdocs.hp.com%2Fen%2Fsysdmp-62001%2Fsysdmp-62001.pdf&ei=z2dfROG-Jp6U-gG4mqS-AQ&sig2=vMOjhHMylVZidSYusLLOdA

http://docs.hp.com/en/sysdmp-62001/sysdmp-62001.pdf
white paper

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Jack C. Mahaffey
Super Advisor

Re: savecrash INDEX file question

melvyn, thanks... I'll put in a call.

Jack...
Josiah Henline
Valued Contributor

Re: savecrash INDEX file question

Check the /var/tombstones directory. If the ts99 file has a valid timestamp, then you have a hardware issue. q4 will also tell you if it was a TOC(transfer of control) or HPMC(high priority machine check).
If at first you don't succeed, read the man page.