Operating System - HP-UX
1753549 Members
5631 Online
108795 Solutions
New Discussion юеВ

Re: vpar crash on upgrading 11i v3

 
SOLVED
Go to solution
Vikas Thorat
Advisor

vpar crash on upgrading 11i v3

Hi Guru's,

I am upgrading my 11i v2 to v3 on itanium superdome.

I am having virtual partion A.04.05
I used "update-ux -s /cdrom" command to upgrade it.

My upgradation was almost completed and then suddenly its rebooted. After reboot I got below error message and from that point of time I am not able to get the OS.

The error I m getting after reboot is :

===============================================
EFI Boot Manager ver 2.00 [14.62] Loading device drivers
EFI Boot Manager ver 2.00 [14.62] Please select a boot option
OS might use only the primary console set via boot manager or conconfig command

8/0/13/1/0/4/1.0.0.0.0.0.0
EFI Shell [Built*in]
Boot Option Maintenance Menu


Use ^ and v to change option(s). Use Enter to select an option
Use > and < to view long descriptions
Hot Key: 'S' or 's' to start the EFI Shell

Selected boot option: 8/0/13/1/0/4/1.0.0.0.0.0.0

Loading.: 8/0/13/1/0/4/1.0.0.0.0.0.0

Executing Image: "\EFI\HPUX\HPUX.EFI"
Optional Data : "\EFI\HPUX\HPUX.EFI boot /stand/vmunix -lq"

Starting: 8/0/13/1/0/4/1.0.0.0.0.0.0


(C) Copyright 1999-2008 Hewlett-Packard Development Company, L.P.
All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.036

