From owner-freebsd-stable@freebsd.org Sun Jan 28 03:10:32 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 98790ED474B for ; Sun, 28 Jan 2018 03:10:32 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 36501682FE for ; Sun, 28 Jan 2018 03:10:32 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x234.google.com with SMTP id a27so8877140qtd.1 for ; Sat, 27 Jan 2018 19:10:32 -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=c4B8ynfDP4Fv5e1sHZ65WoQiHix+c8ubDK/r2NekE08=; b=qjV7r5ZVhLjPyLXyzRWQbHYpNHeITSm4VzzFITSJGSbLGvDxDTEWKwOTYbfMNOPGDn YFJPKXwrXOQT7NqX8L8fhjtk9TCAF363+wkTq23S+P9nOjEfAfi2xBmvL4ukaU+qr7Cb 8+CRH3TL3D4p4T/yHw7wdpaW5lVMIL2ox3uU5VU3hOE+GUlxZzI5kGCwE2IM8p9YYDRz Ew/PGa/udKdeJOGRwaJZJU98kHcVKJkdqGS/nsuaIbHpjR5UuJXuXcm+iFzJ4lx3I7po oone0t+1ah/uSHwJeSK0bLyo5tMGJmoatxAYS9OUReWe0ISXOfHrfiMf2AOdbs1EtI2C A9Ww== 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=c4B8ynfDP4Fv5e1sHZ65WoQiHix+c8ubDK/r2NekE08=; b=IeHlZUSeqq7gVavyNvuXd35i185LEz9+j/ZimtoZhmQYIjTx7tDir/Htpp47UdL3RA CoCf8QJwg2YIQMo4GkRjRzg6La6erqs1o0hW31K25A7zkenmZsRbLDEKQdq+6lZS0I6E LCFiChZXLScOixtyiSaAzhJESEETgj4ZbKtuVkvGLErG+JaMdXagGz8Ww3/EeKpkEuS4 sBMWJyCWo1uCaV/12Sbpor6beC1+Ei0iKPX90TAQFAem5fF2MCYP4/ThroenUDSgqkTN kvWPRhm4qTAZXK9ysIdWW0ekR6jxCOtCCYY42TPiMDk+hAk7qs03miEGS8izUL9MrtUs +mnA== X-Gm-Message-State: AKwxyterhcwAId6vduiIWrB5+9a27GCRrU7BrOVv6TtCm8jfd+Ccd6aw UTrOwD/M5IOQx2WcErqx1r7XmZzMIoa4zZKDxvz3Zw== X-Google-Smtp-Source: AH8x224r4j9rbvxIFVzQT2BFNx0y37ppflBSSrFBb1rEJZf3X71jvVl/4hOTOitLg6kEgRwIA8WykULbLb5j9WzQuCs= X-Received: by 10.237.38.71 with SMTP id z65mr30193032qtc.248.1517109031656; Sat, 27 Jan 2018 19:10:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Sat, 27 Jan 2018 19:10:31 -0800 (PST) Received: by 10.140.39.83 with HTTP; Sat, 27 Jan 2018 19:10:31 -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: Sat, 27 Jan 2018 19:10:31 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Nimrod Levy Cc: Mike Tancsa , FreeBSD-STABLE Mailing List , Ryan Root 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: Sun, 28 Jan 2018 03:10:32 -0000 On Jan 27, 2018 6:20 PM, "Nimrod Levy" wrote: I'm about ready to have a party. My Ryzen 5 1600 has been up for over 8 days so far after changing the memory to a slower speed. System load hovers around .3 I couldn't find an easy way to down-speed my memory in the bios :( On Sat, Jan 27, 2018 at 8:41 PM Peter Moody wrote: > Whelp, I replaced the r5 1600x with an r7 1700 (au 1734) and I'm now > getting minutes of uptime before I hard crash. With smt, without, with c > states, without, with opcache, without. No difference. > > I'm going to try a completely different motherboard next. I think Amazon > is starting to dislike me. > > On Jan 21, 2018 11:05 AM, "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. >> >> 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" >> > -- -- Nimrod