From owner-freebsd-stable@freebsd.org Wed Jan 17 21:46:03 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19F17EB9822 for ; Wed, 17 Jan 2018 21:46:03 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic302-49.consmr.mail.ne1.yahoo.com (sonic302-49.consmr.mail.ne1.yahoo.com [66.163.186.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D962583B33 for ; Wed, 17 Jan 2018 21:46:02 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: PtW6cqUVM1n.T74bTNXWqDMI149KVK1njFd.USVbgbXpTpy8UmvL7nIgefnS6qM UKxKTuMjMIF38tGXTLrlchSGSkWVUUw9KosQnsYMeofkdC16hxOoH9BVMGc783Qr.2JZmveQ87V9 jMb4eYG8UO.SfU.m7E7xhRmfXz4YcNKLuUZxjEzDoZAecy7lcGNQKR2aWmJfDDwicP5ws0Ck2ugI 9fWDbGAzxEJKszl1wYVabFgaBtp0SB0VralIZDiIAblEWpGXvcWTyWSJFIIns_CK6VDebCGVgyBQ Qn7QqG.TEYdRFarxyaM6eLPHjXihhtSGEiCNzJefY5N3P12J_tkziBkIVNsSIdZ0BO1XMFWnjqzk dHY_Rr2QtSifnxhIqGzhfRGiLp8qAiiXvIq6h2ounkqFMszeShvAuWrrL.vTKCzhpzNn8OZHjVCg I1_aTKqiPnTX_tfSepfqEHNELFDUyZZbqg6JgpJCm_Y1FVE2GvsjtoWAOokSaEiChg21ggIiOZNJ jwg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.ne1.yahoo.com with HTTP; Wed, 17 Jan 2018 21:45:55 +0000 Received: from smtp235.mail.ne1.yahoo.com (EHLO [192.168.1.25]) ([10.218.253.206]) by smtp414.mail.ne1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID fa2db8d0081cf196d10a9d3861c8d989; Wed, 17 Jan 2018 21:21:42 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Ryzen issues on FreeBSD ? Message-Id: <11FD366F-9C52-4AB8-BB25-A94A97832300@yahoo.com> Date: Wed, 17 Jan 2018 13:21:41 -0800 To: mike@sentex.net, nimrodl@gmail.com, FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3273) 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, 17 Jan 2018 21:46:03 -0000 Mike Tancsa mike at sentex.net wrote on: Wed Jan 17 14:31:50 UTC 2018 : > On 1/17/2018 8:46 AM, Nimrod Levy wrote: > > I've been seeing similar issues on Ryzen and asked some questions, > > here = https://lists.freebsd.org/pipermail/freebsd-stable/2017-December/088121.ht= ml > >=20 > > My previous queries didn't go anywhere. =20 > > > =20 >=20 >=20 > Thats not very promising :( Googling around, shows lots of similar > reports both on FreeBSD and Linux, but its a lot of "I tweaked this = BIOS > setting and so far so good" but nothing definitive / conclusive. = Having > to mess about with hardware settings for days on end hoping to fix > random lockups is .... not good. See Bugzilla 219399 and 221029 : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 I'm not sure how much stable/11 and the like have been tracking things that were done in head (12) during this. My use has only been via versions of head. My 1800X use was basically after head was updated to deal with what 219399 eventually was isolated to. (221029 is from splitting off problems that were not originally known to be separate.) While I had problems for 1800X that are what the 221029 bugzilla above is about, I've not had such with a 1950X in the same sorts of contexts as I had been using the 1800X. But this was under Hyper-V for both processor variants (with matching boards). I've only tried the 1950X with a native FreeBSD boot once (a fair time ago). It showed a lockup problem fairly quickly (power switch/plug time). I've never seen such (or anything analogous) under Hyper-V with extensive use. It does not look like I'll be investigating native FreeBSD on the 1950X anytime soon. (I no longer have access to the 1800X.) =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late)=