From owner-freebsd-current@freebsd.org Mon Oct 22 22:00:57 2018 Return-Path: Delivered-To: freebsd-current@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 B22FCFD8AFD for ; Mon, 22 Oct 2018 22:00:57 +0000 (UTC) (envelope-from h2+lists2018@fsfe.org) Received: from einhorn-mail.in-berlin.de (einhorn-mail.in-berlin.de [217.197.80.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.in-berlin.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47D1C76788 for ; Mon, 22 Oct 2018 22:00:56 +0000 (UTC) (envelope-from h2+lists2018@fsfe.org) X-Envelope-From: h2+lists2018@fsfe.org X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id w9MM0nJP028810 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 23 Oct 2018 00:00:49 +0200 To: freebsd-current@freebsd.org References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> <20181021173327.GJ5335@kib.kiev.ua> From: Hannes Hauswedell Openpgp: preference=signencrypt Autocrypt: addr=h2+lists2018@fsfe.org; prefer-encrypt=mutual; keydata= mDMEWjvrCBYJKwYBBAHaRw8BAQdA69H3pIQlZtmfHWcHtdO/QHaSCGncSJ5WCcrEOyLNGFq0 KUhhbm5lcyBIYXVzd2VkZWxsIDxoYW5uZXNAaGF1c3dlZGVsbC5uZXQ+iJkEExYIAEECGwMF CQPCZwAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AWIQTvVvZqpoM+Ms4FP1Vvny4w7LN5dwUC WjvrdQIZAQAKCRBvny4w7LN5d/StAQClFHWUmhZehalNE7JFiRuNpwi0/v2jKA+IU7/IvjPj HQD+JC3jTzmchT+R+SMGM4aNvHSnkM3r7z2Y46syUJz6bwC0H0hhbm5lcyBIYXVzd2VkZWxs IDxoMkBmc2ZlLm9yZz6IlgQTFggAPhYhBO9W9mqmgz4yzgU/VW+fLjDss3l3BQJaO+tWAhsD BQkDwmcABQsJCAcCBhUICQoLAgQWAgMBAh4BAheAAAoJEG+fLjDss3l3qg8A/io/KtgVK0C0 RQO4dTv4Cfof7i7Jz6BgJKNCDQnmvFl6AP0VeYDCvWJksngds2ZKz89jboAzAEzAU4/Gmx2G DJpiD7QxSGFubmVzIEhhdXN3ZWRlbGwgPHBvbGl0aWtAaGFubmVzLmhhdXN3ZWRlbGwubmV0 PoiWBBMWCAA+FiEE71b2aqaDPjLOBT9Vb58uMOyzeXcFAlo764MCGwMFCQPCZwAFCwkIBwIG FQgJCgsCBBYCAwECHgECF4AACgkQb58uMOyzeXc2RwD+PG/X0gaPyWXQfhsVC0h+KcRDRNXC U862y9AgstX0bQQBAP+oSMSu1TECWEZAlsijAL2IMpYJLObC0GRGcySHHlYOuDgEWjvrCBIK KwYBBAGXVQEFAQEHQDkbc3o1Tx1VoU3R/FTBZU466MK/hCV4wR5+LIYpy/VBAwEIB7g4BFo7 6wgSCisGAQQBl1UBBQEBB0A5G3N6NU8dVaFN0fxUwWVOOujCv4QleMEefiyGKcv1QQMBCAeI fgQYFggAJhYhBO9W9mqmgz4yzgU/VW+fLjDss3l3BQJaO+sIAhsMBQkDwmcAAAoJEG+fLjDs s3l3NmoBAPybRpTZWiShUDJRfmqSxH0EzcdRuXQC72D8DapTcrrpAQCubhUI634RzxbXYvxa WQctZgBLkfsw+qv+FWB2PfExDA== Subject: Re: Current status of Ryzen (non-)support Message-ID: <6845b53c-63db-7a76-cddb-2ca1b8408e1b@hauswedell.net> Date: Tue, 23 Oct 2018 00:00:39 +0200 MIME-Version: 1.0 In-Reply-To: <20181021173327.GJ5335@kib.kiev.ua> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8x5LMPkBHahSYc4UliLd6P2QVCpF5GcuV" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2018 22:00:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8x5LMPkBHahSYc4UliLd6P2QVCpF5GcuV Content-Type: multipart/mixed; boundary="LDrIDj0YwWjWeXysQ05ONSkk1imU4W9Me"; protected-headers="v1" From: Hannes Hauswedell To: freebsd-current@freebsd.org Message-ID: <6845b53c-63db-7a76-cddb-2ca1b8408e1b@hauswedell.net> Subject: Re: Current status of Ryzen (non-)support References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> <20181021173327.GJ5335@kib.kiev.ua> In-Reply-To: <20181021173327.GJ5335@kib.kiev.ua> --LDrIDj0YwWjWeXysQ05ONSkk1imU4W9Me Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 21.10.18 19:33, Konstantin Belousov wrote: > On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote: >> Hi everyone, >> >> I wanted to ask what the current status of Ryzen support is and/or >> whether any new changes are planned. >> >> My situation: >> * second generation Ryzen: 2600X >> * running -CURRENT >> * I have done the things described here: >> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.h= tml > This was based on the public errata document for the first gen ryzen. > I am not aware of the erratas ('revision guides' in AMD terminology) > for the second gen ryzens. >=20 > For now you can only get fixes for microcode from your BIOS updates. >=20 Thanks for the replies everyone! I ran stress-ng --vm 12 --vm-bytes 12G --verify -v and could reproducibly produce memory issues on FreeBSD, but not on Linux= =2E After updating the BIOS and deactivating swap on FreeBSD they seem to be gone now, I am still investigating whether turning swap back on brings them back which would hint at a possible disk problem or whether the BIOS update changed this behaviour. Disk initially appeared more plausible, but further tests suggest against it (it's a fairly new SSD, multiple ZFS scrubs show now errors, there are no smart errors or other errors reported by the kernel in regard to the disk). Best regards, Hannes --=20 pgp-key: https://hannes.hauswedell.net/hannes_hauswedell_public_key.asc fingerprint: EF56 F66A A683 3E32 CE05 3F55 6F9F 2E30 ECB3 7977 --LDrIDj0YwWjWeXysQ05ONSkk1imU4W9Me-- --8x5LMPkBHahSYc4UliLd6P2QVCpF5GcuV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQTvVvZqpoM+Ms4FP1Vvny4w7LN5dwUCW85IkAAKCRBvny4w7LN5 dzX/AP9X1o39KyRRuXhQBtEbQwhpQciafOyd2rCcy+ouZRZOUgD/dy1ctvyxi+wV uMvKRVnKyvqfHIwj76iE5qRnE/uXGQY= =hMi1 -----END PGP SIGNATURE----- --8x5LMPkBHahSYc4UliLd6P2QVCpF5GcuV--