From owner-freebsd-current@freebsd.org Mon Oct 22 09:30:30 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 D0EA4FF1103 for ; Mon, 22 Oct 2018 09:30:30 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5264B70DAC for ; Mon, 22 Oct 2018 09:30:29 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Mon, 22 Oct 2018 09:30:22 +0000 Authentication-Results: out.migadu.com; auth=pass (plain) Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id E56197BA-21D1-4B5A-A5B1-7E7B5EEFBAB3.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Mon, 22 Oct 2018 09:30:22 +0000 Date: Mon, 22 Oct 2018 12:30:17 +0300 From: Greg V Subject: Re: Current status of Ryzen (non-)support To: Hannes Hauswedell Cc: freebsd-current@freebsd.org Message-Id: <1540200618.1834.0@smtp.migadu.com> In-Reply-To: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> X-Mailer: geary/0.12.4 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bh=DGPkRN6FkJFlzKw4oruVy0lCbSv5u9uQtGM7xrONPS0=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=WdWKBKO/Iz5vrBAhrBvuB5eJmbXhWf1Md5F6nA74fA3QoER9F6sVSGROSwF031V4nl9m1r8ba4d6cDplY10+wfFz15Ebnsx46vIM924hU45Y3ouOxJoWXNiOI7VKPLM4CF6DgbRUMDSCunHbBmSrA4nJy4OTbl0bo/vTQgnoSLs= 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 09:30:31 -0000 On Sun, Oct 21, 2018 at 7:09 PM, Hannes Hauswedell=20 wrote: > Hi everyone, >=20 > I wanted to ask what the current status of Ryzen support is and/or > whether any new changes are planned. >=20 > 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.html > * no full system freezes, but under load, e.g. building with 12=20 > threads, > programs start to segfault. > * memtest86 ran through without issues > * on a Linux dual boot I haven't had any issues >=20 > Is this a known problem? Anythings I can do about it? I thought the > Ryzen problem were only supposed to happen with first generation=20 > CPUs... First gen (R7 1700) here, overclocked to 3.9GHz, also running CURRENT=20 =97 never had any unexpected segfaults, even when building with 16=20 threads. The only bug is that the bottom (chipset) PCIe slot breaks when an NVMe=20 SSD is installed / chipset USB3 ports don't work: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231923 =