From owner-freebsd-stable@FreeBSD.ORG Mon Dec 22 15:06:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53077404 for ; Mon, 22 Dec 2014 15:06:55 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2E75B83E for ; Mon, 22 Dec 2014 15:06:55 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 24857B9A8; Mon, 22 Dec 2014 10:06:54 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: CPUTYPEs includig avx are suspicious with clang in stable/10 Date: Mon, 22 Dec 2014 09:58:24 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <54944D08.8000202@omnilan.de> In-Reply-To: <54944D08.8000202@omnilan.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201412220958.24180.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 22 Dec 2014 10:06:54 -0500 (EST) Cc: Harry Schmalzbauer X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2014 15:06:55 -0000 On Friday, December 19, 2014 11:06:32 am Harry Schmalzbauer wrote: > I'm seeing sporadic problems (core dumps) with binaries compiled with > CPUTYPE=core-i-avx. > They run fine on IvyBridge, but fail on Haswells. > Stripping avx from MACHINE_CPU (by defining CPUTYPE=corei7 instead of > core-i-avx) solved all crashes on the haswell system. > > I have no idea if applications like pkg(8) make use of AVX, I'd bet they > don't do. So I guess it's something wrong with clang. > Unfortuantely I currently don't have a development installation on any > haswell system to provide some useful backtraces, but perhaps somebody > with compiler knowledge can have a look at this problem? If you are getting SIGILL (signal 4), all you really need is to get a core (even from a non-debug binary), then use gdb on the core and run 'x/i $rip' at the gdb prompt to see the instruction that triggered the fault. -- John Baldwin