From owner-freebsd-stable@freebsd.org Wed Jan 24 17:35:23 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 20F87EB74DC for ; Wed, 24 Jan 2018 17:35:23 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ADFC96B4A3 for ; Wed, 24 Jan 2018 17:35:22 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x229.google.com with SMTP id l20so12321398qtj.11 for ; Wed, 24 Jan 2018 09:35:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hda3-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Jgq6MLTrU7yySeBWoqne/PrrmvdxsaERNcSJ/h58Rzo=; b=CYAonkQmp3sJWYRwKsWjAPcJ8Yu2iHTo+I15eaezul+L/mHP9Ih3gvgAg6Dhq55pg9 uuLS2akl5FK6NqR53iXgfbk87zImRn9wsa5Ck94kOxmAtdxVs+5i2YnbmpXc5FP7YuB0 0t7vDPZnPGELvvZYGxMJvQPN5jHu2j6skNtN1ZFIgpdcuxJ+Jw2YexkQhzuzjV+O947a FbRuwoTJrZdZHJCw2BQgQFpScfcuHbA82AcOzngQW7ky7mE/Q1n1wa3lutWAH3CP2uE+ Zo7lMNJDF2w4hnBy2qrcRoiAY+hWzlxflWFPFhSDAUmRkAqPmMtI+0LML3ndMK51NFEO cksQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Jgq6MLTrU7yySeBWoqne/PrrmvdxsaERNcSJ/h58Rzo=; b=UOx2Ga5jIaSgElqkV+otLwQfB7mpZhB7NsNJJoXqMTeIBjxEKq0NJePcg7gVANxwUU JjCHPAj/I+KR31pPAcTqERYdLd4Da3FappRWI9V0cpIeobJcTA6iedM7R6BjWybXkMbp 3rmpmXUCuF8d8m5F3taKawZdfUL+0BppJYbLopWVptu8lCcT7OLTjB5T9X3g4jwCC2EU KjAQTGQhC9ZkQzgf3BtF6BRABF4GVy6P0Au2SraIMhq7Ra3Gi6tvnOB5RwUhFH9+TWFj 81k1hIJE9C530I+u0upvzRkzxhZ2C2ELVivsQWY350dvEvrzjbMCNA1FNi/OJANjrkVY duyQ== X-Gm-Message-State: AKwxyteitIlRj1LdrNi2KvYpnTmgiV+WY/sbNbIttTGjrVvdPl8/o7UQ Q7HijyNxq+QaeUwHNfKhVSpMW1c1KeOyTd1AcH4uRQ== X-Google-Smtp-Source: AH8x224X2Ds3jAWZ9FVh6hTK1T/4tTcbrHNHfXIsKjpfZIu949bvkPcG2+VqgNmCX07/KG/bTNQ6n6p0IsCN3sBbmzE= X-Received: by 10.237.43.70 with SMTP id p64mr10739836qtd.5.1516815322086; Wed, 24 Jan 2018 09:35:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Wed, 24 Jan 2018 09:35:01 -0800 (PST) In-Reply-To: References: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> From: Peter Moody Date: Wed, 24 Jan 2018 09:35:01 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) To: Alban Hertroys Cc: Mike Tancsa , Mark Millard , FreeBSD-STABLE Mailing List , Nimrod Levy Content-Type: text/plain; charset="UTF-8" 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: Wed, 24 Jan 2018 17:35:23 -0000 > I currently have a Ryzen 1600X from week 17/30, which suggests it will > have the bug. Unfortunately, I don't have it built into a system yet > as I'm waiting for DDR4 prices to become reasonable again before > ordering any, so I can't test it. I've seen the blanking screen lockup on a 1600X from 1739SUS and 1740SUS. Only with SMT enabled though. On the 1739 chip I'm also seeing cc segfaults on make -j 18 buildworld (again, just with SMT enabled). This is all so frustrating. > I'm not sure how solid this info is, should I RMA it without even > having tested that it has a problem? > > Alban Hertroys > -- > If you can't see the forest for the trees, > Cut the trees and you'll see there is no forest. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"