From owner-freebsd-stable@freebsd.org Fri Apr 20 11:48:52 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 9AA5CF96579 for ; Fri, 20 Apr 2018 11:48:52 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 3B407786B5 for ; Fri, 20 Apr 2018 11:48:52 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x22c.google.com with SMTP id q12-v6so2646885ywj.0 for ; Fri, 20 Apr 2018 04:48:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YQGMYROybp839OKm995gtGnO5kqpA2j9kZkRB1Wv2+A=; b=O3S8dpYReFrvm8S8AMD2WUwYH0DZU9rGp2mKdq6xwlWpkxhQf8zBF9YNbtNUAWnwLH /vrxyAjwUxr3Cnlze0fOxTs4MnmZE4QkszlhneKkicX5zVZnrXwdax078VKXtL3ZbRXi llSeyjOeGWhpXdpEVY01h5liZOhgS/zLoMA86WWNklriANe23KZO8R4x6Jn7rl6tSNSj PIuUNwPvaHKLsCG6Ce8Jqt3oHrYes4aEC6IPLj8nx9hyLFVxRu+CSc1+b9SGO6ZaKh0p HU6Q/EYD5Kwx1hbfFAGoyYPgD1NzwvaJXZzbtEn2dxx1dHLaY5d77fEJKwIJ17jJ/fX5 igdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YQGMYROybp839OKm995gtGnO5kqpA2j9kZkRB1Wv2+A=; b=ACnU/RT3YmuBGahI3pgqr9CKs045dwKKpp55IANh7eMftxsy5ivyyuX5irprVcR/8p 1D6oSVHuurYgwjF+aiqmaO9EbwN/uF8uhRo5anAyRCZfA9aguuztqXkvaCZCdrvYEqEj HyzzjXf2aW8+3/8GCjerYf2noH+c45leTwYC3dbyrZH0pG3a4rZSZuWuhNvl9PJemkUN e/imsLInF9TQYJSM4EWZjkRs4zql5xUPdQW957VqbcGc9IrIBD9p6FpK+8HBoCa7oQSw mKBPqpBYhcRQTVX7UlWzKnaHoySMuJeNBNvdjQM1bnda3e0nHLXPh5H8p85S2bnLpR/b aBmg== X-Gm-Message-State: ALQs6tDwhQs+7/aM/RehbrHHKAPlFAPmA+X1uvh9GAn1If7f6YIdI7es rnn57JbuMCQVGnb5WjWkdy9AG6cHjQWTHd4Po5gCdg== X-Google-Smtp-Source: AIpwx49LP+mCV2k1LsZNpKw4B65OPDFAYp7wsCPHq3gkDjJo16VoPCtQiV6WKMDNa4lKayu2syEgt5PxvB/h8lIA0yM= X-Received: by 2002:a81:9ccf:: with SMTP id t198-v6mr456034ywg.352.1524224931502; Fri, 20 Apr 2018 04:48:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nimrod Levy Date: Fri, 20 Apr 2018 11:48:40 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French Cc: eric@vangyzen.net, freebsd@hda3.com, truckman@freebsd.org, freebsd-stable@freebsd.org, avg@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 20 Apr 2018 11:48:52 -0000 I'm really glad to see that I'm not the only one still interested in this thread. I don't really have anything new to contribute. I've been getting about a week or so uptime out of my box. My habit has been to see if it hangs, then reboot and rebuild latest stable and reboot and run that for a while. Although now that this thread pops back up, I just realized it's been 2 weeks since the last cycle. I don't trust it yet, but I've seen clear improvement since this started. On Fri, Apr 20, 2018 at 7:18 AM Pete French wrote: > So, resurrecting the thread from a few weeks ago, as I finally found > time yesterday to out together the Ryzen machine I bought the parts for in > Jaunary (busy year at work....). All went smoothl;y, checked it > booted up, used it for 15 minutes, was impressed by the speed and went > home. > > ...and by the time I got home, an hour or so later, it had locked up hard. > > I was somewhat dissapointed, as I had seen various fixes go in,. and had > hoped > the issues were fixed. This morning I have booted the machine back up, > tweaking the BIOPS to do things mentioned in this thread, viz: > > Disable Turbo Boost > Disable SMT > Disable global C-states > > The memory was already ruunning correctly at 2133 (though I have locked > that > in the BIOS too) and I was already using kern.eventtimer.periodic=1, so > the lockup was not related to those. Its the latest BIOS, and a -STABLE > build from yesterday. > > I suspect it will now be stable, but I was wondering if anyone was any > further > forward on working out which of the settings above are the ones which 'fix' > the issue - or indeed if its really fixed, by them or just made far less > likely > to happen. > > Anyone got any more comments on this ? > > cheers, > > -pete. > _______________________________________________ > 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" > -- -- Nimrod