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 <free...@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 &
> now my only issue is crashes when I scrub my zfs pool, though I
> strongly suspect a dying disk is the cause of that.
> On Thu, Feb 1, 2018 at 10:51 AM, Mike Tancsa <m...@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
> >>> 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, m...@sentex.net
> > Providing Internet services since 1994 www.sentex.net
> > Cambridge, Ontario Canada
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"