From owner-freebsd-stable@freebsd.org Sun Jun 3 14:27:45 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 DD200FD5846 for ; Sun, 3 Jun 2018 14:27:44 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::235]) (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 6EA89682C4 for ; Sun, 3 Jun 2018 14:27:44 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yb0-x235.google.com with SMTP id f79-v6so4587385ybg.2 for ; Sun, 03 Jun 2018 07:27:44 -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=Buu9HFEtVJvP9CY4MUPC13gxQ/VtRcwFU0z8DufkayU=; b=R1N5a6oSljv1GWLAbmxhiMiuk9d0Z9PFyNGOGSpvsynK5vNnalPvvELAOjt9nUVDry VZcTiaPcZuAXMwpF2AQiI1A8gviDFjVi13vU1ZfsepoXWV5kvjb645XgJd08Ym/SDQh4 QmulxYCRXy6B11c335xq/sEVSqli8ZVG3NeDYGgP0/X1KZytjViZ+qKHutVGcgKSzMLZ V/R5ErkAkNelkYQ7mQivIMrPwSyWbTr47MXus7r8iikKXAng8eWJdRIIkFrKcHnlUr+w Vi5x3suJbA9Lc9CaaAiUnHAR4mJhyAdBPU9yOW0LrlGEbNycshexdyUB5YPrR/ED+BLD OkDw== 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=Buu9HFEtVJvP9CY4MUPC13gxQ/VtRcwFU0z8DufkayU=; b=Se9L+Rr1lEJa71amnnzYTEyPYeA+/8nBD7WlRamJRLk98OPWgcooYec0LEp3u1G6y/ FES2tCAbuWZqC7Cfp2VUa54NjZTIoBAWhYUMcpwhMmN11CWK5NpDT/HWJfJWjnFfaaSe hee+oaMUF//4ezxgQ+PKOfPRdB7voCvCbABMOYSbboLjypKGyJcVVwExpIfQ7X38w1VL 5WnayJw9Ju4U1X/S0TsWziVBT3T0ONZuRRtiQ5iw9vAnvfMzky6tXjHuG1xejRR00fsv ILSgbXgKjJPq929Ysnqc43cT5kp/Apmef0yhnaRC6TY+qkt7JjQ+mt+UIpehpxlPTqpt xC2A== X-Gm-Message-State: ALKqPwdBvdL22jO77cATM0B4P1UIxFqAqmZ7qJgEeHNHCE3FLPzz1KQg lha8CRhKgxC0dVSCykXTxXo1qCrHzWdTT+g75/942Q== X-Google-Smtp-Source: ADUXVKIpRdCBiZCo8+lOiqvxt9wljFCmOedJ4OK0F10VP7Wts+w6o5U8v7btQIdbxx+VHFEt6P+5xXIX9PLz3vLbwfI= X-Received: by 2002:a25:aa04:: with SMTP id s4-v6mr9335898ybi.375.1528036063156; Sun, 03 Jun 2018 07:27:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nimrod Levy Date: Sun, 3 Jun 2018 10:27:29 -0400 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa Cc: Don Lewis , Pete French , eric@vangyzen.net, FreeBSD Stable Mailing List , Andriy Gapon , Peter Moody Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 03 Jun 2018 14:27:45 -0000 For my case, it's been a while since I fiddled with any thing. From memory, the last time I worked on this, I updated to the latest BIOS on the Asus prime b350+ leaving the settings we've talked about here at stock (c-states, memory clock, etc...), updated to 11-stable, and let things run for a while. This time around, I'm up for almost 3 weeks which is about what I've been getting, so I'm looking for a lockup soon. I think the last lockup I saw was a little different from before. In the past, the console went blank and unresponsive with the monitor showing no signal from the computer. The last time, the screen showed the normal output with a login prompt, but was otherwise unresponsive both on the console and from the network. On Sun, Jun 3, 2018 at 9:49 AM Mike Tancsa wrote: > On 6/2/2018 7:48 PM, Don Lewis wrote: > > On 2 Jun, Pete French wrote: > >> So,I notice that > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 was > >> closes as fixed. I cant remember if there was another bug report for > ongoing > >> Ryzen issues at all - I have been experimenting and have re-enabled > most of > >> the BIOS setting and tweaks fne, but I still need SMP disbled or it > >> locks up. Havent tried for a week or so with that, and maybe some > >> of the latest chnages in STABLE will help. is this fixed for > >> everyone else, or are you all stll running with SMP off ? > > > > With that bug fix, I get pretty much the same behavior on my Ryzen > > machine as on my AMD FX-8320E. BIOS settings are pretty much the just > > the defaults. I'm running 12.0-CURRENT, so I can't really comment on > > 11-STABLE. > > The compile bug has been fixed for me. However, last I checked I can > still freeze a system by generating a lot of network traffic between VMs > in either bhyve or virtbox. Its been a while since I tested (couple of > months) but I dont recall anything obviously committed that highlighted > that issue. Note this is on Epyc and Ryzen boxes > > ---Mike > > > -- > ------------------- > Mike Tancsa, tel +1 519 651 3400 x203 > Sentex Communications, mike@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada > _______________________________________________ > 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" >