From owner-freebsd-stable@freebsd.org Fri Apr 20 12:39:58 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 904F9F9EEAC for ; Fri, 20 Apr 2018 12:39:58 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::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 3058887117 for ; Fri, 20 Apr 2018 12:39:58 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yb0-x22c.google.com with SMTP id c10-v6so2944142ybn.7 for ; Fri, 20 Apr 2018 05:39:58 -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=HhwPYVLWW2XVUtiUYTx/OAN+IPjpFKTm69F9nbJcqHM=; b=YHQ1bmLHP7vggSxc7TwfFd5VzCm8bpVI5spyNccoQfLnHUTMslKpGUbAN/hwVH7fHW Vz96BhEIKIj4fSs6ZeXFdQ0KCbIV3QrVretlJDzcWbM+SsHuvXPL5jaqlpIlz/tP1Hml h65b/IoCMPTyIU6f53UsKGmtsg/u3hTD3rKGbtVBajW9qYQ7suOiBIexgHNcPJjVwJlw os/2ApZDOvOwKD8pRBSX/F090JxMFscchGXgUJDnWxkX5pO/xJxnP1j14ELmhltYujH3 II3RfUoTNUJmH6SY4tPmivOgWRpgX/CmRXCa+U4RKhYpPPVIzJvPSm9LW7oULAO8bsFN 1RRg== 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=HhwPYVLWW2XVUtiUYTx/OAN+IPjpFKTm69F9nbJcqHM=; b=ZemghcuzGGaVgehvMpyGRYz6DhxyZzM2bpZi9050qZiroIQ1fFmqoeT1g6cqlRCCWS tUN589kz+TlAK0/pKo0+SA6GO02nMI7FyCYjuPOyiIAQNRp2H4SE/Xw2XqNOsuXPI+cN 1kcAjfH4+P4fG8fgTx8BBzqDdpSy5aAA4xSgE26HH/LX6ZyZoMSPlz+C/m+W2ODOTFwx dsy37KgQRFVwBti8EBYb67UrhjqbpAghB3VXqV/2/AiILAt+LtrEyQvxZ/2VTKZld4Ca 0GUtMKbDomhUUzcRgGZCXnuVrrMwUn1FG1QREZ6hkdm49MI8JbfIlH6ZQm2EllJfxKt/ 5B2Q== X-Gm-Message-State: ALQs6tBLTgOmG2V9naKDj6/jW61drV5EFrAUZ9dPnQrh1OweYRDnvQES oTkEuZoBxNB0ibwKz0hL6pRqKxZ3dW2A+JojJQdytg== X-Google-Smtp-Source: AIpwx4+BLYTP5XOHPRaK8TBva3j1ns7FVkVNbPVRpNggVlBDbeCpU7FK96mNmwQpHxj4eRQEsnVhvqxkY+3q3Jfe1X4= X-Received: by 2002:a25:20d7:: with SMTP id g206-v6mr6078217ybg.71.1524227997291; Fri, 20 Apr 2018 05:39:57 -0700 (PDT) MIME-Version: 1.0 References: <70328375-165e-6ba4-8c21-03acd6ae8933@ingresso.co.uk> In-Reply-To: <70328375-165e-6ba4-8c21-03acd6ae8933@ingresso.co.uk> From: Nimrod Levy Date: Fri, 20 Apr 2018 12:39:46 +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 12:39:58 -0000 To be honest, I can't remember for certain what's set in the BIOS right now. The last post I made was from 3/17 and it says I have the memory clock lowered and c-states disabled. I don't think I've changed anything but the build of stable since then. -- Nimrod On Fri, Apr 20, 2018 at 7:55 AM Pete French wrote: > > > On 20/04/2018 12:48, 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. > > What setting sdo you have - just the ones I listed or some in the BSD > setup itself ? I am surprised that the operson who said they were > getting an actual Epyc server hasn't commented again on the thread. > Hopefully that means it works fine on the server hardware :-) > > I have seen a few commits go through in STABLE related to VM which > interest me, and which might cause hangs, so we shall see how it goes. > Possibly looking at the Ryzen issue has flushed out a few VM problems > anyway, which would be good, as more stbaility is always good (and I > have a vague hope it might fix the mysetrious Go hangs too). > > -pete. > -- -- Nimrod