From owner-freebsd-stable@freebsd.org Mon Jan 22 18:42:01 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 114B8ECF1DC for ; Mon, 22 Jan 2018 18:42:01 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x244.google.com (mail-qt0-x244.google.com [IPv6:2607:f8b0:400d:c0d::244]) (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 CC7D768012 for ; Mon, 22 Jan 2018 18:42:00 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x244.google.com with SMTP id l20so22037066qtj.11 for ; Mon, 22 Jan 2018 10:42:00 -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=SIn8WSpdJcU/AlOR0cNScssHTvhvJi/NUCHSc/EPZl0=; b=KgLOAd+qXOogxaE3HNdkwWv1Ez+7BZHzpYvJCPbpBpY9f5tZqUgetmhJN3bmrIFzrF c566/OtphXS4HhO5ohSTKXg1qgETXUuawsLmvXime7ZqTTFx/wUdKuzbo7yR5TMDbh8f tvtRMbKOjzGr5fYUbKSia/VPfVlJhes1+3XeWZxqlTsTu8mN9j3RQ8vVhB2CLPrt2X0O EXsklbstkQNE4yn1kyCy/VmuXoA41z2uqX5zBEcuxau1VXfVmG0Rzih/6HJAt/bMvMuj XukUBGgVoJ2CIvqDqEN97T36dCqi1DsVnhM4QaKffuAB6BW2Fttxea0AJmrXC03ulh+Y M4kA== 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=SIn8WSpdJcU/AlOR0cNScssHTvhvJi/NUCHSc/EPZl0=; b=IB49BM+ChfchS2vjcMhTVMwXfjLBpJllc49eKP6ZOyJL1lfbpcp5bCHW1ShAdtnTrY uS6kKYV9krNwWCufW+oQt6J1CRIyuo2RDy71o0m4jBjte4WDDf1puDhFvvyCpWI/3rHZ PCZ+3+eIygad/PdJJrdg2YBpLcG/rSRZ2kVJNRMfc1RQXB89zOCJrWri9ANl7yvvm2sE BXD9Bvd6N1XE8hYBIq5mY8aPzl91yCpJtk27YP24pyEIVp7jW5gf5wSHM/VI9K/FbqwT HMQi5R80la0XN7Xi2j+4cXQTI7mNHaEezf7pKvu6E3diLtnc9l1smdapgZb7Tk693SWp 34tA== X-Gm-Message-State: AKwxytc8ZmIVvLaMVaUdvB+8vxjVXkOn3qhJlf5iXK8WmOY1IcOfQbsi XjOECeGxwrYocffEedCOockU9KHs6t2vZ8cyovHrXQ== X-Google-Smtp-Source: AH8x2249NhdlagUx+f3vw+QvWpClcHOY8kPYK08csK28kRTJMF0bRrfwkgv96Qe+Z/DBNfaO7XrzvKwOhUWytPU7kDE= X-Received: by 10.55.171.5 with SMTP id u5mr10532434qke.20.1516646519756; Mon, 22 Jan 2018 10:41:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Mon, 22 Jan 2018 10:41:39 -0800 (PST) In-Reply-To: <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> 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> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> From: Peter Moody Date: Mon, 22 Jan 2018 10:41:39 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Don Lewis , Pete French , freebsd-stable@freebsd.org 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: Mon, 22 Jan 2018 18:42:01 -0000 fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the hw.lower_amd64_sharedpage setting to my loader.conf and got a crash last night following the familiar high load -> idle. this was with SMT re-enabled. no crashdump, so it was the hard crash that I've been getting. all of the builds that had been failing before were fine; net/samba47, lang/ghc (though hadn't actually done this before to verify that it failed on my rig), so that's at least a plus. The only other out-of-the-ordinary thing I was doing at the time was that I'd started a zpool scrub. That succeeded fine the day before when SMT was disabled. shrug, I'm at a loss here. On Mon, Jan 22, 2018 at 10:32 AM, Mike Tancsa wrote: > On 1/22/2018 1:25 PM, Don Lewis wrote: >> On 22 Jan, Pete French wrote: >>> >>> >>> On 21/01/2018 19:05, Peter Moody wrote: >>>> hm, so i've got nearly 3 days of uptime with smt disabled. >>>> unfortunately this means that my otherwise '12' cores is actually only >>>> '6'. I'm also getting occasional segfaults compiling go programs. >>> >>> Isn't go known to have issues on BSD anyway though ? I have seen >>> complaints of random crashes running go under BSD systems - and >>> preseumably the go compiler itself is written in go, so those issues >>> might surface when compiling. >> >> Not that I'm aware of. I'm not a heavy go user on FreeBSD, but I don't >> recall any unexpected go crashes and I haven't seen problems building >> go on my older AMD machines. > > We use go quite a bit on one customer app and its quite stable. But > thats a FreeBSD RELENG_10 box on an intel chip. > > ---Mike > > > -- > ------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada http://www.tancsa.com/ > _______________________________________________ > 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"