From owner-freebsd-stable@freebsd.org  Fri Jul 27 10:58:07 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 AF285104661F
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri, 27 Jul 2018 10:58:07 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 548FC8F60D
 for <freebsd-stable@freebsd.org>; Fri, 27 Jul 2018 10:58:07 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 18FAC104661D; Fri, 27 Jul 2018 10:58:07 +0000 (UTC)
Delivered-To: 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 078F11046618
 for <stable@mailman.ysv.freebsd.org>; Fri, 27 Jul 2018 10:58:07 +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 A0BD98F60C
 for <stable@freebsd.org>; Fri, 27 Jul 2018 10:58:06 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk)
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>)
 id 1fj0Rf-0005JE-9h; Fri, 27 Jul 2018 10:58:03 +0000
Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91
 (FreeBSD)) (envelope-from <petefrench@ingresso.co.uk>)
 id 1fj0Rf-0000oI-5g; Fri, 27 Jul 2018 11:58:03 +0100
To: petefrench@ingresso.co.uk, stable@freebsd.org
Subject: Re: Linux binaries stopped working on latest stable ? - Only on
 Ryzen/Epyc
Message-Id: <E1fj0Rf-0000oI-5g@dilbert.ingresso.co.uk>
From: Pete French <petefrench@ingresso.co.uk>
Date: Fri, 27 Jul 2018 11:58:03 +0100
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: Fri, 27 Jul 2018 10:58:07 -0000

> Hmm, I gte a core dump trying to run any Linux binary at the moment (stable
> from Tuesday - r336665). I have remoed all packages and re-installed
> and running /compat/linux/bin/bash coredumps. Running ldd on it coredumps
> too, and gdb gets e nowhre.

I did a bit more testing on this. It only affects my Ryzen and Epyc
machines! I copied the OS from the box on my desk to an Intel chip
and it works fine there. Thats knd of upsetting! I did try applying the
sysctl settings that get enabled if Ryzen is detected, but that doesnt
make it crash on Intel.

Hmmm, will go follow this up in the Ryzen thread...

-pete.