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

Reboot after panic: post_hndlr(): Unresolved kernel interruption

 
UJOSHI
Occasional Contributor

Reboot after panic: post_hndlr(): Unresolved kernel interruption

Hello Admins,

 

One of my HPUX 11.23 ( RX 7640 ) is behaving very strange.

From last 10 day its getting reboot everyday around same time ( 12:05 Noon )

 

1) Syslog showing nothing strange.

2) no cron scheduled that can cause this panic reboot at this particular time.

3) everytime crash dump is generated.

4) No major hardware event logs.

 

I have created crash.html with command 

./crashinfo -t -H -continue > crash.html

 

The buffer messages while panic reboot are below:

 

Calling function e0000000011884c0 for Shutdown State 8 type 0x2

Stored message buffer up to panic:
Found adjacent data tr. Growing size. 0x3007000 -> 0x7007000.
Pinned PDK malloc pool: base: 0xe000000100ff9000 size=114716K
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.

MFS is defined: base= 0xe000000100ff9000 size= 1272 KB


Unpinned PDK malloc pool: base: 0xe000000110000000 size=524288K
Multiple MCAs/INITs feature enabled via checksum invalidation method
WARNING: GIO: read_ioconfig_file(): /stand/ioconfig read error.
ioconfig = NULL
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
[Osxinit]: Allocated ots_timeout_lock [e00000010c5476c0]
255/1 rdsk_root

 

What does it mean?

 

/etc/shutdownlog- show the message "Reboot after panic: post_hndlr(): Unresolved kernel interruption"

 

kmeminfo for string 0xdead31 and virtual address is showing below O/P:

 

abcd:/root# ./kmeminfo-a-2 -verbose -virtual 0xdead31.0xe00000010001fc00
Loading symbols from /stand/vmunix
Kernel TEXT pages not requested in crashconf
Will use an artificial mapping from a.out TEXT pages
Loading symbols from /stand/current/mod/rng
Note: Consider P4_ELF_WARNING=2 to get more details
Note: No debug information for this module
Loading symbols from /stand/current/mod/dmpaa
Note: No debug information for this module
Loading symbols from /stand/current/mod/dmpaaa
Note: No debug information for this module
Loading symbols from /stand/current/mod/dmpap
Note: No debug information for this module
Loading symbols from /stand/current/mod/dmpapg
Note: No debug information for this module
Loading symbols from /stand/current/mod/dmpapf
Note: No debug information for this module
Loading symbols from /stand/current/mod/dmpjbod
Note: No debug information for this module
Loading symbols from /stand/current/mod/dmphpalua
Note: No debug information for this module
Loading symbols from /stand/current/mod/dmphdsalua
Note: No debug information for this module
Loading symbols from /stand/current/mod/fdd
tool: kmeminfo 5.19
unix: /stand/vmunix 11.23 64bit IA64 on "abcd"
core: /dev/kmem live
link: Sun Sep 23 05:54:57 METDST 2012
boot: Sat Oct 5 12:25:33 2013
time: Sat Oct 5 19:12:36 2013
nbpg: 4096 bytes


----------------------------------------------------------------------
Virtual Address information:


VA 0xdead31.0xe00000010001fc00 translates to PA 0x801fc00
Page table entry: tr_entry_t 0xe000000101165fa8
Access rights : 0x08 PTE_AR_KRW
Protection key: 0xbeef KERNEL/PUBLIC
Page size : 64MB
Large page details:
Addr : virtual physical
Start: 0xe000000100000000 0x08000000
End : 0xe000000104000000 0x0c000000
PA 0x801fc00 is classified as "PC_KSDATA" (not dumped):
Page classification: pgclass_t 0xe00000010187995f
Locality for PA 0x801fc00 is loc_t 1, loc index 0, loc type CLM.

VA belongs to the "monarch_rse" symbol:

 

Can anyone let me know what is causing the panic reboot everyday? Let me know for further any assistance.

 

Thanks,

Uday Joshi