Date: Wed, 23 Aug 2017 09:44:31 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld Message-ID: <bug-221029-8-FkDdrPUOtN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221029-8@https.bugs.freebsd.org/bugzilla/> References: <bug-221029-8@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=3D221029 --- Comment #95 from Mark Millard <markmi@dsl-only.net> --- I've now tried Hyper-V instead of VirtualBox for building lang/ghc (the most systematic usually-quick-failure test that I've found). In this context: sysctl kern.sched.balance=3D1 sysctl kern.sched.steal_idle=3D0 did not seem to help. Nor did: sysctl kern.sched.balance=3D0 sysctl kern.sched.steal_idle=3D0 Hyper-V did not report going beyond 8 virtual processors as a problem, VirtualBox did. So for Hyper-V I assigned 14 Virtual Processors, leaving by count enough for one core (2 threads) for Windows 10 Pro. While for VirtualBox I used 8 per its report when a larger figure is set. Note: I had to avoid using a M.2 NVME SSD and instead used a SATA SSD for Hyper-V. For NVME the attempt to create the virtual machine crashes Windows 10 Pro. It created the virtual machine just fine when told to use the SATA SSD. Note: When Hyper-V is enabled, VirtualBox 64-bit is blocked --even if every Hyper-V virtual machine is off. I had to disable Hyper-V to get VirtualBox working again. [There were more issues than I've noted here as well.] --=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-221029-8-FkDdrPUOtN>