System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Note: Crash event 0 was a PANIC !

 
Highlighted
JeffBusz
Occasional Visitor

Note: Crash event 0 was a PANIC !

I have had our RX2660 reboot a couple of time over the last few months.  We have some legacy application that needs to run on HP-US B.11.31.  After doing a crashinfo on the last crash, I am getting the following in the crashinfo.out file: for crash event 0:

Reason 0x1c: Data Key Miss Fault

Interrupt Instruction Pointer:
IIP = 0xdead31.0xe000000157771610, slot 1

Interrupt Instruction Bundle:

nsamod_rput+0x90(): (@ 0xe000000157771610)
+0x90 adds r14=20,r14
;;
st4 [r14]=r0,-4
nop.i 0x0
;;

Interrupt Faulting Address:
IFA = 0x1c73c031.0x14

Note: Crash event 0 was a PANIC !

Panic string : Fault when executing in kernel mode


Note: In the case of a PANIC, normally crash event 0 is the crash
event you should concentrate on. There may well be other secondary
panics (for example spinlock panics) that have happened as a
consequence of the original panic.

Getting trap information from trap marker at 0x1c412031.0x9fffffff5ffe7800

Trap information
================

Reason 0x1c: Data Key Miss Fault

Interrupt Instruction Pointer:
IIP = 0xdead31.0xe000000157751610, slot 1

Interrupt Instruction Bundle:

nsamod_rput+0x90(): (@ 0xe000000157751610)
+0x90 adds r14=20,r14
;;
st4 [r14]=r0,-4
nop.i 0x0
;;

Interrupt Faulting Address:
IFA = 0x16012031.0x14

Note: The trapping address has a low offset, and is probably a
null pointer de-reference


Stack Trace for Crash event 0
=============================


============== EVENT ============================
= Event #0 is CT_PANIC on CPU #6;
= p crash_event_t 0xe000000100547000
= p rpb_t 0xe000000101b8c830
= Process at 0xe0000001863b1780, pid 3929, "nsad"
============== EVENT ============================
RR0=0x16012031 RR1=0x05ff0031 RR2=0x02002031 RR3=0x02002031
RR4=0x1c412031 RR5=0x00ffff31 RR6=0x00ffff31 RR7=0x00dead31
BSP SP IP
0x9fffffff5ffea090 0x9fffffff5ffe77c0 0xe000000001f4d6c0 panic+0x410
0x9fffffff5ffea060 0x9fffffff5ffe77d0 0xe000000002174d60 bad_kern_reference+0xa0
0x9fffffff5ffe9f78 0x9fffffff5ffe77d0 0xe000000000859490 $cold_pfault+0x6c0
0x9fffffff5ffe9ed8 0x9fffffff5ffe77e0 0xe000000000d57500 vm_hndlr+0xaa0
0x9fffffff5ffe9eb0 0x9fffffff5ffe77f0 0xe000000001daa780 bubbleup+0x880
+------------- TRAP ----------------------------
| Data Key Miss Fault in KERNEL mode
| IIP=0xe000000157751610:1
| IFA=0x14
| p struct save_state 0x1c412031.0x9fffffff5ffe7800
+------------- TRAP ----------------------------
BSP SP IP
0x9fffffff5ffe9e50 0x9fffffff5ffe7a70 0xe000000157751611 nsamod_rput+0x91
BSP SP IP
str_util.c:337 __str_put_body___str_util.c__32768_0176__(inlined)
0x9fffffff5ffe9db8 0x9fffffff5ffe7a70 0xe000000000cea470 putnext+0x140
0x9fffffff5ffe9d60 0x9fffffff5ffe7a70 0xe000000000c59b70 tcp_rsrv_comm+0x2b0
0x9fffffff5ffe9ce8 0x9fffffff5ffe7a70 0xe000000000c937f0 tcp_rput_other+0x370
0x9fffffff5ffe9ca0 0x9fffffff5ffe7ac0 0xe000000000cdf4b0 tcp_rput+0x1610
str_synch.c:1662 csq_run(inlined)
0x9fffffff5ffe9c08 0x9fffffff5ffe7b00 0xe000000000cc5f90 csq_turnover_with_lock+0x120
str_util.c:340 __str_put_body___str_util.c__32768_0176__(inlined)
0x9fffffff5ffe9b68 0x9fffffff5ffe7b10 0xe000000000ca9f80 puthere+0x3f0
0x9fffffff5ffe9a30 0x9fffffff5ffe7b10 0xe000000000d32190 tcp_accept+0x1650
tcp.c:19201 tcp_wput_proto(inlined)
0x9fffffff5ffe9830 0x9fffffff5ffe7b20 0xe000000000cd9750 tcp_wput+0x160
str_util.c:337 __str_put_body___str_util.c__32768_0176__(inlined)
0x9fffffff5ffe9798 0x9fffffff5ffe7b20 0xe000000000cea470 putnext+0x140
BSP SP IP
0x9fffffff5ffe9730 0x9fffffff5ffe7b20 0xe000000157757360 nsalmod_wput+0x500
BSP SP IP
str_util.c:337 __str_put_body___str_util.c__32768_0176__(inlined)
0x9fffffff5ffe96a0 0x9fffffff5ffe7b20 0xe000000000cea470 putnext+0x140
0x9fffffff5ffe95e0 0x9fffffff5ffe7b20 0xe000000000ca73e0 str_sync_sthinsert_ioctl+0x3a0
str_scalls.c:3611 hpstreams_ioctl_int(inlined)
0x9fffffff5ffe9548 0x9fffffff5ffe7b20 0xe000000000dbb910 streams_ioctl+0x1b0
BSP SP IP
0x9fffffff5ffe9498 0x9fffffff5ffe7b50 0xe000000157755ab0 nsa_daemon+0x640
0x9fffffff5ffe9428 0x9fffffff5ffe7b80 0xe000000157756790 nsa_listen+0x3c0
BSP SP IP
0x9fffffff5ffe93d0 0x9fffffff5ffe7bd0 0xe000000000618620 $cold_net_nsa_check_status+0xb0
0x9fffffff5ffe9358 0x9fffffff5ffe7bd0 0xe000000000aab1d0 inet_stream_listen+0x1b0
uipc_socket.c:507 solisten(inlined)
0x9fffffff5ffe92f0 0x9fffffff5ffe7be0 0xe000000000a9f530 listen+0x1b0
0x9fffffff5ffe9218 0x9fffffff5ffe7be0 0xe000000000cfa9a0 syscall+0x560
------------------------------------------------------


------------------------------------------------------

Any ideas of what could be causing this?  Thank you in advance for taking a look.

1 REPLY 1
Patrick Wallek
Honored Contributor

Re: Note: Crash event 0 was a PANIC !

If you are using the NSA HTTP software, then that may be the issue.  Have a look at this thread, if you have access to it:

 

https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-c02621665&withFrame

 

The resolution was to install the nsaHTTP software version 11.31.01.03 from here https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=NSAHTTP