From owner-freebsd-stable@freebsd.org  Mon Jul 30 11:43:28 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 580111053798
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Mon, 30 Jul 2018 11:43:28 +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 EE9A095684;
 Mon, 30 Jul 2018 11:43:27 +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 1fk6aC-0002Dl-7X; Mon, 30 Jul 2018 11:43:24 +0000
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: Mike Tancsa <mike@sentex.net>, Konstantin Belousov <kostikbel@gmail.com>
Cc: truckman@FreeBSD.org, eric@vangyzen.net, freebsd-stable@freebsd.org,
 freebsd@hda3.com, avg@freebsd.org
References: <20180705133542.GG5562@kib.kiev.ua>
 <E1fb4mD-0006j7-SY@dilbert.ingresso.co.uk>
 <20180705145130.GH5562@kib.kiev.ua>
 <548b493e-6a51-32ca-b3c1-216cac037e8b@ingresso.co.uk>
 <a05cc627-6359-6c9f-0f48-3e7b69f7d9e9@sentex.net>
 <9209d008-03dd-8613-3e6d-303eea8b80ef@ingresso.co.uk>
 <643509b6-511d-ba2b-3e0d-b38cd6607a25@sentex.net>
 <20180727143801.GF2394@kib.kiev.ua>
 <ae1ee1fd-cff4-1bb6-d671-62094970ea44@sentex.net>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <a0abb70f-4a33-16b7-e140-30e2d049dc96@ingresso.co.uk>
Date: Mon, 30 Jul 2018 12:43:24 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <ae1ee1fd-cff4-1bb6-d671-62094970ea44@sentex.net>
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.27
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: Mon, 30 Jul 2018 11:43:28 -0000


> I just brought everything upto date and re-tested and same issue.
> FreeBSD 11.2-STABLE #1 r336761
> 
> # mount | grep -v zfs
> devfs on /dev (devfs, local, multilabel)
> linprocfs on /compat/linux/proc (linprocfs, local)
> linsysfs on /compat/linux/sys (linsysfs, local)
> tmpfs on /compat/linux/dev/shm (tmpfs, local)
> 
> # /compat/linux/bin/bash
> Segmentation fault (core dumped)
> #
> 

I opened a bug report for this here:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230144

It definitely processor dependent (booting same drive on two different 
CPUs shows it up) and it does not happen on CURRENT. Very odd indeed!

-pete.