Date: Sat, 27 Jan 2018 19:10:31 -0800 From: Peter Moody <freebsd@hda3.com> To: Nimrod Levy <nimrodl@gmail.com> Cc: Mike Tancsa <mike@sentex.net>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Ryan Root <rroot@rootautomation.com> Subject: Re: Ryzen issues on FreeBSD ? Message-ID: <CADbMJxkx7=T3c1oaPnkARURQHoWL41m=6NbO8r327dAJq5BNAw@mail.gmail.com> In-Reply-To: <CAMgUhpqJ2bc5cvVzHt4nponnu6Ek294cvG-mWAsPm8Khk=OR5g@mail.gmail.com> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <tkrat.6d8f44d87e74fa14@FreeBSD.org> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <CAMgUhpr%2B5HeBi1MRegs=XoKpdHW8-i%2Bec0k-DNaL_pcN6PCPKw@mail.gmail.com> <tkrat.5ec856810e0c7ced@FreeBSD.org> <CAMgUhpqZyCOjqVhMCAi-b_JaKYtyfqDf0pOcX0LwV2dcTuusyg@mail.gmail.com> <CAMgUhpqpYpoi1bD9h_SYvh83g_Csky%2BqMkTsOYZ1zcHYxtMeHg@mail.gmail.com> <dd29d77a-deb9-423e-f9b8-cb07387bbfd5@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <a601973f-9205-8dd9-7f78-a7f03985ab4a@sentex.net> <CAMgUhpop3=J7TQimK2iHdGTc=hnTgCEZDqibDSRCyTPMWX5wJQ@mail.gmail.com> <CAMgUhpop54hJ%2Biq_VYYqrEHgSapmMu_GmOPaOsmhA=QbjPEZ5A@mail.gmail.com> <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC%2BD9fddENPiiFng@mail.gmail.com> <CADbMJx=Pu2w9oRxa2AofRVS-LpR9hmF6VV_Od=3r0BYWj4YFKg@mail.gmail.com> <CAMgUhpqJ2bc5cvVzHt4nponnu6Ek294cvG-mWAsPm8Khk=OR5g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 27, 2018 6:20 PM, "Nimrod Levy" <nimrodl@gmail.com> 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 <freebsd@hda3.com> 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" <freebsd@hda3.com> 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 <nimrodl@gmail.com> 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 <nimrodl@gmail.com> 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 <mike@sentex.net> 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 <nimrodl@gmail.com >> >>> >>> <mailto:nimrodl@gmail.com>> 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 <truckman@freebsd.org >> >>> >>> <mailto:truckman@freebsd.org>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADbMJxkx7=T3c1oaPnkARURQHoWL41m=6NbO8r327dAJq5BNAw>