kern/47482: kernel panic: possibly vmt0 problem

[pettai%nordu.net@localhost]

>Number:         47482
>Category:       kern
>Synopsis:       kernel panic: possibly vmt0 problem
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 21 15:30:00 +0000 2013
>Originator:     Fredrik Pettai
>Release:        NetBSD 6.0.1 (i386)
>Organization:
NORDUnet A/S
>Environment:
NetBSD stats3 6.0.1 NetBSD 6.0.1 (SD_VMT_TWEAK) #1: Wed Dec 26 21:56:55 CET 
2012  
root%stats3.nordu.net@localhost:/usr/obj/sys/arch/i386/compile/SD_VMT_TWEAK i386
>Description:
One of our NetBSD 6.0.1 (i386) systems running as a VMware guest on a ESX 
cluster, got a kernel panic. What's unique about this host, is that it's the 
only NetBSD server that has vmt0 (VMware tools) enabled in the kernel, hence we 
think this could be related to vmt0.

Here is the messages log:

Jan 21 03:26:55 stats3 syslogd[173]: restart
Jan 21 03:26:55 stats3 /netbsd: fatal double fault in supervisor mode
Jan 21 03:26:55 stats3 /netbsd: trap type 13 code 80000000 eip c07964ea cs 8 
eflags 10287 cr2 d7e3dff0 ilevel 6
Jan 21 03:26:55 stats3 /netbsd: panic: trap
Jan 21 03:26:55 stats3 /netbsd: cpu0: Begin traceback...
Jan 21 03:26:55 stats3 /netbsd: 
printf_nolog(c0bad84f,d7c7ff7c,d7c7ff7c,c07964ea,8,10287,d7e3dff0,6,0,0) at 
netbsd:printf_nolog
Jan 21 03:26:55 stats3 /netbsd: trap_tss() at netbsd:trap_tss
Jan 21 03:26:55 stats3 /netbsd: --- trap via task gate ---
Jan 21 03:26:55 stats3 /netbsd: 1000:
Jan 21 03:26:55 stats3 /netbsd: cpu0: End traceback...
Jan 21 03:26:55 stats3 /netbsd: 
Jan 21 03:26:55 stats3 /netbsd: dumping to dev 4,1 offset 1056842
Jan 21 03:26:55 stats3 /netbsd: dump succeeded
Jan 21 03:26:55 stats3 /netbsd: 
Jan 21 03:26:55 stats3 /netbsd: 
Jan 21 03:26:55 stats3 /netbsd: vmware: sending length failed, eax=00000000, 
ecx=00000000
Jan 21 03:26:55 stats3 /netbsd: vmt0: failed to send shutdown ping
Jan 21 03:26:55 stats3 /netbsd: vmware: close failed, eax=00000000, ecx=00000000
Jan 21 03:26:55 stats3 /netbsd: rebooting...

We have some files in /var/crash/, so if someone can give us instructions on 
what we should do with them, just let us know...

stats3# ls -l /var/crash/
total 37990
-rw-------  1 root  wheel         2 Jan 21 03:27 bounds
-rw-------  1 root  wheel        52 Dec 26 22:12 cron.core
-rw-------  1 root  wheel         5 Oct 13 15:43 minfree
-rw-------  1 root  wheel  38288461 Jan 21 03:27 netbsd.0.core.gz
-rw-------  1 root  wheel    535779 Jan 21 03:27 netbsd.0.gz
>How-To-Repeat:
First time we've seen this. 
The server has been up since late december last year.
>Fix: