Date: Mon, 22 Jan 2018 13:50:50 -0500 From: Mike Tancsa <mike@sentex.net> To: Peter Moody <freebsd@hda3.com> Cc: Don Lewis <truckman@freebsd.org>, Pete French <petefrench@ingresso.co.uk>, freebsd-stable@freebsd.org Subject: Re: Ryzen issues on FreeBSD ? Message-ID: <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> In-Reply-To: <CADbMJxkRR8s1=WWXP%2BH9eOHv_UWMQrUR=_E4aFw91VCeep82pw@mail.gmail.com> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@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> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <tkrat.8fa97919286143d7@FreeBSD.org> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <CADbMJxkRR8s1=WWXP%2BH9eOHv_UWMQrUR=_E4aFw91VCeep82pw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/22/2018 1:41 PM, Peter Moody wrote: > 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. hw.lower_amd64_sharedpage=1 is the default on AMD boxes no ? I didnt need to set mine to 1 > > shrug, I'm at a loss here. I am trying an RMA with AMD. ---Mike > > On Mon, Jan 22, 2018 at 10:32 AM, Mike Tancsa <mike@sentex.net> 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" > > -- ------------------- 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?343acf99-3e9e-093a-7390-c142396c2985>