Looks like disabling the C- states in the bios didn't change anything. On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy <nimr...@gmail.com> wrote:
> That looks promising. I just found that seeing in the bios and disabled > it. I'll see how it runs. > > Thanks > > > On Wed, Jan 17, 2018, 18:38 Don Lewis <truck...@freebsd.org> wrote: > >> On 17 Jan, Nimrod Levy wrote: >> > I'm running 11-STABLE from 12/9. amdtemp works for me. It also has the >> > systl indicating that it it has the shared page fix. I'm pretty sure >> I've >> > seen the lockups since then. I'll update to the latest STABLE and see >> > what happens. >> > >> > One weird thing about my experience is that if I keep something running >> > continuously like the distributed.net client on 6 of 12 possible >> threads, >> > it keeps the system up for MUCH longer than without. This is a home >> server >> > and very lightly loaded (one could argue insanely overpowered for the >> use >> > case). >> >> This sounds like the problem with the deep Cx states that has been >> reported by numerous Linux users. I think some motherboard brands are >> more likely to have the problem. See: >> >> http://forum.asrock.com/forum_posts.asp?TID=5963&title=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze >> >> -- > > -- > Nimrod > -- -- Nimrod _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
