Date: Fri, 09 Feb 2018 11:42:59 +0000 From: Nimrod Levy <nimrodl@gmail.com> To: Peter Moody <freebsd@hda3.com> Cc: Mike Tancsa <mike@sentex.net>, Ed Maste <emaste@freebsd.org>, freebsd-stable stable <freebsd-stable@freebsd.org>, Don Lewis <truckman@freebsd.org>, Andriy Gapon <avg@freebsd.org>, Pete French <petefrench@ingresso.co.uk> Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <CAMgUhprrAYKDiDEAQuSLszR53rP-cUzvTcr-eF%2BxyY6E__vgOg@mail.gmail.com> In-Reply-To: <CADbMJx=xQ%2B73w7sjUS1KUy0cr9zmeashWD3tNwrmABf-2oNjbw@mail.gmail.com> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <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> <tkrat.ada77e0420783bed@FreeBSD.org> <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> <tkrat.e541d1b83f4f6c75@FreeBSD.org> <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net> <c0319297-d47d-449d-a6f1-2529d1d38541@sentex.net> <CAMgUhppdkcqYTpZEZJ1ScTevPOEK6WRXpg_WP-L-R6rKNhpYAA@mail.gmail.com> <ed1dd16e-0121-a578-23f0-1b3503d6475d@sentex.net> <CAPyFy2C33S8-=HR2Vv-hSVU5ewknskH7G0MxQ%2Bmvq_FNMfJgqA@mail.gmail.com> <38a14576-2dbd-a1ba-791c-197351d091c0@sentex.net> <f852ecc7-bbe3-5b7a-236c-52078ceaec46@sentex.net> <CADbMJx=xQ%2B73w7sjUS1KUy0cr9zmeashWD3tNwrmABf-2oNjbw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mine was running so well. I had almost 3 weeks of uptime before it locked up twice last night. On Thu, Feb 8, 2018 at 10:24 PM Peter Moody <freebsd@hda3.com> wrote: > to close the loop on this thread (for me at least); I replaced the > asrock ab350 with an msi x370 and things now, just work (c). the msi > detects the memory as 2133 (rather than the 3000 mhz it was sold as). > i'm not sure if this because it really is 2133 mhz, or because the msi > just likes that frequency better. i'm also not sure to what extent the > issue was fixed by the slower memory versus the different mobo brand & > chipset. > > now my only issue is crashes when I scrub my zfs pool, though I > strongly suspect a dying disk is the cause of that. > > Cheers, > peter > > > On Thu, Feb 1, 2018 at 10:51 AM, Mike Tancsa <mike@sentex.net> wrote: > > On 2/1/2018 1:49 PM, Mike Tancsa wrote: > >> On 2/1/2018 1:40 PM, Ed Maste wrote: > >>>> root@amdtestr12:/home/mdtancsa # procstat -kk 6067 > >>>> PID TID COMM TDNAME KSTACK > >>>> > >>>> 6067 100865 python2.7 - ??+0 ??+0 ??+0 > ??+0 > >>>> ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > >>> > >>> I think this part is due to the broken loader change in r328536. > >>> Kernel symbol loading is broken, and this in particular isn't related > >>> to Ryzen issues. > >> > >> Just for the archives, after a buildworld to a newer rev of the source > >> tree, all was good :) > > Ugh, to clarify, all was good with the procstat issue. > > > > ---Mike > > > > > > -- > > ------------------- > > Mike Tancsa, tel +1 519 651 3400 x203 <(519)%20651-3400> > > Sentex Communications, mike@sentex.net > > Providing Internet services since 1994 www.sentex.net > > Cambridge, Ontario Canada > -- -- Nimrod
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMgUhprrAYKDiDEAQuSLszR53rP-cUzvTcr-eF%2BxyY6E__vgOg>