[OpenIndiana-discuss] why kernel panic

[Alexander Lesle]

Hello All

my Serverconfig see footer of this eMail.

I want to have my server a little bit more green, so I do yesterday
the follow things:
In ESXi set the PowerManagementSetting to "Low power"

In OI:
# /usr/sbin/pmconfig -r

adding/changing at /etc/power.conf:
device-dependency-property removable-media /dev/fb
autopm                  enable
autoS3                  default
cpupm                   enable
cpu-threshold           300s
system-threshold        always-on

# rpool
device-thresholds       /pci at 0,0/pci15ad,1976 at 10/sd at 0,0 always-on

# sanpool
# mirror0
device-thresholds       /scsi_vhci/disk at g5000cca36ad1b495       always-on
device-thresholds       /scsi_vhci/disk at g5000cca36ad1774a       always-on
device-thresholds       /scsi_vhci/disk at g5000cca36ad1780c       always-on

# bigpool
# mirror0
device-thresholds       /scsi_vhci/disk at g5000cca22bc6b319       10m
device-thresholds       /scsi_vhci/disk at g5000cca22bc7eac9       10m
# mirror1
device-thresholds       /scsi_vhci/disk at g5000cca22bc5b3ac       10m
device-thresholds       /scsi_vhci/disk at g5000cca22bc8accd       10m
# mirror2
device-thresholds       /scsi_vhci/disk at g5000cca22bc6c23b       10m
device-thresholds       /scsi_vhci/disk at g5000cca22bc8a445       10m
# mirror3
device-thresholds       /scsi_vhci/disk at g5000cca22bc18d61       10m
device-thresholds       /scsi_vhci/disk at g5000cca22bc8aa67       10m
# mirror4
device-thresholds       /scsi_vhci/disk at g5000cca22bc6b9e7       10m
device-thresholds       /scsi_vhci/disk at g5000cca22bc8d31a       10m

adding at /usr/lib/fm/fmd/plugins/disk-transport.conf:
setprop interval 24h

make all changes activ:
# /usr/sbin/pmconfig
# svcadm refresh fmd

After one hour waiting nothing happened. The HDs dont spinning down.
The wattage standing high.
After restarting server HDs spinning down.
At the new morning the server CPU is running 80% and more. I cant find
the problem why the CPU is so high. I make a restart and see at

/var/adm/messages the follow message:
Jan 16 16:01:19 ripley fmd: [ID 377184 daemon.error] SUNW-MSG-ID: SUNOS-8000-KL, TYPE: Defect, VER: 1, SEVERITY: Major
Jan 16 16:01:19 ripley EVENT-TIME: Wed Jan 16 16:01:19 CET 2013
Jan 16 16:01:19 ripley PLATFORM: VMware-Virtual-Platform, CSN: VMware-56-4d-72-01-ab-91-7d-3e-21-1c-2b-ba-9a-11-cf-42, HOSTNAME: ripley
Jan 16 16:01:19 ripley SOURCE: software-diagnosis, REV: 0.1
Jan 16 16:01:19 ripley EVENT-ID: 2e53a992-e6b4-695e-abe3-e68270a3f2b7
Jan 16 16:01:19 ripley DESC: The system has rebooted after a kernel panic.  Refer to http://illumos.org/msg/SUNOS-8000-KL for more information.
Jan 16 16:01:19 ripley AUTO-RESPONSE: The failed system image was dumped to the dump device.  If savecore is enabled (see dumpadm(1M)) a copy of the dump will be written to the savecore directory .
Jan 16 16:01:19 ripley IMPACT: There may be some performance impact while the panic is copied to the savecore directory.  Disk space usage by panics can be substantial.
Jan 16 16:01:19 ripley REC-ACTION: If savecore is not enabled then please take steps to preserve the crash image.
Jan 16 16:01:19 ripley Use 'fmdump -Vp -u 2e53a992-e6b4-695e-abe3-e68270a3f2b7' to view more panic detail.  Please refer to the knowledge article for additional informati
Jan 16 16:01:20 ripley vmxnet3s: [ID 654879 kern.notice] vmxnet3s:0: getcapab(0x200000) -> no
Jan 16 16:01:20 ripley last message repeated 3 times

OK, I know the vmxnet3 driver is spamming the log and I dont find a
solution for that.
But why a kernel panic?
The illumos-link tells me nothing
fmdump:
OpenIndiana (powered by illumos)    SunOS 5.11    oi_151a7    October 2012
root at ripley:~# fmdump -Vp -u 2e53a992-e6b4-695e-abe3-e68270a3f2b7
TIME                           UUID                                 SUNW-MSG-ID
Jan 16 2013 16:01:19.481527000 2e53a992-e6b4-695e-abe3-e68270a3f2b7 SUNOS-8000-KL

  TIME                 CLASS                                 ENA
  Jan 16 16:01:15.0101 ireport.os.sunos.panic.dump_pending_on_device 0x0000000000000000

nvlist version: 0
        version = 0x0
        class = list.suspect
        uuid = 2e53a992-e6b4-695e-abe3-e68270a3f2b7
        code = SUNOS-8000-KL
        diag-time = 1358348479 471674
        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/ripley/.2e53a992-e6b4-695e-abe3-e68270a3f2b7
                resource = sw:///:path=/var/crash/ripley/.2e53a992-e6b4-695e-abe3-e68270a3f2b7
                savecore-succcess = 0
                os-instance-uuid = 2e53a992-e6b4-695e-abe3-e68270a3f2b7
                panicstr = mutex_enter: bad mutex, lp=ffffffffc015dd38 owner=ffffff04ae5e1480 thread=ffffff00182a2c40
                panicstack = unix:mutex_panic+73 () | unix:mutex_vector_enter+446 () | genunix:cv_timedwait_hires+fd () | genunix:cv_timedwait_sig_hires+336 () | genunix:cv_timedwait_sig+4c () | fffffffff82f69c5 () | unix:thread_start+8 () |
                crashtime = 1358348372
                panic-time = 16. Januar 2013 15:59:32 CET CET
        (end fault-list[0])

        fault-status = 0x1
        severity = Major
        __ttl = 0x1
        __tod = 0x50f6c0bf 0x1cb384d8
root at ripley:~#

Any hints or solutions for the kernel panic??
Maybe a solution for the vmxnet3 driver log-spamming??

-- 
Best Regards
Alexander
Januar, 16 2013
Server:
SM X8SI6-F Board with Xeon L3426 16 GB ECC RAM, LSI9211-8i
ESXi 5.1 build 914609  with Guest OI_151a7