vpar panic

linda wang_1 — Thu, 22 Mar 2007 13:20:46 GMT

I created a vpar inside a superdome IA npar. It failed to boot the vpar.

Here is part of the dump file:
ptest53 could not take ownership of module at 0/250/2 because it is not assignable
MON> Launching all vPars with autoboot attribute set
[MON] Booting ptest53...
Bad News: Fault/trap with interrupts disabled and we cared.

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

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

Interruption type: Data Page Not Present Fault

0- 3 00000000_00000000 60000001_02c0d138 00000000_0000050c 00000000_00002018
4- 7 00000000_00000061 00000000_00000897 60000001_00008000 00000000_00000000
8-11 00000000_00000000 ffffffff_ffffae08 00000000_00005310 60000001_03c14fe8
12-15 60000001_0001ff90 60000001_02c53d58 ffffffff_ffffadf0 00000000_00002998
16-19 00000000_00002990 00000000_0000001b 00000000_000001d9 60000001_03c17970
20-23 60000001_03c14fd8 00000000_00000068 00000000_00000000 00000000_00003fff
24-27 00000000_0000002f 60000001_0001fe11 60000001_0001fe0b 00000000_00000077
28-31 80000ffc_500554a0 00000000_00000000 60000001_0001fdc0 00000000_00000b1b

br_0-3 60000000_000eb5d0 00000701_fc78f5a0 00000000_ffa555a0 00000000_ffa85180
br_4-7 00000000_00000000 00000000_00000000 60000000_00069f80 00000701_fc81e800

11 1 1 10 00 00
pr bits = ---------------------------------------------87-5--2-09--65---10
pr value = 00000000_00069663

k0 00000000_00000000 rsc 00000000_00000010 fpsr 00000000_8864433f
k1 00000000_00000000 bsp 60000001_000083e0 unat 00000000_00000000
k2 00000000_00000000 bspstore 60000001_000082b0 lc 00000000_000001e5
k3 00000000_00000000 bsp_base 00000000_00000000
k4 00000000_00000000 dirty 00000000_00000130 csd 00000000_00000000
k5 00000000_00000000 rnat 00000000_00000000 ssd 00000000_00000000
k6 00000000_00000000 ccv 00000000_00000000
k7 00000000_00000000 pfs 00000000_00000b1b ec 00

iip 60000000_000eb840/0 ifs 80000000_00000183 [i]psr 00001010_0802201a
iipa 60000000_000eb830 tpr 00000000_00000000 isr 00000804_00000000

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

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

arg0=60000000_000eb840 (cr.iip or cr.ifa)
arg1=00000000_00000000 (unknown)

Dirty Registers:
82b0: 00000000_00000000 00000000_00000000 00000000_00000b9c 60000000_000e7da0
82d0: 00000000_000694e1 00000000_000694e1 00000000_00000100 60000001_02fd99f0
82f0: 60000001_02c0d1f8 ffffffff_ffffffff 00000000_00000002 60000001_02fd99d8
8310: 60000001_02fd9958 00000000_00000000 00000000_00000692 60000000_000e1310
8330: 00000000_00000000 00000000_000696a3 60000001_0001ffa0 60000001_00816e1c
8350: 00000000_00000728 60000001_0080084c 9ffffffe_ff7ffed4 00000000_00000000
8370: 00000000_00000001 60000001_0080012c 60000000_000eb2a0 60000001_03e873f0
8390: 60000001_00800138 60000001_00800108 60000001_00800128 00000000_00000000
83b0: 60000001_00800130 60000001_03e85bd8 60000001_03e869e0
out20: 00000000_00000000 00000000_00000000 00000000_0000040b

[MON]
panic: Bad News!

[MON]
waiting for 1 cpus

+++++++++++++++++++++++++++++++++++++++++++++++++++
panic: Bad News!

+++++++++++++++++++++++++++++++++++++++++++++++++++

Event log:

