Date: Tue, 26 Jun 2018 15:42:28 +0100 From: Pete French <petefrench@ingresso.co.uk> To: Freddie Cash <fjwcash@gmail.com> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <df5d7696-2c60-cbf1-4301-61a2a6b4b5f5@ingresso.co.uk> In-Reply-To: <CAOjFWZ4Mz7f9HAi%2BLs8_Zh3AfgZoxuSs=WOJrXkFaZ5ZKOmgDQ@mail.gmail.com> References: <20180626112919.GK2430@kib.kiev.ua> <E1fXn8b-0000se-1B@dilbert.ingresso.co.uk> <CAOjFWZ4Mz7f9HAi%2BLs8_Zh3AfgZoxuSs=WOJrXkFaZ5ZKOmgDQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Gah! I my memory said it was /var/boot - so close :-) Thanks! On 26/06/2018 15:22, Freddie Cash wrote: > > > On Tue, Jun 26, 2018, 5:33 AM Pete French, <petefrench@ingresso.co.uk > <mailto:petefrench@ingresso.co.uk>> wrote: > > > > Also, please show the 100 first lines of the verbose boot dmesg > on this > > machine. > > the dmesg wraps around if I boot verbosely, but heres the contnets of > /var/log/messages from the time it starts to where it stops > talking about CPU specific stuff... if you need something else then > let me know - this is an easy machine to reboot and play about with. > > > /var/run/dmesg.boot is there for this various reason (dmesg buffer > rolling over). :) It's the dmesg output for the current boot. > > Cheers, > Freddie >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?df5d7696-2c60-cbf1-4301-61a2a6b4b5f5>