From owner-freebsd-stable@freebsd.org Sun Jan 21 19:06:05 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 34A3DEB4E2E for ; Sun, 21 Jan 2018 19:06:05 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (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 E5BEE77B0D for ; Sun, 21 Jan 2018 19:06:04 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x22f.google.com with SMTP id s39so15788289qth.7 for ; Sun, 21 Jan 2018 11:06:04 -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=VRJABj1lr8fH57xoX8YeMLbR+v1cGVG6Dk5COsHxpb4=; b=stt3M7sa8eQBX0XFVANGulAcZHRQii36ReG7OaKDltb+r4etd28tO9g13AzIxouIw9 CXMAKQGsvBNcnlQJ2IC8/u+Dee7aITaNi2N50Ng+oNWz6/ViczMMRaM1JKpgobiyEwUH JRSuDc20Y07xVClgYSLqZqUO5yA1Q0lLGKH9qIOTxH61sbgjP0epc7eitJKBB+NfI9TD F5NArgxMDtPAepQvNBPllJ1pkAowHkyRTveajwuS+0kJBiM0Gla6Gfu83VV+BrO0UbEp BKjA0t7U6mjLqroBcgSJ82Daf1QsTtlOgGFUQP4ICwdgZq6C1k+j1LcCVkf/3ou+eYH6 Vd1Q== 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=VRJABj1lr8fH57xoX8YeMLbR+v1cGVG6Dk5COsHxpb4=; b=Y3lJ8uhfhIbu9UQU7mhlVkupBZ4wbxyUYni9QRUvmosvy8lEbLrzTEiU6fuhbusfwh GE2JmUT+hAUxSJ9zs309daWjZ4DmsyKDE3rNTgWKYuSuGnGvjov//1HGIOc216QKYrcp O+GFr8J2kPt8ZFuy2y7LVuOpLZQrMD88Y/V1ajh3j983+omLw+C22sLy3aBJo1Cjr4+8 2vLS+cw3tajZQECJkA20xks+XWBGBO8f9XUfOyhH63eigH/6n04ciMgWGNRABtPZFCEX XSaig9LznStEIjrtwmLsg1bs82XRb5h+KRo9VP8CfYoy+pN04FgrGzagRlqPNjY3AMYH xoCA== X-Gm-Message-State: AKwxytdXsx86viR1LKrD/kxtorB1c9BOQGWpsVbs2v/W4M9byG06QENz rA7PBSiQqLEmct1MRqo9p47bGItyqbvwc08WYbfYSg== X-Google-Smtp-Source: AH8x224XBAXFNfK8hFslZS9eBnMyCswlbO1YapSqbdTipBBkiQq+vo7V8NcZOygjfLo6rEJVgj/IVnl2D2xdBeOSsTw= X-Received: by 10.200.23.66 with SMTP id u2mr7459832qtk.294.1516561563730; Sun, 21 Jan 2018 11:06:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Sun, 21 Jan 2018 11:05:43 -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> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> From: Peter Moody Date: Sun, 21 Jan 2018 11:05:43 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Nimrod Levy Cc: Mike Tancsa , freebsd-stable@freebsd.org, Ryan Root 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: Sun, 21 Jan 2018 19:06:05 -0000 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. should I just RMA this beast again? On Sun, Jan 21, 2018 at 5:25 AM, Nimrod Levy wrote: > almost 2 days uptime with a lower memory clock. still holding my breath, > but this seems promising. > > > > On Fri, Jan 19, 2018 at 4:02 PM Nimrod Levy wrote: > >> I can try lowering my memory clock and see what happens. I'm a little >> skeptical because I have been able to run memtest with no errors for some >> time. I'm glad to give anything a try... >> >> >> On Fri, Jan 19, 2018 at 3:49 PM Mike Tancsa wrote: >> >>> On 1/19/2018 3:23 PM, Ryan Root wrote: >>> > This looks like the QVL list for your MB -> >>> > >>> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pdf >>> >>> Its an Asus MB, but the memory I have is in the above PDF list >>> >>> I dont see CT16G4DFD824A, but I do see other crucial products with >>> slower clock speeds. Right now I do have it set to 2133 where as it was >>> 2400 before. >>> >>> ---Mike >>> >>> >>> > >>> > >>> > On 1/19/2018 12:13 PM, Mike Tancsa wrote: >>> >> Drag :( I have mine disabled as well as lowering the RAM freq to 2100 >>> >> from 2400. For me the hangs are infrequent. Its only been a day and a >>> >> half, so not sure if its gone or I have been "lucky"... Either ways, >>> >> this platform feels way too fragile to deploy on anything :( >>> >> >>> >> ---Mike >>> >> >>> >> On 1/19/2018 3:08 PM, Nimrod Levy wrote: >>> >>> Looks like disabling the C- states in the bios didn't change >>> anything. >>> >>> >>> >>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy >> >>> > wrote: >>> >>> >>> >>> That looks promising. I just found that seeing in the bios and >>> >>> disabled it. I'll see how it runs. >>> >>> >>> >>> Thanks >>> >>> >>> >>> >>> >>> On Wed, Jan 17, 2018, 18:38 Don Lewis >> >>> > wrote: >>> >>> >>> >>> On 17 Jan, Nimrod Levy wrote: >>> >>> > I'm running 11-STABLE from 12/9. amdtemp works for me. It >>> >>> also has the >>> >>> > systl indicating that it it has the shared page fix. I'm >>> >>> pretty sure I've >>> >>> > seen the lockups since then. I'll update to the latest >>> STABLE >>> >>> and see >>> >>> > what happens. >>> >>> > >>> >>> > One weird thing about my experience is that if I keep >>> >>> something running >>> >>> > continuously like the distributed.net < >>> http://distributed.net> >>> >>> client on 6 of 12 possible threads, >>> >>> > it keeps the system up for MUCH longer than without. This >>> is >>> >>> a home server >>> >>> > and very lightly loaded (one could argue insanely >>> overpowered >>> >>> for the use >>> >>> > case). >>> >>> >>> >>> This sounds like the problem with the deep Cx states that has >>> been >>> >>> reported by numerous Linux users. I think some motherboard >>> >>> brands are >>> >>> more likely to have the problem. See: >>> >>> >>> http://forum.asrock.com/forum_posts.asp?TID=5963&title=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze >>> >>> >>> >>> -- >>> >>> >>> >>> -- >>> >>> Nimrod >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> >>> >>> -- >>> >>> Nimrod >>> >>> >>> >> >>> > >>> > >>> > _______________________________________________ >>> > 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" >>> > >>> > >>> >>> >>> -- >>> ------------------- >>> Mike Tancsa, tel +1 519 651 3400 <(519)%20651-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" >>> >> >> >> -- >> >> -- >> Nimrod >> > > > -- > > -- > Nimrod > _______________________________________________ > 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"