INFO:CPU0:MON:vPar Monitor version 1.0 started
INFO:CPU0:MON:Version string: @(#) $Revision: vmunix: jazz @ 20070226.17:11:06PST; jmkvw -proj vpar -RW bhaski_ic61_depot cup2_vpar_i380_dev(CUP2_VPAR_I380_DEV_BL_2007-FEB-26-0) ; FLAVOR=perf
INFO:CPU0:MON:gen_proc_init: root_cell = 0
DEBUG:CPU0:MON:Completed IPMI initialization
INFO:CPU0:MON:MFS is defined: base= 0x6000000103e8f000 size= 28 KB
INFO:CPU31:MON:CPU 0 in NO VP changed state from MPMON to MPRENDEZ for MPRENDEZ_FW
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #26 path \_SB_.N002.S032.IOC0.L002.S2F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #27 path \_SB_.N002.S032.IOC0.L004.S3F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #28 path \_SB_.N002.S032.IOC0.L005.S4F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #29 path \_SB_.N002.S032.IOC0.L006.S5F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #34 path \_SB_.N002.S032.IOC1.L013.S7F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #35 path \_SB_.N002.S032.IOC1.L014.S6F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #38 path \_SB_.N002.S032.IOC0.L002.S2F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #39 path \_SB_.N002.S032.IOC0.L004.S3F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #40 path \_SB_.N002.S032.IOC0.L005.S4F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #41 path \_SB_.N002.S032.IOC0.L006.S5F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #46 path \_SB_.N002.S032.IOC1.L013.S7F0
ERROR:CPU0:MON:set_mod_to_acpi_reg_bits: Could not obtain the LBA native module for #47 path \_SB_.N002.S032.IOC1.L014.S6F0
INFO:CPU0:MON:mfs_get_header: successful - hdr size 28672
INFO:CPU0:MON:mfs_open: successful
INFO:CPU0:MON:mfs_get_header: successful - hdr size 28672
INFO:CPU0:MON:open: file /stand/vpdb size= 8272 bytes
WARNING:CPU0:MON:ptest53 could not take ownership of module at 0/250/2 because it is not assignable
INFO:CPU0:MON:VPAR STATE CHANGE ptest53 from VPS_DOWN to VPS_LOAD for VPS_LOAD_PREP_LOAD
INFO:CPU0:MON:Partition ptest53 monarch set to 0/120
INFO:CPU0:MON:[18:38:10 3/21/2007 GMT] CPU 0/120 bound to partition ptest53
INFO:CPU0:MON:[18:38:10 3/21/2007 GMT] CPU 0/121 bound to partition ptest53
INFO:CPU2:MON:CPU 0/122 in NO VP changed state from MPRENDEZ to MPMON for MPMON_BOOT_RENDEZ
INFO:CPU0:MON:Initialising pri shmem for vpar ptest53
INFO:CPU0:MON:alloc_vpar_private_shmem: r/w shmem=0x6000000100c00000 for ptest53
INFO:CPU0:MON:alloc_vpar_private_shmem: r/o shmem=0x6000000100c40000 for ptest53
FATAL:CPU0:MON:panic: Bad News!

FATAL:CPU0:MON:[18:38:11 3/21/2007 GMT] Crash event detected: panic
INFO:CPU0:MON:VPAR "ptest53" state: loading
FATAL:CPU0:MON:Panic detected by CPU 0
INFO:CPU0:MON:CPU 0/120 in ptest53 changed state from MPMON to MPCRASH for MPCRASH_CPT_UPDATE
INFO:CPU0:MON:waiting for 1 cpus
FATAL:CPU2:MON:Unexpected INIT detected by CPU 2
INFO:CPU2:MON:CPU 0/122 in NO VP changed state from MPMON to MPCRASH for MPCRASH_CPT_UPDATE
FATAL:CPU0:MON:IP Value Stack Trace [Image = (;)/stand/vpmon]:
FATAL:CPU0:MON: 0x60000000000EB840
FATAL:CPU0:MON:End of Stack

******** PANIC -- Processor 0: LID 0x0000000000000000 ********
nat value = 0000000000000000
nat bits = ----------------------------------------------------------------

Any suggestion, is it a hardware or software/config issue?

Thanks

Re: vpar panic

Steven E. Protter — Thu, 22 Mar 2007 14:29:12 GMT

Shalom,

Looks like no cpu is assigned to this vpar, or the cpu it thinks it is assigned is unavailable, possibly failed.

Have you gone through the isntall guide carefully? Has this vpar ever worked or is this a brand new one?

Knowing the OS of the host and the guest would also be helpful along with the version of vpar software (swlist -l product | grep -i vpar)

SEP

topic Re: vpar panic in Operating System - HP-UX

vpar panic

Re: vpar panic