From owner-freebsd-stable@freebsd.org  Tue Jun 26 14:42:32 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4857D102979A
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Tue, 26 Jun 2018 14:42:32 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E330C73600
 for <freebsd-stable@freebsd.org>; Tue, 26 Jun 2018 14:42:31 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6])
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>)
 id 1fXpAr-000Cgk-0L; Tue, 26 Jun 2018 14:42:29 +0000
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: Freddie Cash <fjwcash@gmail.com>
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
References: <20180626112919.GK2430@kib.kiev.ua>
 <E1fXn8b-0000se-1B@dilbert.ingresso.co.uk>
 <CAOjFWZ4Mz7f9HAi+Ls8_Zh3AfgZoxuSs=WOJrXkFaZ5ZKOmgDQ@mail.gmail.com>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <df5d7696-2c60-cbf1-4301-61a2a6b4b5f5@ingresso.co.uk>
Date: Tue, 26 Jun 2018 15:42:28 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CAOjFWZ4Mz7f9HAi+Ls8_Zh3AfgZoxuSs=WOJrXkFaZ5ZKOmgDQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2018 14:42:32 -0000

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
>