From owner-freebsd-arm@freebsd.org Sat Mar 4 21:47:44 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65A0DCF5E4F for ; Sat, 4 Mar 2017 21:47:44 +0000 (UTC) (envelope-from andrew@tao11.riddles.org.uk) Received: from lungold.riddles.org.uk (lungold.riddles.org.uk [82.68.208.19]) (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 19C2711D9 for ; Sat, 4 Mar 2017 21:47:43 +0000 (UTC) (envelope-from andrew@tao11.riddles.org.uk) Received: from [192.168.127.1] (port=13171 helo=caithnard.riddles.org.uk) by lungold.riddles.org.uk with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.88 (FreeBSD)) (envelope-from ) id 1ckHWe-0000PB-4O; Sat, 04 Mar 2017 21:47:40 +0000 Received: from localhost ([127.0.0.1]:34747 helo=caithnard.riddles.org.uk) by caithnard.riddles.org.uk with esmtp (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ckHWd-0002zF-7V; Sat, 04 Mar 2017 21:47:39 +0000 From: Andrew Gierth To: Warner Losh Cc: "freebsd-arm\@freebsd.org" Subject: Re: Is CPUTYPE=cortex-A7 supposed to work? In-Reply-To: (Warner Losh's message of "Sat, 4 Mar 2017 14:07:22 -0700") Message-ID: <87tw7820fc.fsf@news-spur.riddles.org.uk> References: <871suc3nv8.fsf@news-spur.riddles.org.uk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) Date: Sat, 04 Mar 2017 21:47:38 +0000 MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2017 21:47:44 -0000 >>>>> "Warner" == Warner Losh writes: >> Is building with CPUTYPE=cortex-A7 (this is on an RPI2) known to >> work, known to not work, or of unknown working status? Warner> I've not had good luck getting it to work. (cortex-a7 is the Warner> proper type name, btw). It kinda works, but ports are kinda Warner> wonky. My findings so far: 1. openssl speed (base system's openssl, not a port) produces a bunch of errors, such as: 542635024:error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01:/home/FreeBSD/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/rsa/rsa_pk1.c:103: 542635024:error:04067072:rsa routines:RSA_EAY_PUBLIC_DECRYPT:padding check failed:/home/FreeBSD/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/rsa/rsa_eay.c:705: 2. git fails with semi-random sha1 failures when cloning a repo of any size; these failures go away if you make it use its internal sha1 rather than the openssl one it defaults to. HOWEVER, testing in a world build without CPUTYPE and shoehorning the vectorized sha1 from openssl back in does not reproduce the failure. Also, extensive testing with "openssl dgst -sha1" did not produce any failure. (I've confirmed that both the above go away from recompiling without CPUTYPE.) I've also noticed some breakage probably not related to openssl for which I'm still waiting on recompilations in order to definitively test. -- Andrew.