System core dump showed the following:
void unix:panicsys+0x48((const char *)0x10c8620(unix:Drodata.rodata+0x1671), (va_list)0x2a100aed638(*unix(data):panicargs), (struct regs *)0x198f830(unix(data):panic_stack+0x3f60), (int)1, 0x1602, , , , , , , , 0x10c8620(unix:Drodata.rodata+0x1671), 0x2a100aed638(*unix(data):panicargs))
unix:vpanic_common+0x78(0x10c8620(unix:Drodata.rodata+0x1671), 0x2a100aed638(*unix(data):panicargs), 0x5f824, 0x2a100aed131, 0x2a100aed930, 0x9980001605)
-- switch to kernel thread's stack --
void unix:panic+0x1c((const char *)0x10c8620(unix:Drodata.rodata+0x1671), (void *)0x31, 0x2a100aed890, 0x3016c58e000, 0, 0x2a100aed950, ...)
int unix:die+0x9c((unsigned)0x31, (struct regs *)0x2a100aed890, (caddr_t)0x3016c58e000, (uint_t)0)
void unix:trap+0xa20((struct regs *)0x2a100aed890, (caddr_t)0x3016c58e000, (uint32_t), (uint32_t))
unix:ktl0+0x64()
-- trap data type: 0x31 (data access MMU miss) rp: 0x2a100aed890 --
addr: 0x3016c58e000
tstate: 0x9980001605 %cwp:5 %pstate:0x16 (IE|PRIV|PEF|TSO)
%asi:0x80 (ASI_P) %ccr:0x99 (IC|IN|XC|XN) %gl:0
pc: 0x7bf9fb1c vxdmp:dmp_process_stats+0x35c: lduw [%l3 + %l4], %g1
npc: 0x7bf9fb20 vxdmp:dmp_process_stats+0x360: sra %l5, 0x0, %o7
global: %g1 0
%g2 0 %g3 0
%g4 0x400 %g5 0x6048424a000
%g6 0x10 %g7 0x2a100aedc80
out: %o0 0x605caff4000 %o1 0
%o2 0x172c %o3 0x1a9c000
%o4 0 %o5 0x5cb
%sp 0x2a100aed131 %o7 0x400
loc: %l0 0x70325b58 %l1 0x20
%l2 0x605caff4000 %l3 0x1000
%l4 0x3016c58d000 %l5 0x401
%l6 0x31c %l7 0xc7
in: %i0 0xffffffff %i1 0xffffffff
%i2 0x1a9a690 %i3 0
%i4 0x1a9a678 %i5 0x1a9a698
%fp 0x2a100aed1e1 %i7 0x7bfaac10
void vxdmp:dmp_daemons_loop+0x160()
unix:thread_start+4()
-- end of kernel thread's stack --
The vxdmp driver attempted to access an invalid address resulting in trap and associated panic
Issue was a hit on e3909992 and addressed in VRTSvxvm-7.2.0.200