Error Message

 System messages file will have below stack when system panics

unix: [ID 836849 kern.notice]  ^Mpanic[cpu514]/thread=2a10032fc80:
unix: [ID 799565 kern.notice] BAD TRAP: type=34 rp=2a10032f5b0 addr=deadbeefdeadbeef mmu_fsr=0
unix: [ID 100000 kern.notice]
unix: [ID 839527 kern.notice] sched:
unix: [ID 123557 kern.notice] alignment error:
unix: [ID 381800 kern.notice] addr=0xdeadbeefdeadbeef
unix: [ID 101969 kern.notice] pid=0, pc=0x104c064, sp=0x2a10032ee51, tstate=0x4480001601, context=0x0
unix: [ID 743441 kern.notice] g1-g7: c, 9f8, 70422768, 70422000, 0, e68, 2a10032fc80
unix: [ID 100000 kern.notice]
genunix: [ID 723222 kern.notice] 000002a10032f2d0 unix:die+9c (34, 2a10032f5b0, deadbeefdeadbeef, 0, 2a10032f390, c1e00000)
genunix: [ID 179002 kern.notice]   %l0-3: 00000000c0800000 0000000000000034 0000000000000000 00000000019f0cb8
  %l4-7: 0000000000000000 0000000000000000 00000000000001c0 00000000010ad000
genunix: [ID 723222 kern.notice] 000002a10032f3b0 unix:trap+6d4 (2a10032f5b0, 10000, 0, 80000d, 0, 2a10032fc80)
genunix: [ID 179002 kern.notice]   %l0-3: 0000000000000000 00000000018cdc40 0000000000000034 0000000000000000
  %l4-7: 0000000000000000 0000000000044e0c 0000000000044e0b 0000000000010200
genunix: [ID 723222 kern.notice] 000002a10032f500 unix:ktl0+48 (deadbeefdeadbeef, 2a10032fc80, 70400, 0, 1a07000, 1a07)
genunix: [ID 179002 kern.notice]   %l0-3: 0000000000000002 0000000000001400 0000004480001601 000000000101c6cc
  %l4-7: 000003004a896000 00000000000065c0 0000000000000000 000002a10032f5b0
genunix: [ID 723222 kern.notice] 000002a10032f650 genunix:psignal+4 (3009f9ef440, 16, 2a10032f7a0, 19f1d60, 2, 2a10032f86c)
genunix: [ID 179002 kern.notice]   %l0-3: 0000000000001800 000000000007040e 0000000000070400 00000000564f4c00
  %l4-7: 0000000000000064 0000000001836000 0000000000001836 0000000000001800
genunix: [ID 723222 kern.notice] 000002a10032f700 vxdmp:dmp_signal_event_daemon+40 (19f1cb8, 19ef000, 19ef, 1800, 19f1000, 19f1)
genunix: [ID 179002 kern.notice]   %l0-3: 00000000019f1000 00000000000019f1 000000007c1e6890 000000007c1e6000
  %l4-7: 00000000019ef000 00000000000019ef 0000000000001800 000003009f9ef440
genunix: [ID 723222 kern.notice] 000002a10032f7b0 vxdmp:dmp_signal_vold+32c (0, 202, 19f0608, 19afe70, 1800, 0)
genunix: [ID 179002 kern.notice]   %l0-3: 00000000000019af 000000000000001e 0000000000000000 00000000019ef000
  %l4-7: 00000000000019ef 0000000000001800 00000000000019f0 000000007ffffc00
genunix: [ID 723222 kern.notice] 000002a10032f870 vxdmp:dmp_throttle_paths+424 (1583b045e, 3004d741000, 1b, 2000000a, 19f1d00, 2)
genunix: [ID 179002 kern.notice]   %l0-3: 000000000000001b 0000060040dbfa00 00000000019f09e8 000000000000001b
  %l4-7: 00000000000f423c 000000000000001b 00000600405b2eb0 00000000000000b6
genunix: [ID 723222 kern.notice] 000002a10032f930 vxdmp:dmp_process_stats+278 (1800, 19f09cc, 0, 19f0e70, 1583b045a, a81)
genunix: [ID 179002 kern.notice]   %l0-3: 0000000000001800 00000000019f0998 0000000000000002 0000000000001800
  %l4-7: 00000000019f1000 00000000000019f1 0000000000001800 00000000000019f1
genunix: [ID 723222 kern.notice] 000002a10032f9e0 vxdmp:dmp_daemons_loop+160 (8, 13d1d94, 19f0ca4, 19f1ad8, 19f0cc8, 19f0cc0)
genunix: [ID 179002 kern.notice]   %l0-3: 00000000019f0cd8 00000000019f0cb0 00000000019f0cd0 00000000019f0cb8
  %l4-7: 0000000000000000 0000000000000000 00000000000001c0 0000000000000001

Also the core file will have panic stack as below

mutex_enter+4(3009f9ef440, 16, 2a10032f7a0, 19f1d60, 2, 2a10032f86c)
dmp_signal_event_daemon+0x40(19f1cb8, 19ef000, 19ef, 1800, 19f1000, 19f1)
dmp_signal_vold+0x32c(0, 202, 19f0608, 19afe70, 1800, 0)
dmp_throttle_paths+0x424(1583b045e, 3004d741000, 1b, 2000000a, 19f1d00, 2)
dmp_process_stats+0x278(1800, 19f09cc, 0, 19f0e70, 1583b045a, a81)
dmp_daemons_loop+0x160(8, 13d1d94, 19f0ca4, 19f1ad8, 19f0cc8, 19f0cc0)
thread_start+4(0, 0, 0, 0, 0, 0)

System panic is caused by dmp_signal_event_daemon() function calling psignal() with incorrect pointer for vxesd process.

VxVM gets the incorrect pointer by calling drv_getparm() function, which is replaced with ddi_get_pid() function in newer Solaris Operating Systems.

This issue is addressed via incident e2101093 in Veritas.

VxVM code is modified to enable newer Solaris OS functions, ddi_get_lbolt() ddi_get_time() and ddi_get_pid(), in getting process details.

This issue is fixed in below patches.

sfha-sol_sparc-5.1SP1RP4,  https://sort.Veritas.com/patch/detail/7894

sfha-sol_sparc-5.1SP1PR3RP4, https://sort.Veritas.com/patch/detail/7895

sfha-sol10_x64-5.1SP1RP4, https://sort.Veritas.com/patch/detail/7896

sfha-sol10_x64-5.1SP1PR3RP4, https://sort.Veritas.com/patch/detail/7897

sfha-sol10_sparc-6.0.5, https://sort.Veritas.com/patch/detail/8512

sfha-sol11_sparc-6.0.5, https://sort.Veritas.com/patch/detail/8513

sfha-sol10_x64-6.0.5, https://sort.Veritas.com/patch/detail/8514

sfha-sol11_x64-6.0.5, https://sort.Veritas.com/patch/detail/8515

Veritas suggests customers to upgrade to above or latest patches to address this issue.

Applies To

Solaris systems running Storage foundation below 5.1SP1RP4 and 6.0.5.