Just to throw another datapoint out there, I've been running on my Asus
prime b350+ ryzen 5 and I've been stable since the microcode updates over
the summer. I believe I returned all the bios settings (cstates, memory
timing, etc..) back to stock. I've had to shutdown and relocate (and
reconfigure some networks bits) since then. I've also shifted to RELENG
11.2 from the STABLE code that I'd been running. It's been very stable
for
me with a current uptime of 60 days and before that, it was rebooted for an
update. So whatever was going on seems to be fixed for me.
On Tue, Dec 4, 2018 at 10:44 AM Pete French <petefrench at ingresso.co.uk>
wrote:
>
>
> On 04/12/2018 15:04, Mike Tancsa wrote:
> > Well, another lockup. This time after ~ 10 days of uptime. Box was
idle
> > at the time and just a solid freeze. This is an ASUS PRIME X370-PRO
> > running BIOS from 09/07/2018 (latest). Not sure if BIOS related or OS
> > related. I have another motherboard (MSI) that I will install 12.0 on
> > and see if its any different. There is also a micro code update from
> > AMD last week. However, there are no release notes as to what it
> > changes. I will hold off on that for now and see if I can get lockups
on
> > the MSI in the next week or two.
>
> I did the opposite yesterday - I updated my microcode to the latest one
> from MSI (though the AMD update it contains is from the summer I belive,
> depsite the BIOS only comming out a couple of weeks ago). Am running
> 12-STABLE on there, and will see how long it lasts.
>
> Only got to do this yesterday as havent been near the machine for weeks.
> I didnt adjust any RAM timings and left everything at the default after
> the BIOS update.
>
> but until yesterday it has locked up about every couple of days :-(
>
> -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"
>