I'm really glad to see that I'm not the only one still interested in this thread. I don't really have anything new to contribute. I've been getting about a week or so uptime out of my box. My habit has been to see if it hangs, then reboot and rebuild latest stable and reboot and run that for a while. Although now that this thread pops back up, I just realized it's been 2 weeks since the last cycle. I don't trust it yet, but I've seen clear improvement since this started. On Fri, Apr 20, 2018 at 7:18 AM Pete French <petefrench at ingresso.co.uk> wrote:> So, resurrecting the thread from a few weeks ago, as I finally found > time yesterday to out together the Ryzen machine I bought the parts for in > Jaunary (busy year at work....). All went smoothl;y, checked it > booted up, used it for 15 minutes, was impressed by the speed and went > home. > > ...and by the time I got home, an hour or so later, it had locked up hard. > > I was somewhat dissapointed, as I had seen various fixes go in,. and had > hoped > the issues were fixed. This morning I have booted the machine back up, > tweaking the BIOPS to do things mentioned in this thread, viz: > > Disable Turbo Boost > Disable SMT > Disable global C-states > > The memory was already ruunning correctly at 2133 (though I have locked > that > in the BIOS too) and I was already using kern.eventtimer.periodic=1, so > the lockup was not related to those. Its the latest BIOS, and a -STABLE > build from yesterday. > > I suspect it will now be stable, but I was wondering if anyone was any > further > forward on working out which of the settings above are the ones which 'fix' > the issue - or indeed if its really fixed, by them or just made far less > likely > to happen. > > Anyone got any more comments on this ? > > cheers, > > -pete. > _______________________________________________ > freebsd-stable at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >-- -- Nimrod
On 20/04/2018 12:48, Nimrod Levy wrote:> I'm really glad to see that I'm not the only one still interested in > this thread.? I don't really have anything new to contribute. I've been > getting about a week or so uptime out of my box. My habit has been to > see if it hangs, then reboot and rebuild latest stable and reboot and > run that for a while. Although now that this thread pops back up, I just > realized it's been 2 weeks since the last cycle. I don't trust it yet, > but I've seen clear improvement since this started.What setting sdo you have - just the ones I listed or some in the BSD setup itself ? I am surprised that the operson who said they were getting an actual Epyc server hasn't commented again on the thread. Hopefully that means it works fine on the server hardware :-) I have seen a few commits go through in STABLE related to VM which interest me, and which might cause hangs, so we shall see how it goes. Possibly looking at the Ryzen issue has flushed out a few VM problems anyway, which would be good, as more stbaility is always good (and I have a vague hope it might fix the mysetrious Go hangs too). -pete.
And of course now that we say something about it, I get a lockup overnight... -- Nimrod On Fri, Apr 20, 2018 at 7:48 AM Nimrod Levy <nimrodl at gmail.com> wrote:> I'm really glad to see that I'm not the only one still interested in this > thread. I don't really have anything new to contribute. I've been getting > about a week or so uptime out of my box. My habit has been to see if it > hangs, then reboot and rebuild latest stable and reboot and run that for a > while. Although now that this thread pops back up, I just realized it's > been 2 weeks since the last cycle. I don't trust it yet, but I've seen > clear improvement since this started. > > > On Fri, Apr 20, 2018 at 7:18 AM Pete French <petefrench at ingresso.co.uk> > wrote: > >> So, resurrecting the thread from a few weeks ago, as I finally found >> time yesterday to out together the Ryzen machine I bought the parts for in >> Jaunary (busy year at work....). All went smoothl;y, checked it >> booted up, used it for 15 minutes, was impressed by the speed and went >> home. >> >> ...and by the time I got home, an hour or so later, it had locked up hard. >> >> I was somewhat dissapointed, as I had seen various fixes go in,. and had >> hoped >> the issues were fixed. This morning I have booted the machine back up, >> tweaking the BIOPS to do things mentioned in this thread, viz: >> >> Disable Turbo Boost >> Disable SMT >> Disable global C-states >> >> The memory was already ruunning correctly at 2133 (though I have locked >> that >> in the BIOS too) and I was already using kern.eventtimer.periodic=1, so >> the lockup was not related to those. Its the latest BIOS, and a -STABLE >> build from yesterday. >> >> I suspect it will now be stable, but I was wondering if anyone was any >> further >> forward on working out which of the settings above are the ones which >> 'fix' >> the issue - or indeed if its really fixed, by them or just made far less >> likely >> to happen. >> >> Anyone got any more comments on this ? >> >> cheers, >> >> -pete. >> _______________________________________________ >> freebsd-stable at freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >> > -- > > -- > Nimrod >-- -- Nimrod