Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Feb 2018 19:49:24 -0500
From:      George Mitchell <george+freebsd@m5p.com>
To:        freebsd-stable@freebsd.org
Subject:   Re: Ryzen issues on FreeBSD (can we sum up yet)?
Message-ID:  <11382853-af10-c629-1e6a-21ab8fc37f53@m5p.com>
In-Reply-To: <tkrat.7fad2b76b85bc4b1@FreeBSD.org>
References:  <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <a601973f-9205-8dd9-7f78-a7f03985ab4a@sentex.net> <CAMgUhpop3=J7TQimK2iHdGTc=hnTgCEZDqibDSRCyTPMWX5wJQ@mail.gmail.com> <CAMgUhpop54hJ%2Biq_VYYqrEHgSapmMu_GmOPaOsmhA=QbjPEZ5A@mail.gmail.com> <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC%2BD9fddENPiiFng@mail.gmail.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <tkrat.8fa97919286143d7@FreeBSD.org> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <CADbMJxkRR8s1=WWXP%2BH9eOHv_UWMQrUR=_E4aFw91VCeep82pw@mail.gmail.com> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <tkrat.975666e9f483a6a0@FreeBSD.org> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> <tkrat.ada77e0420783bed@FreeBSD.org> <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> <tkrat.e541d1b83f4f6c75@FreeBSD.org> <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net> <c0319297-d47d-449d-a6f1-2529d1d38541@sentex.net> <5A71C5AE.6020202@grosbein.net> <tkrat.7fad2b76b85bc4b1@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--UHiw2ZLU1f9rkPRlZ9ZHFIzgb2BrHpPxL
Content-Type: multipart/mixed; boundary="zyBKuChoOjBAhjiBBm9TjE3hYCA3mg28k";
 protected-headers="v1"
From: George Mitchell <george+freebsd@m5p.com>
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>
 <dd29d77a-deb9-423e-f9b8-cb07387bbfd5@sentex.net>
 <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com>
 <a601973f-9205-8dd9-7f78-a7f03985ab4a@sentex.net>
 <CAMgUhpop3=J7TQimK2iHdGTc=hnTgCEZDqibDSRCyTPMWX5wJQ@mail.gmail.com>
 <CAMgUhpop54hJ+iq_VYYqrEHgSapmMu_GmOPaOsmhA=QbjPEZ5A@mail.gmail.com>
 <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC+D9fddENPiiFng@mail.gmail.com>
 <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk>
 <tkrat.8fa97919286143d7@FreeBSD.org>
 <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net>
 <CADbMJxkRR8s1=WWXP+H9eOHv_UWMQrUR=_E4aFw91VCeep82pw@mail.gmail.com>
 <343acf99-3e9e-093a-7390-c142396c2985@sentex.net>
 <tkrat.975666e9f483a6a0@FreeBSD.org>
 <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net>
 <tkrat.ada77e0420783bed@FreeBSD.org>
 <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net>
 <tkrat.e541d1b83f4f6c75@FreeBSD.org>
 <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net>
 <c0319297-d47d-449d-a6f1-2529d1d38541@sentex.net>
 <5A71C5AE.6020202@grosbein.net> <tkrat.7fad2b76b85bc4b1@FreeBSD.org>
In-Reply-To: <tkrat.7fad2b76b85bc4b1@FreeBSD.org>

--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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11382853-af10-c629-1e6a-21ab8fc37f53>