From owner-freebsd-stable@freebsd.org Sun Apr 22 11:04:12 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 621A5FB6578 for ; Sun, 22 Apr 2018 11:04:12 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 029536F79B for ; Sun, 22 Apr 2018 11:04:11 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x22b.google.com with SMTP id l15-v6so3589068ywk.3 for ; Sun, 22 Apr 2018 04:04:11 -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=4Y7CXh0APC/ux5xZI+3FzAEiP1xr8pIXStWOHq6Kjww=; b=pYHOh3Go/5UZ7q+UXJzzTXsmP9qiEXWAwwGW9BsHizWONzdT0KHBGREQDiYxycUIge 75bU40FEk/zshE+mJ1lljl/I41ELRthRVA0f7LywFOKiIup5rbQ+mUaFXrNt2ECHcWA2 HL2R6+W2ZqzOqpzSc0uRbptG363J0oIJIappaPLblB5zZnHj0e4O65Qy5g5/liTw3QJT SVwM72BbDqC7ZkR27KMR9bBMtEAOMHOf6KMpvTF6UegYOzPKpAT15HwurcYaXkF9T5xE G24IamkmbUUjKKGp3Dk8jrxTWz82M92HhERZc2MDMtEOGUfd1opHrJ1zjd5BaXDI/3nL jE2Q== 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=4Y7CXh0APC/ux5xZI+3FzAEiP1xr8pIXStWOHq6Kjww=; b=Uq/q43kBwUKyj4EIOTaZ+LemJ/trFmtb9y7V1dbokgIytlTqDoP0Q4+a54jgBL49r/ wPy1nGpyOn5pkmODq5mGdT6fr3W62PPNeSnNrZdl/TyQfzgAknXllEqSoT7e9OQQ+69/ CIyHshbn40MWb+Jir0KZ8rx5asrFqoy2+CF7vtey6c+dgT7sA4OnKeC5FHMx/9igoLuk vdlTOTlLaUhecrjkJRQhqj3OxKcHVKCG9RcllMxLRNNz3ON3BEQ+Sox6vu4rMxpfxI0r QT6QoIVXHwr0kCteldU7oOHuOp+dqkxIu3NXbkwG7p52PM+NjW+YBD7unMLXigTORvN6 CM7g== X-Gm-Message-State: ALQs6tBHmEG/jFpJV5Uwq/7eT+rJ8IIyp9XprIW7QQuxvaLxwinaVU5l A8ymtUhn5r253YJhlRxkiPOYOtwv81e759wJEvj4hg== X-Google-Smtp-Source: AIpwx48r/qyRmQn/oWpavSPQSbuOmUo+6Txm/hAqsCJPDqS2KbM93NLrmxaJd0jUHieW6hGvPqxoAcEZCV/ziJo/5fo= X-Received: by 2002:a81:3612:: with SMTP id d18-v6mr8911441ywa.381.1524395050921; Sun, 22 Apr 2018 04:04:10 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nimrod Levy Date: Sun, 22 Apr 2018 11:04:00 +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: Sun, 22 Apr 2018 11:04:12 -0000 And of course now that we say something about it, I get a lockup overnight... -- Nimrod On Fri, Apr 20, 2018 at 7:48 AM Nimrod Levy wrote: > 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 > -- -- Nimrod