I've kicked off 3 2G vm's which do a continous
while(1) { make -j 4 buidlworld }

And one of those VM's just crashed with the message below.

The VM is clearly not able to recover from this. And probably needs to
be destroyed and restarted... Don't know it it got as far as vmrun.sh
restarting it.

1) I expect this to be due to 3 VM's running in parallel with quite some
load. But is this something that needs to be reported to stable@?
Or does this belong here on this list.
2) Killing the VM and restarting probably also kills the memory but not
the swap? And thus would allow to extract a core? I'll see when I reboot.


spin lock 0xffffffff814fa030 (smp rendezvous) held by 0xfffff80079e8d490
(tid 100097) too long
timeout stopping cpus
panic: spin lock held too long
cpuid = 3
KDB: stack backtrace:
#0 0xffffffff808e7dd0 at kdb_backtrace+0x60
#1 0xffffffff808af8b5 at panic+0x155
#2 0xffffffff8089cb71 at _mtx_lock_spin_cookie+0x241
#3 0xffffffff80c7ec7a at smp_tlb_shootdown+0x8a
#4 0xffffffff80c8066c at pmap_invalidate_range+0x2fc
#5 0xffffffff80932f6d at allocbuf+0x55d
#6 0xffffffff809317cf at brelse+0x14f
#7 0xffffffff80934b18 at bufdone+0x78
#8 0xffffffff809346c2 at biodone+0xe2
#9 0xffffffff8081c561 at g_io_schedule_up+0x1b1
#10 0xffffffff8081ca5d at g_up_procbody+0x6d
#11 0xffffffff8088198a at fork_exit+0x9a
#12 0xffffffff80c758ce at fork_trampoline+0xe
Uptime: 1h21m3s
Dumping 183 out of 2025 MB:..9%..18%..27%..35%..44%..53%..62%..79%..88%..97%
Dump complete
Automatic reboot in 15 seconds - press a key on the console to abort
cpu_reset: Stopping other CPUs
timeout stopping cpus
cpu_reset: Restarting BSP
cpu_reset: Failed to restart BSP
freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to