On 2018-01-21, Base Pr1me <tlemery5...@gmail.com> wrote: > I'll try. Not sure I can keep it running long enough to get dmesg lol. Last > upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try > and get dmesg this week, when I have more time ... Or wait until newer > snaps and try again. > > On Jan 21, 2018 10:37, "Sebastien Marie" <sema...@online.fr> wrote: > >> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: >> > Anyone else's system hanging randomly after upgrading to yesterday's >> > snapshot? This isn't a panic that drops to ddb. It's just freezing with >> no >> > response to anything. >> >> A full dmesg would be welcome, and having the date of your previous >> version too. >> >> thanks. >> -- >> Sebastien Marie >> >
Moving back to a slightly older kernel and getting dmesg would be useful. If you have an working bsd.rd on the disk you can drop to a shell and mount the filesystems, save a copy of /var/run/dmesg.boot (interested to see any microcode-update related lines from the newer one). Here's a saved snapshot from a couple of weeks ago you could try: https://junkpile.org/bsd.mp.20180108.gz Hopefully that will be stable and you can then send a dmesg showing what's in the system.
