[OmniOS-discuss] OmniOS r151016 crashed and rebootet

[Stephan Budach]

Hi Dan,

yesterday, I had been struck by the very same fault, at least this is my 
guess, which caused my system to reboot. This actually happened shortly 
after I performed some network/MTU reconfiguration on my ixgbe NICs and 
the assiciated aggregation. I have compared the two fmdump instances and 
they nearly look like twins:

root at nfsvmpool08:/var/crash/unknown# fmdump -Vp -u 
d02238fa-4892-6c21-cd77-e5e70d20e9b1
TIME                           UUID SUNW-MSG-ID
Jan 31 2016 17:20:33.177419000 d02238fa-4892-6c21-cd77-e5e70d20e9b1 
SUNOS-8000-KL

   TIME                 CLASS                                 ENA
   Jan 31 17:20:33.1634 ireport.os.sunos.panic.dump_available 
0x0000000000000000
   Jan 31 17:17:36.1766 ireport.os.sunos.panic.dump_pending_on_device 
0x0000000000000000

nvlist version: 0
         version = 0x0
         class = list.suspect
         uuid = d02238fa-4892-6c21-cd77-e5e70d20e9b1
         code = SUNOS-8000-KL
         diag-time = 1454257233 164636
         de = fmd:///module/software-diagnosis
         fault-list-sz = 0x1
         fault-list = (array of embedded nvlists)
         (start fault-list[0])
         nvlist version: 0
                 version = 0x0
                 class = defect.sunos.kernel.panic
                 certainty = 0x64
                 asru = 
sw:///:path=/var/crash/unknown/.d02238fa-4892-6c21-cd77-e5e70d20e9b1
                 resource = 
sw:///:path=/var/crash/unknown/.d02238fa-4892-6c21-cd77-e5e70d20e9b1
                 savecore-succcess = 1
                 dump-dir = /var/crash/unknown
                 dump-files = vmdump.0
                 os-instance-uuid = d02238fa-4892-6c21-cd77-e5e70d20e9b1
                 panicstr = kernel heap corruption detected
                 panicstack = fffffffffba4e8d4 () | 
genunix:kmem_slab_free+c1 () | genunix:kmem_magazine_destroy+6e () | 
genunix:kmem_cache_magazine_purge+dc () | 
genunix:kmem_cache_magazine_resize+40 () | genunix:taskq_thread+2d0 () | 
unix:thread_start+8 () |
                 crashtime = 1454255408
                 panic-time = Sun Jan 31 16:50:08 2016 CET
         (end fault-list[0])

         fault-status = 0x1
         severity = Major
         __ttl = 0x1
         __tod = 0x56ae3451 0xa9332f8

Last time you mentioned setting kmem_flags=0xf in /etc/system, but you 
also noted that it would cause a performance impact. Can you judge on 
that performance impact?

Thanks,
Stephan