Date: Thu, 30 Mar 2017 22:32:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215972] Bhyve crash more then 1 cpu AMD Message-ID: <bug-215972-27103-LNJHGqU26o@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 --- Comment #9 from Peter Grehan <grehan@FreeBSD.org> --- Insta-repro for me on a Ryzen 1700. Happens almost immediately on install w= ith >=3D 2 vCPUs, and the more configured, the faster the freeze. Single vCPU i= nstall is reliable, and I've been able to get occasional long uptimes with server sku's and 2 vCPUs. I also see cases where it's only some vCPUs that are stuck at 100% - someti= mes 2, with the remainder idle. The RIPs of the spinning vCPUs are generally constant, indicating a lock-spin or similar. To debug further with Windows, it probably needs the Windows kernel debugge= r to be hooked up, and then trapped into once the spin is seen. However, I can repro this doing a FreeBSD buildworld with >=3D 12 vCPUs. It= takes a lot longer (~20 mins) but seems to be reliable. Backtraces in ddb seem to show a missed IPI while holding a spinlock, which eventually blocks the ent= ire system. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215972-27103-LNJHGqU26o>