Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 May 2018 11:14:51 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 215972] Bhyve crash more then 1 cpu AMD
Message-ID:  <bug-215972-27103-X5VV9ecgr9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215972-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-215972-27103@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215972

Adam Jimerson <vendion@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vendion@gmail.com

--- Comment #39 from Adam Jimerson <vendion@gmail.com> ---
It seems I'm running into this issue still running FreeBSD 12.0-CURRENT as =
the
guest and trying to run make buildworld.

Host: 11.1-RELEASE-p10
Guest: 12.0-CURRENT

Stacktrace
---
spin lock 0xffffffff81d42760 (smp rendezvous) held by 0xfffff800040c0560 (t=
id
100089) too long
panic: spin lock held too long
cpuid =3D 3
time =3D 1525935605
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe000046e=
570
vpanic() at vpanic+0x18d/frame 0xfffffe000046e5d0
panic() at panic+0x43/frame 0xfffffe000046e630
_mtx_lock_indefinite_check() at _mtx_lock_indefinite_check+0x8c/frame
0xfffffe000046e650
_mtx_lock_spin_cookie() at _mtx_lock_spin_cookie+0xd5/frame 0xfffffe000046e=
6c0
__mtx_lock_spin_flags() at __mtx_lock_spin_flags+0xd8/frame 0xfffffe000046e=
700
smp_targeted_tlb_shootdown() at smp_targeted_tlb_shootdown+0xd8/frame
0xfffffe000046e780
smp_masked_invlpg_range() at smp_masked_invlpg_range+0x42/frame
0xfffffe000046e7b0
pmap_invalidate_range() at pmap_invalidate_range+0x291/frame 0xfffffe000046=
e810
pmap_remove_ptes() at pmap_remove_ptes+0xae/frame 0xfffffe000046e870
pmap_remove() at pmap_remove+0x404/frame 0xfffffe000046e8f0
_kmem_unback() at _kmem_unback+0x43/frame 0xfffffe000046e930
kmem_free() at kmem_free+0x37/frame 0xfffffe000046e950
zone_drain_wait() at zone_drain_wait+0x374/frame 0xfffffe000046e9b0
arc_kmem_reap_now() at arc_kmem_reap_now+0xa4/frame 0xfffffe000046e9e0
arc_reclaim_thread() at arc_reclaim_thread+0x2e5/frame 0xfffffe000046ea70
fork_exit() at fork_exit+0x84/frame 0xfffffe000046eab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe000046eab0
--- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 ---
KDB: enter: panic
[ thread pid 8 tid 100056 ]
Stopped at      kdb_enter+0x3b: movq    $0,kdb_why

Sysctls
---
hw.vmm.npt.pmap_flags: 507
hw.vmm.svm.num_asids: 32768
hw.vmm.svm.disable_npf_assist: 0
hw.vmm.svm.features: 113919
hw.vmm.svm.vmcb_clean: 959
hw.vmm.vmx.vpid_alloc_failed: 0
hw.vmm.vmx.posted_interrupt_vector: -1
hw.vmm.vmx.cap.posted_interrupts: 0
hw.vmm.vmx.cap.virtual_interrupt_delivery: 0
hw.vmm.vmx.cap.invpcid: 0
hw.vmm.vmx.cap.monitor_trap: 0
hw.vmm.vmx.cap.unrestricted_guest: 0
hw.vmm.vmx.cap.pause_exit: 0
hw.vmm.vmx.cap.halt_exit: 0
hw.vmm.vmx.initialized: 0
hw.vmm.vmx.cr4_zeros_mask: 0
hw.vmm.vmx.cr4_ones_mask: 0
hw.vmm.vmx.cr0_zeros_mask: 0
hw.vmm.vmx.cr0_ones_mask: 0
hw.vmm.ept.pmap_flags: 0
hw.vmm.vrtc.flag_broken_time: 1
hw.vmm.ppt.devices: 0
hw.vmm.iommu.enable: 1
hw.vmm.iommu.initialized: 0
hw.vmm.bhyve_xcpuids: 8346
hw.vmm.topology.cpuid_leaf_b: 1
hw.vmm.topology.cores_per_package: 2
hw.vmm.topology.threads_per_core: 1
hw.vmm.create: beavis
hw.vmm.destroy: beavis
hw.vmm.trace_guest_exceptions: 0
hw.vmm.ipinum: 251
hw.vmm.halt_detection: 1

Bhyve options (running bhyve using https://github.com/churchers/vm-bhyve as=
 a
frontend if need be I can see if I can get it to spit out the full command
rather than just the options passed)
---
May 09 20:05:33:  [bhyve options: -c 4 -m 6G -AHPw -U
84b02223-f0d7-11e7-a8e5-1c1b0de910d7]
May 09 20:05:33:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s
4:0,virtio-blk,/bhyve/fbsd-current/disk0.img -s
5:0,virtio-net,tap0,mac=3D58:9c:fc:0b:23:f9]
May 09 20:05:33:  [bhyve console: -l com1,stdio]

CPU info
---
hw.model: AMD Ryzen 7 1700 Eight-Core Processor
hw.machine: amd64
hw.ncpu: 16

My FreeBSD 12-Current guest is the only one I have problems with so fair (a=
lso
have a Linux guest and another BSD guest but neither have done anything CPU
intensive)

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215972-27103-X5VV9ecgr9>