Date: Sun, 25 Feb 2018 09:51:37 -0800 From: Peter Grehan <grehan@freebsd.org> To: Mike Tancsa <mike@sentex.net> Cc: Nimrod Levy <nimrodl@gmail.com>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?) Message-ID: <2f2b6f96-d6ef-8e02-966d-dcbbfb0c92fb@freebsd.org> In-Reply-To: <425be16f-9fdc-9ed6-72b1-02e28bfd130f@sentex.net> References: <a687883a-b2a8-5b18-f63e-754a2ed445c0@sentex.net> <bbcc09cf-0072-8510-156f-5c20c301d43f@sentex.net> <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> <CAMgUhpo1C_0L86Xkzmuz5%2Be3C3zk5RNkVS9aEBEwF-2XZ4d1sQ@mail.gmail.com> <425be16f-9fdc-9ed6-72b1-02e28bfd130f@sentex.net>
index | next in thread | previous in thread | raw e-mail
Hi Mike, (moving this to -virtualization) > Actually I can confirm the same sort of hard lockup happens on my Epyc > board with RELENG11. It also happens in current. I will file a PR and > post on freebsd-current in case someone has any suggestions on how to > try and figure out whats going on. I could reproduce this on a Ryzen 1700 with HT enabled - it took ~700 seconds, and the entire machine locked up. An interesting point is a single VM was able to run to completion. I'll keep testing with various combinations of numbers of VMs, different vCPUs per VM, and pinning guest vCPUs. later, Peter.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2f2b6f96-d6ef-8e02-966d-dcbbfb0c92fb>