From owner-freebsd-bugs@freebsd.org Wed Jul 26 20:57:13 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 810A9DB029C for ; Wed, 26 Jul 2017 20:57:13 +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 6218676A08 for ; Wed, 26 Jul 2017 20:57:13 +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 v6QKvDxo097140 for ; Wed, 26 Jul 2017 20:57:13 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, 26 Jul 2017 20:57:13 +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 Some People X-Bugzilla-Who: nbe@renzel.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, 26 Jul 2017 20:57:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #13 from Nils Beyer --- (In reply to Don Lewis from comment #12) > I'm pretty sure I saw one while doing a buildworld on ZFS as well. I thi= nk these errors occur less frequently on ZFS. I just did two poudriere run= s with tmpfs disabled and didn't see this error. try my buildkernel/buildworld "ryzen_stress_test.sh" script - let it run for 24h. Execute with: /usr/bin/nohup sh ryzen_stress_test.sh & and hope for a "nohup.out" file like this: ---------------------------------------------------------------------------= -- mkdir: /tmp/ryzen_stress_test: File exists Wed Jul 26 19:23:09 CEST 2017 begin Wed Jul 26 19:45:04 CEST 2017 end - errorcode 0 Wed Jul 26 19:45:04 CEST 2017 begin Wed Jul 26 20:07:06 CEST 2017 end - errorcode 0 Wed Jul 26 20:07:06 CEST 2017 begin Wed Jul 26 20:29:09 CEST 2017 end - errorcode 0 Wed Jul 26 20:29:09 CEST 2017 begin Wed Jul 26 20:44:52 CEST 2017 end - errorcode 2 Wed Jul 26 20:44:52 CEST 2017 begin Wed Jul 26 21:06:52 CEST 2017 end - errorcode 0 Wed Jul 26 21:06:52 CEST 2017 begin Wed Jul 26 21:28:55 CEST 2017 end - errorcode 0 Wed Jul 26 21:28:55 CEST 2017 begin Wed Jul 26 21:50:57 CEST 2017 end - errorcode 0 Wed Jul 26 21:50:57 CEST 2017 begin Wed Jul 26 22:13:00 CEST 2017 end - errorcode 0 Wed Jul 26 22:13:00 CEST 2017 begin Wed Jul 26 22:35:00 CEST 2017 end - errorcode 0 Wed Jul 26 22:35:00 CEST 2017 begin ---------------------------------------------------------------------------= -- > My first suspicion is that this could be race condition in our code expos= ed by more parallelism. I don't think so because this does happen in poudriere builds, too. These builds are mainly single-thread builds - "kf5-kservice-5.36.0" for instance generated that though it is single-threaded. And for buildkernel/buildworld, this does not happen on my Intel system with the same number of threads (20) > Which version of the share page patch are you running? this one: ---------------------------------------------------------------------------= ---- Index: sys/amd64/include/vmparam.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/amd64/include/vmparam.h (revision 321399) +++ sys/amd64/include/vmparam.h (working copy) @@ -176,7 +176,7 @@ #define VM_MAXUSER_ADDRESS UVADDR(NUPML4E, 0, 0, 0) -#define SHAREDPAGE (VM_MAXUSER_ADDRESS - PAGE_SIZE) +#define SHAREDPAGE (VM_MAXUSER_ADDRESS - 2*PAGE_SIZE) #define USRSTACK SHAREDPAGE #define VM_MAX_ADDRESS UPT_MAX_ADDRESS ---------------------------------------------------------------------------= ---- > Earlier you mentioned not seeing this on the machine using the original v= ersion. I think you mean this comment here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399#c127 I haven't seen them yet at that time - but they appeared in a following poudriere session... --=20 You are receiving this mail because: You are the assignee for the bug.=