From owner-freebsd-virtualization@freebsd.org Fri Mar 31 13:41:15 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC4D8D27CA5 for ; Fri, 31 Mar 2017 13:41:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9388A118 for ; Fri, 31 Mar 2017 13:41:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2VDfEFn019735 for ; Fri, 31 Mar 2017 13:41:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215972] Bhyve crash more then 1 cpu AMD Date: Fri, 31 Mar 2017 13:41:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: grehan@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 13:41:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215972 --- Comment #11 from Peter Grehan --- It's ddb from within the guest. The signature is: 1 vCPU will panic with a lock-spin timeout: CPU 11, panic spin lock 0xffffffff81ea0480 (smp rendezvous) held by 0xfffff800079da000 (tid 100093) too long vpanic() at vpanic+0x1b9/frame 0xfffffe02ba76f6f0 panic() at panic+0x43/frame 0xfffffe02ba76f750 _mtx_lock_spin_cookie() at _mtx_lock_spin_cookie+0x328/frame 0xfffffe02ba76= f7d0 __mtx_lock_spin_flags() at __mtx_lock_spin_flags+0xe0/frame 0xfffffe02ba76f= 810 smp_rendezvous_cpus() at smp_rendezvous_cpus+0xab/frame 0xfffffe02ba76f880 dtrace_sync() at dtrace_sync+0x77/frame 0xfffffe02ba76f8d0 dtrace_state_deadman() at dtrace_state_deadman+0x13/frame 0xfffffe02ba76f900 That spinlock is held by another vCPU that is waiting for an ack to it's IPI CPU 5 --- trap 0x13, rip =3D 0xffffffff81033ac2, rsp =3D 0xfffffe02c8009860, rbp = =3D 0xfffffe02c80098d0 --- smp_targeted_tlb_shootdown() at smp_targeted_tlb_shootdown+0x352/frame 0xfffffe02c80098d0 smp_masked_invlpg() at smp_masked_invlpg+0x4c/frame 0xfffffe02c8009900 pmap_invalidate_page() at pmap_invalidate_page+0x191/frame 0xfffffe02c80099= 50 pmap_ts_referenced() at pmap_ts_referenced+0x7b3/frame 0xfffffe02c8009a00 vm_pageout() at vm_pageout+0xe04/frame 0xfffffe02c8009a70 ... and all other vCPUs are waiting on the lock held by the vCPU awaiting the ack. --- trap 0x13, rip =3D 0xffffffff80a8d222, rsp =3D 0xfffffe02c8349600, rbp = =3D 0xfffffe02c8349610 --- lock_delay() at lock_delay+0x42/frame 0xfffffe02c8349610 __mtx_lock_sleep() at __mtx_lock_sleep+0x228/frame 0xfffffe02c83496a0 __mtx_lock_flags() at __mtx_lock_flags+0xe8/frame 0xfffffe02c83496f0 vm_page_enqueue() at vm_page_enqueue+0x6b/frame 0xfffffe02c8349720 vm_fault_hold() at vm_fault_hold+0x1ab9/frame 0xfffffe02c8349850 vm_fault() at vm_fault+0x75/frame 0xfffffe02c8349890 --=20 You are receiving this mail because: You are the assignee for the bug.=