ACSLS - ACSLS Server Panics During Reboot
(Doc ID 1500638.1)
Last updated on JULY 11, 2022
Applies to:
Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) High Availability - Version 3.0 Sun Cluster to 8.0 Sun Cluster [Release 3.0 to 8.0]Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 7.3 to 8.5.1 [Release 7.0 to 8.0]
Information in this document applies to any platform.
Symptoms
The ACSLS server panics during the reboot process at the time when ACSLS services are starting up.
Messages at bootup time:
Rebooting with command: boot
Boot device: disk:a File and args:
SunOS Release 5.10 Version Generic_147440-19 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Hostname: server1
/kernel/drv/sparcv9/stmf symbol zone_get_hostid multiply defined
NOTICE: smc_lu module: built Aug 30 2010 14:32:37 - _init()
NOTICE: smc_init(): sizeof scstPacket_t 0x368
NIS domain name is domain1
server1 console login: Oct 6 15:14:57 server1 svc.startd[11]: application/slm/rmi-registry:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Oct 6 15:15:10 server1 su: 'su root' succeeded for scos on /dev/pts/1
Oct 6 15:16:27 server1 svc.startd[11]: system/webconsole:console failed: transitioned to maintenance (see 'svcs -xv' for details)
Oct 6 15:17:49 server1 svc.startd[11]: application/slm/acsls:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
panic: failed to stop cpu4
panic: failed to stop cpu5
panic: failed to stop cpu6
panic: failed to stop cpu7
panic: failed to stop cpu12
scat "analyze" output:
==============================
SolarisCAT(vmcore.6/10V)> analyze
core file: /var/crash/server1/vmcore.6
user: Super-User (root:0)
release: 5.10 (64-bit)
version: Generic_147440-19
machine: sun4v
node name: server1
domain: domain1
hw_provider: Oracle Corporation
system type: SUNW,SPARC-Enterprise-T2000 (UltraSPARC-T1)
hostid: 852770da
dump_conflags: 0x10000 (DUMP_KERNEL) on /dev/zvol/dsk/rpool/dump(16G)
time of crash: Sat Oct 6 15:44:25 EDT 2012
age of system: 30 minutes 49.65 seconds
panic CPU: 18 (32 CPUs, 31.9G memory)
panic string: xt_sync: timeout
==== panic thread: 0x2a102397c80 ==== CPU: 18 ====
==== panic kernel thread: 0x2a102397c80 PID: 0 on CPU: 18 affinity CPU: 18 ====
cmd: sched
t_procp: 0x18a68c0(proc_sched)
p_as: 0x18a8558(kas)
zone: global
t_stk: 0x2a102397a90 sp: 0x1912a71 t_stkbase: 0x2a102392000
t_pri: 99(SYS)ctf_field_read(thread.t_lbolt) failed: field "t_lbolt" not found in structure "kthread_t"
pctcpu: 0.000000
t_lwp: 0x0 psrset: 0 last CPU: 18
idle: 132 ticks (1.32 seconds)
start: Sat Oct 6 15:13:53 2012
age: 1832 seconds (30 minutes 32 seconds)
tstate: TS_ONPROC - thread is being run on a processor
tflg: T_TALLOCSTK - thread structure allocated from stk
T_PANIC - thread initiated a system panic
tpflg: none set
tsched: TS_LOAD - thread is in memory
TS_DONT_SWAP - thread/LWP should not be swapped
TS_SIGNALLED - thread was awakened by cv_signal()
pflag: SSYS - system resident process
pc: unix:panicsys+0x48: call unix:setjmp
startpc: genunix:taskq_thread+0x0: save %sp, -0xe0, %sp
unix:panicsys+0x48(0x10bd3f8, 0x2a102396fd0, 0x1913440, 0x1, , , 0x44e2001601, , , , , , , , 0x10bd3f8, 0x2a102396fd0)
unix:vpanic_common+0x78(0x10bd3f8, 0x2a102396fd0, 0x2a102397058, 0x2183b76cda8, 0x0, 0x1913cf0)
genunix:cmn_err+0x98(0x3, 0x10bd3f8, 0x0, 0x0, 0x40, 0x0)
unix:xt_sync+0x370(0x2a102397370)
unix:hat_unload_callback+0x7d4(0x30002cb7b40?, 0x3002e7ca000?, , 0x4)
unix:hat_unload(0x30002cb7b40, 0x3002e78a000, 0x40000, 0x4, 0x18a8400, 0x41fff) - frame recycled
unix:segkmem_free_vn+0x58(0x19742e0, 0x3002e78a000, 0x40000, 0x198d588)
genunix:vmem_hash_rescale(0x300029fc000) - frame recycled
genunix:vmem_update+0x34(0x0)
genunix:callout_list_expire+0x5c(0x60033bb07c0, 0x6004863c340)
genunix:callout_expire+0x1c(0x60033bb07c0)
genunix:callout_execute+0xc(0x60033bb07c0, 0x6003934f4a0, 0x10e584c, 0x0, 0x8978600, 0x0)
genunix:taskq_thread+0x3b8(0x6003925e678, 0x0)
unix:thread_start+0x4()
-- end of kernel thread's stack --
SolarisCAT(vmcore.6/10V)>
Changes
Applied the latest Oracle Critical Patch Update
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |