Date: Tue, 23 Jan 2018 21:22:17 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Mike Tancsa <mike@sentex.net> Cc: Don Lewis <truckman@FreeBSD.org>, freebsd-stable@freebsd.org Subject: Re: Ryzen issues on FreeBSD ? Message-ID: <0cde9097-a454-a979-fac9-2d5b63a82759@FreeBSD.org> In-Reply-To: <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <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> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <tkrat.975666e9f483a6a0@FreeBSD.org> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23/01/2018 19:15, Mike Tancsa wrote: > On 1/22/2018 5:13 PM, Don Lewis wrote: >> On 22 Jan, Mike Tancsa wrote: >>> 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. >> >> Something else that you might want to try is 12.0-CURRENT. There might >> be some changes in HEAD that need to be merged back to 11.1-STABLE. > > > Temp works as expected now. However, a (similar?) hang building Samba47. > > ctrl+T shows If that works, then maybe you can get procstat -kk -a or a crash dump. Maybe this is not a hardware problem at all (or maybe it is). > load: 1.98 cmd: python2.7 53438 [usem] 54.70r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 > load: 0.34 cmd: python2.7 53438 [usem] 168.48r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 > load: 0.31 cmd: python2.7 53438 [usem] 174.12r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0cde9097-a454-a979-fac9-2d5b63a82759>