panic on 20160105T144453Z

> fffff0cd8933a7e0::findstack -v
stack pointer for thread fffff0cd8933a7e0: fffff001ed4a28b0
  fffff001ed4a2920 param_preset()
  fffff001ed4a29b0 die+0xdf(e, fffff001ed4a2ad0, 40, 1d)
  fffff001ed4a2ac0 trap+0xe18(fffff001ed4a2ad0, 40, 1d)
  fffff001ed4a2ad0 0xfffffffffb8001d6()
  fffff001ed4a2c20 udp_do_open+0x68(fffff043a8545e28, 0, 0, fffff001ed4a2ccc)
  fffff001ed4a2c90 udp_create+0x69(2, 1, 0, fffff0431c47bbc8, fffff0431c47ba84, fffff001ed4a2ccc, ffffffff00000000, fffff043a8545e28)
  fffff001ed4a2d10 socket_init_common+0x1c0(fffff0431c47ba50, 0, 0, fffff043a8545e28)
  fffff001ed4a2d40 so_init+0x25(fffff0431c47ba50, 0, fffff043a8545e28, 0)
  fffff001ed4a2df0 socket_create+0xc2(2, 1, 0, 0, 0, 0, fffff00100000001, fffff043a8545e28, fffff001ed4a2e48)
  fffff001ed4a2eb0 so_socket+0x228(2, 1, 0, 0, 1)
  fffff001ed4a2f10 _sys_sysenter_post_swapgs+0x153()

>  ::panicinfo
             cpu               29
          thread fffff0cd8933a7e0
         message BAD TRAP: type=e (#pf Page fault) rp=fffff001ed4a2ad0 addr=40 occurred in module "ip" due to a NULL pointer dereference
             rdi fffff043a8545e28
             rsi                0
             rdx fffff0f5e7b2b900
             rcx fffff001ed4a2ccc
              r8 fffff0431c47ba84
              r9 fffff001ed4a2ccc
             rax                0
             rbx fffff043a8545e28
             rbp fffff001ed4a2c20
             r10                0
             r11                0
             r12                0
             r13 fffff0431b7b7940
             r14 fffff001ed4a2ccc
             r15                0
          fsbase                0
          gsbase fffff042eb04bac0
              ds               4b
              es               4b
              fs                0
              gs              1c3
          trapno                e
             err                0
             rip fffffffff7ab2af8
              cs               30
          rflags            10246
             rsp fffff001ed4a2bc0
              ss               38
          gdt_hi                0
          gdt_lo         c000ffff
          idt_hi                0
          idt_lo         f000ffff
             ldt                0
            task               70
             cr0         8005003b
             cr2               40
             cr3       202e421000
             cr4           1426f8
             
             
             
             
             
> fffff043a8545e28::print cred_t
{
    cr_ref = 0x61
    cr_uid = 0
    cr_gid = 0
    cr_ruid = 0
    cr_rgid = 0
    cr_suid = 0
    cr_sgid = 0
    cr_priv = {
        crprivs = [
            {
                pbits = [ 0x14810, 0x3820000, 0, 0 ]
            },
            {
                pbits = [ 0x14810, 0x3820000, 0, 0 ]
            },
            {
                pbits = [ 0x14810, 0x3820000, 0, 0 ]
            },
            {
                pbits = [ 0xe7f9e8fe, 0xfbdbb935, 0x98000000, 0 ]
            },
        ]
        crpriv_flags = 0
    }
    cr_projid = 0
    cr_zone = 0xfffff0f5e7b2b900
    cr_label = 0
    cr_klpd = 0
    cr_ksid = 0
    cr_grps = 0
}




> 0xfffff0f5e7b2b900::print zone_t
{
    zone_name = 0xfffff221a7b6f340 "8931d577-5a9d-443c-9a73-cd4059d3b056"
    zone_nodename = 0xfffff1ff27769280 "8931d577-5a9d-443c-9a73-cd4059d3b056"
    zone_domain = 0xfffff1fde60bae00 ""
    zone_hostid = 0xffffffff
    zone_lock = {
        _opaque = [ 0 ]
    }
    zone_linkage = {
        list_next = zone_active+0x10
        list_prev = 0xfffff04383024d68
        


After the hyp rebooted the zone that opeed the socket is in failed state, possibly a race condition when zone starting/stopping
[root@phy10-sw1-ash (ash) ~]# vmadm list | grep 8931d577-5a9d-443c-9a73-cd4059d3b056
8931d577-5a9d-443c-9a73-cd4059d3b056  OS    2048     failed            buildzone_ash_169