> System Memory = 16333 MB
loading section 0
...................................................................................... (complete)
loading section 1
............. (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
.....x
loading MFSFILES directory (/stand/bootfs) to MFS
.....................xxxxxxxxx.
Launching /stand/vmunix
SIZE: Text:43729K + Data:6347K + BSS:25445K = Total:75522K
Console is on virtual console - via PCDP
Booting kernel...

This version of the vPar monitor (2.0) does not
support all the capabilities required by this kernel

panic : Failed to halt all processors

Stored message buffer up to system crash:

MFS is defined: base= 0xe000000101f0f000 size= 28496 KB
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.



Message buffer contents after system crash:

panic: VPAR: Versioning check failed
Stack Trace:
IP Function Name
0xe0000000028faa10
0xe0000000028fc0e0
0xe000000001ef7e80
0xe000000000b232f0
0xe000000002915a60
0xe000000002096560
End of Stack Trace

linkstamp: Tue Feb 24 11:57:00 IST 2009
_release_version: @(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf
shutdown : Failed to halt all processors

Stored message buffer up to system crash:

MFS is defined: base= 0xe000000101f0f000 size= 28496 KB
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.



panic: VPAR: Versioning check failed
Stack Trace:
IP Function Name
0xe0000000028faa10
0xe0000000028fc0e0
0xe000000001ef7e80
0xe000000000b232f0
0xe000000002915a60
0xe000000002096560
End of Stack Trace

linkstamp: Tue Feb 24 11:57:00 IST 2009
_release_version: @(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf
shutdown : Failed to halt all processors
Bad News: pr == 0x184802c11186003d
Bad News: Interrrupted sp was expected to be on the ICS. Instead,
Bad News: sp (0xe0000001005c7fc0) was > ppdp (ar.k4 == 0xe000000100300000).
Bad News: Cannot use the Kernel Stack when interrupted on the ICS.
Bad News: Fault/trap with interrupts disabled and we cared.
Bad News: ar.bsp (0xe0000001005a8380) is greater than the
Bad News: ICS backing store limit of 0xe0000001002ef000.
Bad News: Predicate set: 0x184802c11186003d.

******************************************************************************
******************************************************************************

reg_dump(): Displaying register values (in hex) from the save state at
ssp e0000001_002ffc00 return_status/reason/flags 0000/0008/00000001

Interruption type: Data TLB Fault

0- 3 00000000_00000000 e0000001_0062d818 00000000_00000001 e0000001_00dd0081
4- 7 00000000_00000268 00000000_00000918 c0000000_00000000 00000000_00000005
8-11 00000000_00000000 00000000_00000000 ffffffff_ffffffff 00000000_00000000
12-15 e0000001_005c7fc0 ffffffff_ffffffff 00000000_00000100 00000000_00000010
16-19 00000000_00000008 ffffffff_ffffffff 04000000_000ab54e 00000000_00000bff
20-23 00000000_00000000 0000002c_b8104d1e e0000001_00dd0080 00000000_00000005
24-27 01c00000_0201ba01 01c00000_0201ba01 00000000_00000716 00000000_00007700
28-31 00000000_00000000 00000000_00000001 00000000_00000000 0000002c_b8104d1e

br_0-3 e0000000_011727a0 00000b07_fc467800 00000b07_fc49a7a0 00000000_00000000
br_4-7 00000000_00000000 00000000_00000000 e7ffffff_075975a0 e7ffffff_0781c400

66 5 1 1 11110 0 00
pr bits = 32---8--------------------------------------9--6--32109-7-----10
pr value = c4000000_00093e83

k0 e7ffffff_17000000 rsc 00000000_00000010 fpsr 0009a04d_8a7c437f
k1 00000000_00002a26 bsp e0000001_005a8380 unat 00000000_00000000
k2 00000000_00000000 bspstore e0000001_005a8220 lc 00000000_00000002
k3 00000000_00000000 bsp_base e0000001_002e0020
ppdp e0000001_00300000 dirty 00000000_00000160 csd 00000000_00000000
ktp e0000001_9438d040 rnat 00000000_00000000 ssd 00000000_00000000
ksp 00000000_00000002 ccv 00000000_00000000
sv e0000001_08884000 pfs 0000002c_b8104d1e ec 00

iip e0000000_011675b0/1 ifs 80000000_00000205 [i]psr 00001210_0842201a
iipa e0000000_011675b0 tpr 00000000_00000010 isr 00000a04_00000000

ibe sddiimic rtldsdpsddd p i mmaub
andrisdadtcspl tbpbiipphlt kic hlcpe
psr bits = ------------------01001000010000----10000100001-001-------01101-

e snirsn
deioirsparwx < code >
isr bits = --------------------101000000100--------000000000000000000000000

arg0=ffffffff_fffffff0 (cr.ifa)
arg1=00000000_00000000 (unknown)

Dirty Registers:
0020: e0000001_0062afb8 e0000000_009d81a0 00000000_00000308 e0000000_01fc1210
0040: 04000000_000a0f4d e0000001_00633704 e0000001_0062af14 e0000001_003ba5d8
0060: e0000001_003ba580 e0000001_0062afe0 e0000001_003ba5d8 e0000001_00bb8010
0080: e0000001_00b68334 ffffffff_ffffffff e0000001_048f7280 e0000001_0062b358
00a0: e0000000_00472df0 00000000_00000001 e0000001_0062b360 e0000001_0062b34c
00c0: e0000001_048f7290 00000000_00000001 00000000_00000690 e0000000_01172e00
00e0: 04000000_000afe0d 00000000_000007a0 e0000001_048f7288 00000000_00000000
0100: e0000001_048f72b8 00000000_00000002 00000000_003fcde4 e0000001_0062b360
0120: e0000001_0062b338 e0000001_0062b350 e0000001_00633748 e0000001_0062af14
0140: e0000001_048f7280 00000000_00000000 00000000_00000003
out23: ffffffff_fffffff0 e0000001_048f7280 0000002c_b8104d1e 0000002c_b8104d1e
out27: e0000000_01172740

Message buffer contents after system crash:

double panic: Bad News!


Stored message buffer up to system crash:

Message buffer contents after system crash:

double panic: Bad News!
==============================================

Also, I m not able to get EFI shell prompt too. May be the "Autoboot Delay" is set to 0 sec. Not able to reach to EFI Boot Manager too.

How should I change this delay parameter in this case?

Appreciate your help and suggestions. Right suggestions will be awarded asap.

regards,

Vikas Thorat
Success is not a Permanent & Failure is not Final! So,Never Stop Working after Success & Never Stop Trying after Failure!
3 REPLIES 3
Torsten.
Acclaimed Contributor

Re: vpar crash on upgrading 11i v3

You need to stop all vpars, switch (reboot) to npars mode, upgrade this os instance, upgrade vpars software, repeat this on all vpars and finally then switch back to vpars mode and boot the vpmon.

Did you do this?

Not possible to upgrade (like you did) while other vpars are running.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor
Solution

Re: vpar crash on upgrading 11i v3

See this link for more:

http://docs.hp.com/en/T1335-90098/ch04s05.html

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vikas Thorat
Advisor

Re: vpar crash on upgrading 11i v3

Hi Torsten,

Thank you very much for exact solution.

If possible I will put the complete steps by step document after completeing this activity with problems I faced.

Thanks again.

regards,

Vikas Thorat
Success is not a Permanent & Failure is not Final! So,Never Stop Working after Success & Never Stop Trying after Failure!