From owner-freebsd-stable@freebsd.org Tue Feb 13 01:05:17 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62DBFF0AED7 for ; Tue, 13 Feb 2018 01:05:17 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D91C578D39 for ; Tue, 13 Feb 2018 01:05:16 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id w1D0nVnM011068 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 12 Feb 2018 19:49:40 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: Ryzen issues on FreeBSD (can we sum up yet)? To: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net> <5A71C5AE.6020202@grosbein.net> From: George Mitchell Message-ID: <11382853-af10-c629-1e6a-21ab8fc37f53@m5p.com> Date: Mon, 12 Feb 2018 19:49:24 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UHiw2ZLU1f9rkPRlZ9ZHFIzgb2BrHpPxL" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Mon, 12 Feb 2018 19:49:41 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 01:05:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UHiw2ZLU1f9rkPRlZ9ZHFIzgb2BrHpPxL Content-Type: multipart/mixed; boundary="zyBKuChoOjBAhjiBBm9TjE3hYCA3mg28k"; protected-headers="v1" From: George Mitchell To: freebsd-stable@freebsd.org Message-ID: <11382853-af10-c629-1e6a-21ab8fc37f53@m5p.com> Subject: Re: Ryzen issues on FreeBSD (can we sum up yet)? References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net> <5A71C5AE.6020202@grosbein.net> In-Reply-To: --zyBKuChoOjBAhjiBBm9TjE3hYCA3mg28k Content-Type: text/plain; charset=iso-8859-5 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 02/12/18 16:49, Don Lewis wrote: > [...] > I'm having really good luck with the kernel patch attached to this > message: > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D417183+0+archive/2018/f= reebsd-hackers/20180211.freebsd-hackers >=20 > Since applying that patch, I did three poudriere runs to build the set > of ~1700 ports that I use. Other than one gmake-related build runaway > that I've also seen on my AMD FX-8320E, I didn't see any random port > build failures. When I was last did some testing a few weeks ago, > lang/go would almost always fail. I also would seem random build > failures in lang/guile or finance/gnucash (which uses guile during its > build) on both my Ryzen and FX-8320E machines, but those built cleanly > all three times. >=20 > I even built samba 16 times in a row without a hang. > [...] Until this thread started last year, I had been on the verge of upgrading the build server on my net to a Ryzen. Needless to say, I postponed the change. Now it seems there is hope that a resolution for the issue may be in sight. Is it time to survey everyone's experience with the problem, and determine whether the cited patch helps? My sincere thanks in advance. -- George --zyBKuChoOjBAhjiBBm9TjE3hYCA3mg28k-- --UHiw2ZLU1f9rkPRlZ9ZHFIzgb2BrHpPxL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlqCNhsACgkQwRES3m+p 4flIiw/+MExWZ3tTUrcrbWjqkgJOlBRENjcoxeC0e1QJpsZRilib4DGu07dtsYxk 6H36b3I1V1lIHFE590ZYK6HIu7+4d4VL9yvCbdEFxzR8EhKTpZtGrXw1s61JHVe9 AZ9r/gTLyLruJpu0LfbUx0Bts51DJoWJOqj+izQVmArB6Ni9icLhBX82ezMv/rmd f2zoF8fpPgIBhB7BdYCq2p7AJD7vyRiBfEMtgXmaxX5nKSbRIJ8EG3qYjQBvzOUn 3ERuSAsCjp7gA8S/zX/X3B4VGHB3QEaDrlo8WUxA9Zk+j4+xhxT2GBbij/0iQLxy uyvEisoBBRT7jDGIEK8iJovwttSu0/GAy5vXsKEO8Q1LtpwjtE9rLDczE3GBSbEh Voca4OL0K5y+WtvMx/sCXL59ipXeGBGfYSFCnjYk0R5MDLqLVmn5s1zducwxYxBL P2wiljcAf5f6jbWH39Lod8KzJkLZ1/aIwKuJScAP7G/HT6X0trbczPQAe8+kBmzv VeISEDh37Qkf9BEf0NW2Ac8nXh67h7Pey2JxlNQ5RLcRYyuhIX9WDTFgnZ3r38Xt fFhvkafLP1TjzI0UkBuHr/LEfFaNiAAUcNv2OhEnZ8pxaZIp33bEwJEaAkwsl3gg VlycYTR3aGoNieTcYMr8ItD5c6Ob3aJ8LGfTdXk9uNgUhYVrLUg= =iidl -----END PGP SIGNATURE----- --UHiw2ZLU1f9rkPRlZ9ZHFIzgb2BrHpPxL--