From owner-freebsd-stable@freebsd.org Wed Jan 24 14:22:14 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 1229BED69CF for ; Wed, 24 Jan 2018 14:22:14 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic313-13.consmr.mail.bf2.yahoo.com (sonic313-13.consmr.mail.bf2.yahoo.com [74.6.133.123]) (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 AFC358B582 for ; Wed, 24 Jan 2018 14:22:13 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: Gsj0NkcVM1kRUiULzFa526IvpqbLfMk7O.nVJO2pYQ3MTmMFHT5WyHfaNkv7xak KZLJYdGyUCdXIeG3F6CufSEAl19tALwAeSXU9zDY2Us77IkFdjj8jZfw_9aY0r30C8EacaGdyyva .XzAIzFBSYVsKqjNYGZFMKUgarh1pj4V0Aci0LEGFBl2r1vfUvqW3twCnM.EdvcmjlQgaGpTH9AM ap5W8.s6Yv6Eiu9mvnhQVtbh9kiDt4cEhdk2l_Cf5wsF_i49Ntq31c.TW9olPyrxkT9gp6XD3cwM 1VET5ab9vgQAVr1plNl1IACmLZQ75AH6tkQrJDzebs9Dcf7F37MQLx78wCkJONj7lTVVFdpmiR58 WtpZH09sNG5GBTS3zTi_g33MExHneQzg_9xOH525c3p5yQj.7gJVixrzASjiQjoFyUW4oqHh3jl7 4Wlex3OqVUc_JLNWe3b7DbLIo5jsLFgYzjZsDeVoWNwqYgZRBZvo9l8x3Xzf_NVRkorY- Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.bf2.yahoo.com with HTTP; Wed, 24 Jan 2018 14:22:07 +0000 Received: from smtp104.rhel.mail.bf1.yahoo.com (EHLO [192.168.1.25]) ([98.139.230.215]) by smtp409.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 170b2f3726a0d666f3526f64f209f2d0; Wed, 24 Jan 2018 14:22:02 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Ryzen issues on FreeBSD ? Message-Id: Date: Wed, 24 Jan 2018 06:22:00 -0800 To: nimrodl@gmail.com, michaelp@bsquare.com, FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3445.5.20) 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 14:22:14 -0000 Mike Pumford michaelp at bsquare.com wrote on Wed Jan 24 12:03:04 UTC 2018 : > I've run into this on modern Intel systems as well. The RAM is sold as > 2400 but thats actually an overclock profile. If I actually enabled it > (despite both board and RAM being qualified for that) the system ends up > locking up or crashing as soon as you stress it. Go back to the standard > DDR profile advertised by the RAM and it is totally stable. The reported fails are during idle time as I understand. Things are working when the CPU's are kept busy from what I've read in the various notes. The hang-ups are during idle times. "the system ends up locking up or crashing as soon as you stress it" does not sound like a matching context. That a slower RAM speed might help idle behave correctly is interesting given the Zen and Ryzen dependence on RAM speed for the speed of its internal interconnect-fabric's operation. I'll note that, if one goes through the referenced Linux exchanges about this, Ryzen Threadripper's examples are also reported to have the problem. === Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late)