1847291 Members
2923 Online
110263 Solutions
New Discussion

Re: system panic

 
yulianto piyut
Valued Contributor

system panic

hi all,

we just restore OS using ignite server, after complete, system boot but system can't up with error:
System Panic:

linkstamp: Mon Jul 30 19:09:52 TST 2007
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: Data page fault

PC-Offset Stack Trace (read across, top of stack is 1st):
0x002086b8 0x0025dcd4 0x0025d198
0x00163788 0x00784bac 0x001ce404
0x003529c4 0x0025d650 0x00163724
0x00174cb4 0x00172e44
End Of Stack



*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

ERROR: Your system crashed before I/O and dump configuration was complete.
A crash dump cannot be taken under these circumstances without
special configuration. Contact your HP support representative.


many thanks for your valuable time to give me solutions!

thx,

-yut-
7 REPLIES 7
Aussan
Respected Contributor

Re: system panic

from the line datapage fault, it indicates a software issue and not hardware,
you might have to reboot your system and do a TOC to create a crashdump, (i'm not sure it will work if it's not hung anymore)

if you call HP they will analyze the crashdump for you
The tongue weighs practically nothing, but so few people can hold it
evilmike
Advisor

Re: system panic

Can you boot to either single-user mode or logical volume maintenance mode?

Did you perform an interactive restore or an automated restore?

There was probably a problem with the creation of the root, boot, or swap areas. If "vg00" is mirrored to an additional boot disk, that disk must be present upon boot if that disk is used for swap or dump.

yulianto piyut
Valued Contributor

Re: system panic

we backup my system to ignite server (make_net_recovery -s ignite_server -x inc_entire=vg00) and the backup is successfully with no warning. than we restored this system to another server, restore archive is success but when system try to update the kernel from /stand/system/vmunix_test to /stand/vmunix is failed. i run kmupdate and reboot the server. system is panic when try to booting up.
skt_skt
Honored Contributor

Re: system panic

u mean the system came up properly after the ignite restoration. But after the kernel parameter is is NOT.is it?

If yes what is changed?
Dennis Handly
Acclaimed Contributor

Re: system panic

>Aussan: you might have to reboot your system and do a TOC to create a crashdump

I doubt this will help. If it is too early, you can't take a dump without that "special configuration".
Sameer_Nirmal
Honored Contributor

Re: system panic

I suspect the kernel didn't get rebuild for the server you are trying to ignite. Since the kernel rebuild step was taken by IG-UX, it is clear that both server platforms are different. The kernel with which you booted the system is not built for the system and hence it's paniced.

Can you post details like OS version, server models etc you are dealing with?

Did you note the error message given while kernel was being built ?
yulianto piyut
Valued Contributor

Re: system panic

sorry,

we don't nore error message when kernel built. the source system is hpux 11.11 dec 2003, running on Superdome with PA 8700, the client server that will be used to restore is superdome with PA 8900. I think, system panic beacause of different CPU type in both server. for PA 8900, bundle OS minimal is dec 2004.

thx for all