From owner-freebsd-bugs@freebsd.org Wed Aug 23 09:44:31 2017 Return-Path: Delivered-To: freebsd-bugs@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 985CCDE2A17 for ; Wed, 23 Aug 2017 09:44:31 +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 7BD8269414 for ; Wed, 23 Aug 2017 09:44:31 +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 v7N9iUAw065717 for ; Wed, 23 Aug 2017 09:44:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld Date: Wed, 23 Aug 2017 09:44:31 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2017 09:44:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #95 from Mark Millard --- 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.=