Mixed vPars: 11.23/11.31

[Yarek]

Hello Masters,
I have 2 vPars on rx8640

vPar1: hpux 11.31
vPar1:/root# vparstatus -P
Current Virtual Partition Version: A.05.04
Monitor Version: A.05.04

vPar2: hpux 11.23
vPar2:/root# vparstatus -P
vparstatus: Warning: Command version is different from monitor version. Some fields may not be displayed.
Current Virtual Partition Version: A.04.06
Monitor Version: A.05.04

When I try to boot the whole nPar from disks belonging to vPar2, the following error occurs:

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= 0xe000000101bc8000 size= 27732 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
0xe000000001e73070
0xe000000001e74740
0xe000000001b775e0
0xe000000000b09a90
0xe000000001e8dfa0
0xe000000001d16e60
End of Stack Trace

linkstamp: Wed Jan 28 14:08:38 MET 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= 0xe000000101bc8000 size= 27732 KB
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.



panic: VPAR: Versioning check failed
Stack Trace:
IP Function Name
0xe000000001e73070
0xe000000001e74740
0xe000000001b775e0
0xe000000000b09a90
0xe000000001e8dfa0
0xe000000001d16e60
End of Stack Trace

linkstamp: Wed Jan 28 14:08:38 MET 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 (0xe000000100567fc0) 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 (0xe000000100548380) 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_005bc6f0 00000000_00000001 e0000001_00ba4771
4- 7 00000000_00000040 00000000_00000918 c0000000_00000000 00000000_00000000
8-11 00000000_00000000 00000000_00000000 ffffffff_ffffffff 00000000_00000000
12-15 e0000001_00567fc0 ffffffff_ffffffff 00000000_00000100 00000000_00000010
16-19 00000000_00000008 ffffffff_ffffffff 00000000_000ab56e 00000000_00000bff
20-23 00000000_00000000 0000002b_b60c4d1e e0000001_00ba4770 00000000_00000002
24-27 01c00000_0201748e 01c00000_0201748e 00000000_00000716 00000000_00007700
28-31 00000000_00000000 00000000_00000001 00000000_00000000 0000002b_b60c4d1e

br_0-3 e0000000_01146c60 00000703_fc467800 00000703_fc49a7a0 00000000_ffa72580
br_4-7 00000000_00000000 00000000_00000000 e7ffffff_075975a0 e7ffffff_0781c400

666 1 1 11110 0 0 00
pr bits = 321-----------------------------------------9--6--32109-7-5---10
pr value = e0000000_00093ea3

k0 e7ffffff_0f000000 rsc 00000000_00000010 fpsr 0009a04d_8a7c437f
k1 00000000_00000000 bsp e0000001_00548380 unat 00000000_00000000
k2 00000000_00000000 bspstore e0000001_00548220 lc 00000000_00000003
k3 00000000_00000000 bsp_base e0000001_002e0020
ppdp e0000001_00300000 dirty 00000000_00000160 csd 00000000_00000000
ktp 00000000_00000000 rnat 00000000_00000000 ssd 00000000_00000000
ksp 00000000_00000002 ccv 00000000_00000000
sv 00000000_00000000 pfs 0000002b_b60c4d1e ec 00

iip e0000000_0113ba70/1 ifs 80000000_00000205 [i]psr 00001210_0842201a
iipa e0000000_0113ba70 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_005b9ef8 e0000000_0096e3e0 00000000_00000308 e0000000_01c412f0
0040: 00000000_000a0f6d e0000001_005c20c4 e0000001_005b9e54 e0000001_00355858
0060: e0000001_00355800 e0000001_005b9f20 e0000001_00355858 e0000001_00b39750
0080: e0000001_00af7394 e0000001_03fbf300 00000000_00000004 e0000000_003cdb10
00a0: 00000000_00000001 e0000001_005ba2e0 e0000001_005ba2cc e0000001_03fbf310
00c0: ffffffff_ffffffff 00000000_00000001 00000000_00000690 e0000000_011472c0
00e0: 00000000_000afe2d 00000000_000007a0 e0000001_03fbf308 00000000_00000000
0100: e0000001_03fbf348 00000000_00000003 00000000_003fcf02 e0000001_005ba2e0
0120: e0000001_005ba2b8 e0000001_005ba2d0 e0000001_005c2108 e0000001_005b9e54
0140: e0000001_03fbf300 00000000_00000000 00000000_00000004
out23: ffffffff_fffffff0 e0000001_03fbf300 0000002b_b60c4d1e 0000002b_b60c4d1e
out27: e0000000_01146c00

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!



Any suggestion? Hyper Threading is OFF

regards
J.

[melvyn burnard]

so you ar erebooting to use the whole Npar? i.e. not start Vpars?
If so you must tell the IA firmware that this is so, use the vparenv command from the OS shell, the vparconfig command at the EFI shell prompt, or reboot npars at the MON> prompt

[Mounaam]

Hi,

what do you mean by "When I try to boot the whole nPar from disks belonging to vPar2..."?

- if you want to boot in nPar mode you have to play with vparenv(OS) or parconfig/vparconfig (EFI)

- if you want to load the vPar monitor from vPar2 boot disk, vPar1 will not boot.
Only vPar A.05.X monitor support a mixed HP-UX 11i v2/v3 vPars environment.

Regards.

[Yarek]

I want to load the vPar monitor from vPar2 boot disk.

vPar2:/root# vparstatus -P
vparstatus: Warning: Command version is different from monitor version. Some fields may not be displayed.
Current Virtual Partition Version: A.04.06
Monitor Version: A.05.04

So I suppose thar Monitor Version is A.05.04.
Did I mix something up?

[Duncan Edmonstone]

Yarek,

The output from "vparstatus -P" is telling you what version the *running* vpmon is, not what version the vpmon is in a given vPar.

The version of vpmon in a vPar will match the vPars version in that partition, so if vPar2 has 04.06 installed, then the version of the monitor in vPar2 will also be 04.06.

I'm not sure its supported to boot anything but a vpmon in a 05.03 partition when running mixed vPars. (at least it makes no sense to me).

HTH

Duncan

[Yarek]

Thank you!

regards
J.