From owner-freebsd-stable@freebsd.org Fri Jan 19 20:48:46 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 206BBEC76CD for ; Fri, 19 Jan 2018 20:48:46 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 A73617472B for ; Fri, 19 Jan 2018 20:48:45 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x236.google.com with SMTP id s3so6985602qtb.10 for ; Fri, 19 Jan 2018 12:48:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hda3-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=shCRsPhBHK8+Gz47qRHB/WyC0+U/ShLb1Xla320wV14=; b=jRy9NS+IosZThr121Z2rETIGevPqR1UrXB6J3T3u0DPLmVk67F20r88cAIdmuPleEi +t7SYgZREcF15whnJqcyjv5OU9WkFEiTG5C7fXKk6vRjkvZmrhEf4BJ7WKwkhVXtEvN4 UDwvH6PRQqSv46s0/yy5kZUJUuBm/GPpsmjkPM9fAagFK+Rrn8p/Eo2oooBiMp6gT+EY tUhvGDHi9uqPwvo7hv3RpQ1o7IMpWoFR+DXO8r8i5ysrZBLvV4GXMHOove4Ltb3xS05y gXOxqfFAFOjW1+BO/3R+j8VYMPd1goUlk6sQ9husXZuj0HGbyKxcl+UFOuK/N4N3WCaU GtKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=shCRsPhBHK8+Gz47qRHB/WyC0+U/ShLb1Xla320wV14=; b=I5hnQIvefMI4Z4hWSPvlj8WKj5o62qUyGTszILgUv09OVINZ350o8xYQYOAiBI/wK9 aCyM9Sk7oEzbXT9X1ijk0M0PyJD7yVFJg2VCO4q02fTKuRdIpls1YZ4mrLgNHEla0RI0 tVaceRPI5iZd3Ze0q9D4VHjFiC/ZXn685+383Km4PWUB1jDIXLSGDCU6WBKE1vOD+yPK zIw9Ui/5sqKX9jxxB7xMxmsy3kcowtNGJp03MPkT3LMpi7mfUK4wHXtGHIQ2Vd4cyxmH pvQU+AW1s01+kT1qhusQabC20lrF0PrBBIFx4TqMrnnebqXMLJ55wn1nYCOmach5BSdq RFnw== X-Gm-Message-State: AKwxyterTpnMbBlBJVVlVpV22ZLJkqgMU002GOpzxdtxNibbfxBAlIde bwMiowePZ1/S7tpbQMDGMB6+Vl1sYnqCG9SCQ45flwTjG1s= X-Google-Smtp-Source: ACJfBotFKwX4hpxyrtKOHLRg0bkMc7ADcbX58rIp2m/siXtxMvrX9W+mE73nxdS34XDRUDlwI3CceffTDBLYCsTd/Sc= X-Received: by 10.200.4.19 with SMTP id v19mr30923875qtg.69.1516394924314; Fri, 19 Jan 2018 12:48:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Fri, 19 Jan 2018 12:48:23 -0800 (PST) In-Reply-To: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> From: Peter Moody Date: Fri, 19 Jan 2018 12:48:23 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Nimrod Levy , Don Lewis , freebsd-stable@freebsd.org, Pete French Content-Type: text/plain; charset="UTF-8" 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, 19 Jan 2018 20:48:46 -0000 On Fri, Jan 19, 2018 at 12:39 PM, Mike Tancsa wrote: > On 1/19/2018 3:32 PM, Peter Moody wrote: >> >> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about >> everything in all of these threads; disabling C state (no effect), >> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking >> voltage and cooling settings, rma'ing the board the cpu and the >> memory. nothing helped. >> >> last night I tried disabling SMT and, so far so good. > > > Is there anything that can be done to trigger the lockup more reliably ? > I havent found any patterns. I have had lockups with the system is 100% > idle and lockups when lightly loaded. I have yet to see any segfaults > or sig 11s while doing buildworld (make -j12 or make -j16 even) "reliably" trigger the lockup, no. The general pattern was high load followed by low load would lock up; so a couple 'make -j 32 buildworld' would almost always result in a lock up a few hours after the last one completes. weirdly enough though, with SMT enabled, building net/samba47 would always hang (like compilation segfaults). with SMT disabled, no such problems. > ---Mike >