Error Message

Panic string:
mutex_enter: bad mutex, lp=6003ec3e4f8 owner=30008150180 thread=30008150180 

Panic stack:
unix:panicsys+0x48(0x10b2868, 0x2a1037ab2c8, 0x187bd40, 0x1, , , 0x44e2001605, , , , , , , , 0x10b2868, 0x2a1037ab2c8)
unix:vpanic_common+0x78(0x10b2868, 0x2a1037ab2c8, 0x0, 0x0, 0x0, 0x30007ae2000)
unix:panic+0x1c(0x10b2868, 0x1834390, 0x6003ec3e4f8, 0x30008150180, 0x30008150180, 0x0)
unix:mutex_enter(0x6003ec3e4f8) - frame recycled
vxdmp:dmp_flush_throttle_queue+0xc(0x6003ec3e340, 0x0, , , 0x8, 0x0)
vxdmp:dmp_service_throttle_queue() - frame recycled
vxdmp:dmp_start_failover+0x78(0x6003bd0d100, , 0x8, , 0x0, 0x6004c933250)
vxdmp:gen_update_cur_pri+0x90(, , , , 0x7600000eba, 0xffffffff)
vxdmp:dmp_update_cur_pri+0x30(, , 0x0, 0x300e3f20ac8, 0x30007ae2000, 0x1e8)
vxdmp:dmp_reconfig_update_cur_pri+0x4(, , 0x197fd98, 0x197fda0, 0x2a1037ab698, 0x200)
vxdmp:dmp_decipher_instructions+0x3d0(0x2a1037ab758, 0x3, 0x100003, 0x0, 0x197b8d8)
vxdmp:dmp_process_instruction_buffer+0x190(0x1220003ffff, 0x2f4154, 0x100003, 0x0, 0x197b8d8)
vxdmp:dmp_reconfigure_db+0x6c(0x1220003ffff?, 0x2f4154?, 0x100003, 0x0, 0x197b8d8)
vxdmp:gendmpioctl(0x1220003ffff, 0x444d5040, 0x2f4154, 0x100003, 0x60031c11558, 0x2a1037abadc) - frame recycled
vxdmp:dmpioctl+0x1c(, 0x444d5040, 0x2f4154, 0x100003, 0x60031c11558, 0x2a1037abadc)
specfs:spec_ioctl(0x30057439880, 0x444d5040, 0x2f4154, 0x100003, 0x60031c11558) - frame recycled
genunix:fop_ioctl+0x20(0x30057439880, 0x444d5040, 0x2f4154, 0x100003, , 0x2a1037abadc)
genunix:ioctl+0x184()
unix:syscall_trap32+0xcc()

System panics with bad mutex due to a known issue with VxDMP and Powerpath combination. This issue is tracked via Symantec etrack incidents e1084928 / e1078793.

This issue is tracked via e1084928 / e1078793 and is fixed in VxVM 5.0 MP1 RP3 (and above) and VxVM 5.0 MP3 (and above).

Applies To

This problem is only applicable if all of the following conditions are met:

- Solaris Operating System (8, 9 or 10)

- VxVM 5.0MP1RP2 (or below)

- EMC  PowerPath