From owner-freebsd-mips@FreeBSD.ORG Mon Jun 24 11:06:49 2013 Return-Path: Delivered-To: freebsd-mips@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2880A14A for ; Mon, 24 Jun 2013 11:06:49 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 1B03A1DCC for ; Mon, 24 Jun 2013 11:06:49 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5OB6mEL001042 for ; Mon, 24 Jun 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5OB6m2a001040 for freebsd-mips@FreeBSD.org; Mon, 24 Jun 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Jun 2013 11:06:48 GMT Message-Id: <201306241106.r5OB6m2a001040@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-mips@FreeBSD.org Subject: Current problem reports assigned to freebsd-mips@FreeBSD.org X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jun 2013 11:06:49 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/178319 mips [patch] [arge] arge_stop() doesn't clean the tx ring p o kern/178318 mips [patch] [arge] if_arge/bootp race under some circunsta o kern/177876 mips [mips] kernel stack overflow panic on mips64, EdgeRout o kern/177832 mips [mips] [gpio] [patch] GPIO and RF LED do not function o kern/177032 mips [arge] arge1 fails to attach on UBNT Routerstation o kern/165951 mips [ar913x] [ath] DDR flush isn't being done for the WMAC p kern/163670 mips [mips][arge] arge can't allocate ring buffer on multip 7 problems total. From owner-freebsd-mips@FreeBSD.ORG Tue Jun 25 16:06:10 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 52456A0F; Tue, 25 Jun 2013 16:06:10 +0000 (UTC) (envelope-from lists@rewt.org.uk) Received: from hosted.mx.as41113.net (unknown [IPv6:2001:b70:201:2::22]) by mx1.freebsd.org (Postfix) with ESMTP id 9492F1626; Tue, 25 Jun 2013 16:06:09 +0000 (UTC) Received: from [172.16.9.23] (bella.stf.rewt.org.uk [91.208.177.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3bfsfv5sPLz2k; Tue, 25 Jun 2013 17:05:59 +0100 (BST) Message-ID: <51C9BFE6.20701@rewt.org.uk> Date: Tue, 25 Jun 2013 17:05:58 +0100 From: Joe Holden User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: "freebsd-mips@FreeBSD.org" Subject: AES-GCM/Hardware crypto for Octeon Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 16:06:10 -0000 Hi, Is the hardware crypto used by OpenCrypto/OpenSSL on the Octeon Plus range? Other than specifying cryptodev engine, is there a way to make sure that it's being used? Also, according to the Cavium product brief, the coprocessor supports AES-GCM, I can't work out if it's actually supported in OpenSSL as the patches seem to be geared towards Intel's hardware assisted variant - is this supportable on the current tree, or will it require extra patches/work (perhaps upstream?) Cheers, Joe From owner-freebsd-mips@FreeBSD.ORG Tue Jun 25 17:02:08 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 456EEA34 for ; Tue, 25 Jun 2013 17:02:08 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id C5441186D for ; Tue, 25 Jun 2013 17:02:07 +0000 (UTC) Received: by mail-la0-f44.google.com with SMTP id er20so12615059lab.17 for ; Tue, 25 Jun 2013 10:02:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=IXEFXVsk4g0vyMh28aH2ORsI/CdMLMyQnoyFNyGgAIU=; b=pEJL4JJ4zr+yzhiSzFGEH0iyEKcpi0El662bdN8i6+vmZ/yr6j/XJrU4kyci2eQLm0 b7OGZDsWdnN5Vcijs0MOmGbN0UJvYTl+45hOAYXgFBSfGlm/aigP7JnWrVvsC41CQ6yj jGtEb+EswwINc16HM25WZdaqRwMeaWyf4WfaRTB7poqvPsxfg1pa6HJ+K75pH2eTs+J4 GEP+A59EroqJoTU70CbFlY88ZTnaXiHXOeS037RCbigG5fHf38B6GUryW1YJ+Cr0pj0q L+An3YSm7T40dMUhGHsMTfO+Kc4fyqse4l9hOCjfPWwoO49bp46RarxsWQTf2B3dPN4L 9ivg== X-Received: by 10.152.2.201 with SMTP id 9mr13742776law.84.1372179726656; Tue, 25 Jun 2013 10:02:06 -0700 (PDT) MIME-Version: 1.0 Sender: juli@clockworksquid.com Received: by 10.152.113.231 with HTTP; Tue, 25 Jun 2013 10:01:45 -0700 (PDT) In-Reply-To: <51C9BFE6.20701@rewt.org.uk> References: <51C9BFE6.20701@rewt.org.uk> From: Juli Mallett Date: Tue, 25 Jun 2013 10:01:45 -0700 X-Google-Sender-Auth: TEwye1VwxbiDHLJqfCH25UtSUcc Message-ID: Subject: Re: AES-GCM/Hardware crypto for Octeon To: Joe Holden Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQk78Eb9EBOWVqUfH96CF5eymrCYIJdXc8cOj0Z5lYEyNxyPjMhmoh4Xym2mhEsh1mxLWdsV Cc: "freebsd-mips@FreeBSD.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 17:02:08 -0000 Rather than using a cryptodev, you can actually use the crypto coprocessor from userland. I remember looking at AES-GCM once, and I think it includes some instructions or coprocessor features that make implementing GCM easier, but it's not like the hardware will directly do AES in Galois Counter Mode for you. I could be misremembering. If you look at the cvmx-asm.h file in sys/contrib/octeon-sdk you can see what the interfaces for crypto offload are like, and you can see (somewhat convoluted) sample code using them in sys/mips/cavium/cryptocteon. There are patches to OpenSSL to use the crypto coprocessor directly, but they're certainly not in our tree, and I don't think there's a version of OpenSSL that ships with them. Are you just wanting AES-GCM to go faster across the whole OS, with SSH, etc., or do you have a specialized application that you want it for? If the latter, I'd encourage you to consider getting someone to throw together code to use the crypto coprocessor that's tailored to your application. Thanks, Juli. On Tue, Jun 25, 2013 at 9:05 AM, Joe Holden wrote: > Hi, > > Is the hardware crypto used by OpenCrypto/OpenSSL on the Octeon Plus range? > Other than specifying cryptodev engine, is there a way to make sure that > it's being used? > > Also, according to the Cavium product brief, the coprocessor supports > AES-GCM, I can't work out if it's actually supported in OpenSSL as the > patches seem to be geared towards Intel's hardware assisted variant - is > this supportable on the current tree, or will it require extra patches/work > (perhaps upstream?) > > Cheers, > Joe From owner-freebsd-mips@FreeBSD.ORG Tue Jun 25 17:25:24 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7E257F69 for ; Tue, 25 Jun 2013 17:25:24 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by mx1.freebsd.org (Postfix) with ESMTP id 524611977 for ; Tue, 25 Jun 2013 17:25:24 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id 10so29270696ied.28 for ; Tue, 25 Jun 2013 10:25:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=4KOl/KpkSI2r0BmQ9QkzPAErbzaDSNblLRdiwjmuuT8=; b=TI5phf5XBDOw5s4M7R/Vvx6lWpLJDe5FxFVckHrmDLdFwvQtq670eZGUBW9NDZ5usi ySGCbN58qrST1xvmOwhnl9F9GEd6dSxGssMtg2YCzBxfX6Zh5JeOViselFKpgYnDLsMC 4hFrA4UZUQOz2Pn7He+qfuX7EITwZyvNd9h4Id+cMtlu3GhTph46zXPVvBhXYoRz48cI KUmkI/mXsO4MqC7Z63QnmPMKZWOxZpZrKossRFGVYVxwW/ElZfPRnBbaxuAYZ1TRv72T HgOrYB1b+rDQtsS7TmpjqUdMdvCsdS1nGm5bWhKgdpg3UIMPlsvq8DDUqKmxlrpVmwBE zX3Q== X-Received: by 10.50.131.137 with SMTP id om9mr9290365igb.1.1372181123724; Tue, 25 Jun 2013 10:25:23 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id z15sm2322903igp.0.2013.06.25.10.25.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Jun 2013 10:25:22 -0700 (PDT) Sender: Warner Losh Subject: Re: AES-GCM/Hardware crypto for Octeon Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <51C9BFE6.20701@rewt.org.uk> Date: Tue, 25 Jun 2013 11:25:16 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <51C9BFE6.20701@rewt.org.uk> To: Joe Holden X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQlPhxluIyahEL/L29VK21VFnMXRthyhzQU+t+uc0FL+7BeMPVJuvock9vwC+BTrgsAyGfE+ Cc: "freebsd-mips@FreeBSD.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 17:25:24 -0000 On Jun 25, 2013, at 10:05 AM, Joe Holden wrote: > Hi, >=20 > Is the hardware crypto used by OpenCrypto/OpenSSL on the Octeon Plus = range? Other than specifying cryptodev engine, is there a way to make = sure that it's being used? >=20 > Also, according to the Cavium product brief, the coprocessor supports = AES-GCM, I can't work out if it's actually supported in OpenSSL as the = patches seem to be geared towards Intel's hardware assisted variant - is = this supportable on the current tree, or will it require extra = patches/work (perhaps upstream?) The Cavium crypto support is done as part of the open crypto framework. = OpenSSL uses the open crypto framework to offload crypto calculations. = The cavium coprocessor is used inside the open crypto framework in the = kernel. It isn't used like intel's AES instructions in userland. Looking at the code, it appears we'd support using the Cavium = Coprocessor in user space. However, a quick peek at the OpenSSL code in = the tree today suggests that the MIPS optimized versions of the various = crypto functions don't use the cavium coprocessor. I believe Cavium has patches to OpenSSL available on their cnusers.org = web site that could be used to update the code in the FreeBSD tree, but = I haven't looked closely lately at that stuff since the opencrypto = support is plenty fast for my needs. Warner From owner-freebsd-mips@FreeBSD.ORG Tue Jun 25 19:54:22 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B6FF0F22; Tue, 25 Jun 2013 19:54:22 +0000 (UTC) (envelope-from lists@rewt.org.uk) Received: from hosted.mx.as41113.net (hosted.mx.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id 182C11170; Tue, 25 Jun 2013 19:54:22 +0000 (UTC) Received: from [172.16.9.23] (bella.stf.rewt.org.uk [91.208.177.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3bfykM2vZlz4K; Tue, 25 Jun 2013 20:54:19 +0100 (BST) Message-ID: <51C9F56A.5070401@rewt.org.uk> Date: Tue, 25 Jun 2013 20:54:18 +0100 From: Joe Holden User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Juli Mallett Subject: Re: AES-GCM/Hardware crypto for Octeon References: <51C9BFE6.20701@rewt.org.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "freebsd-mips@FreeBSD.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 19:54:22 -0000 Juli Mallett wrote: > Rather than using a cryptodev, you can actually use the crypto > coprocessor from userland. I remember looking at AES-GCM once, and I > think it includes some instructions or coprocessor features that make > implementing GCM easier, but it's not like the hardware will directly > do AES in Galois Counter Mode for you. I could be misremembering. > > If you look at the cvmx-asm.h file in sys/contrib/octeon-sdk you can > see what the interfaces for crypto offload are like, and you can see > (somewhat convoluted) sample code using them in > sys/mips/cavium/cryptocteon. There are patches to OpenSSL to use the > crypto coprocessor directly, but they're certainly not in our tree, > and I don't think there's a version of OpenSSL that ships with them. > > Are you just wanting AES-GCM to go faster across the whole OS, with > SSH, etc., or do you have a specialized application that you want it > for? If the latter, I'd encourage you to consider getting someone to > throw together code to use the crypto coprocessor that's tailored to > your application. > Well, at present I can't see the hardware crypto being used, even with -engine cryptodev, unless the coprocessor is slower than a 1.8ghz atom for RC4 (which Cavium seem to indicate is supported by their SSL stuff, the product brief isn't specific though, http://www.cavium.com/css_ssl_sof_stk.html). Unless of course support for these isn't included in the GPL sdk, which wouldn't surprise me. In particular I was after support for openvpn, which should support the same ciphers as openssl supports - but openssl doesn't use the hardware for aes-gcm as you say. I'm going off the product brief which says: • Support for IPsec, SSL, DH, SRTP, WLAN security, DES, 3DES, AES (up to 256-bit including GCM), SHA1, SHA-2 up to SHA-512, RSA, ECC, KASUMI, and Data-at-rest security (AES-XTS) which would imply that AES-GCM is supported in hardware but again isn't specific as to what is actually done in hardware and what is just a partial helper. WRT RC4, the output I've got from openssl speed don't quite tally with what I'd expect: erl2# openssl speed -engine cryptodev: type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes rc4 17156.32k 21248.94k 22636.75k 23062.56k 23180.05k same on an atom minus cryptodev: type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes rc4 66027.12k 84307.30k 90219.81k 92061.93k 92585.39k The things I'd expect to be faster are much, much faster, eg aes-128-cbc, I also see similar for SHA1 et al, which is specifically supported by their SSL stuff. I'm not clued up with what is/isn't supported by the GPL sdk though. Looking at the code for cryptoctean, would registering other supported methods do the trick, or does it require extra code to actually work? Thanks, Joe > Thanks, > Juli. > > On Tue, Jun 25, 2013 at 9:05 AM, Joe Holden wrote: >> Hi, >> >> Is the hardware crypto used by OpenCrypto/OpenSSL on the Octeon Plus range? >> Other than specifying cryptodev engine, is there a way to make sure that >> it's being used? >> >> Also, according to the Cavium product brief, the coprocessor supports >> AES-GCM, I can't work out if it's actually supported in OpenSSL as the >> patches seem to be geared towards Intel's hardware assisted variant - is >> this supportable on the current tree, or will it require extra patches/work >> (perhaps upstream?) >> >> Cheers, >> Joe From owner-freebsd-mips@FreeBSD.ORG Tue Jun 25 20:04:43 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D3511646 for ; Tue, 25 Jun 2013 20:04:43 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) by mx1.freebsd.org (Postfix) with ESMTP id 5CF051220 for ; Tue, 25 Jun 2013 20:04:43 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id o10so1093580lbi.25 for ; Tue, 25 Jun 2013 13:04:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=rbvYeOE/M89Nqwue8PnGCE9ZX8C+tIikTsR4atk3DMg=; b=mUHi/5LhUKfY0vhN/9wYN/bkX97DL2k1Gw8AYGiniwVczsixx1Sb8qn9vNRuwBivr4 elbzauDh5IZ4gGEKZuaadaFnqiVLSSRTiqkAesjW+7MsZeDfnnCRBalYu5IzKwhEAIr8 axWVdRNmxfFc+wK3rzJqyOziqbQxH3UOupnyEkOKf6or51fANaGcWe619FG08O4cLcuv b9JEnjEN8oinuZrGKRkSv9bOBfaIVZCUNUegXGjkx70X0oHn92M+X4TiT9M2Yv+dUxi6 1Xs4dlxHn81/qG+PDBzCV6+TxQP+14wzP+omjt4487zA39sQmfPPjN8Z6Aa1nJxsmBLb uyXQ== X-Received: by 10.112.52.97 with SMTP id s1mr663653lbo.8.1372190682016; Tue, 25 Jun 2013 13:04:42 -0700 (PDT) MIME-Version: 1.0 Sender: juli@clockworksquid.com Received: by 10.152.113.231 with HTTP; Tue, 25 Jun 2013 13:04:21 -0700 (PDT) In-Reply-To: <51C9F56A.5070401@rewt.org.uk> References: <51C9BFE6.20701@rewt.org.uk> <51C9F56A.5070401@rewt.org.uk> From: Juli Mallett Date: Tue, 25 Jun 2013 13:04:21 -0700 X-Google-Sender-Auth: KZGsSNl8Mgk9kLaNLbik6RwpB9M Message-ID: Subject: Re: AES-GCM/Hardware crypto for Octeon To: Joe Holden Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlpEmDlZ+xp80fyF16csfYppcK1xAxKCrW2CsK2qYX47n3Qfd9dZ6LkSbKYoi2+wsUMzgMK Cc: "freebsd-mips@FreeBSD.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 20:04:43 -0000 On Tue, Jun 25, 2013 at 12:54 PM, Joe Holden wrote: > Juli Mallett wrote: >> >> Rather than using a cryptodev, you can actually use the crypto >> coprocessor from userland. I remember looking at AES-GCM once, and I >> think it includes some instructions or coprocessor features that make >> implementing GCM easier, but it's not like the hardware will directly >> do AES in Galois Counter Mode for you. I could be misremembering. >> >> If you look at the cvmx-asm.h file in sys/contrib/octeon-sdk you can >> see what the interfaces for crypto offload are like, and you can see >> (somewhat convoluted) sample code using them in >> sys/mips/cavium/cryptocteon. There are patches to OpenSSL to use the >> crypto coprocessor directly, but they're certainly not in our tree, >> and I don't think there's a version of OpenSSL that ships with them. >> >> Are you just wanting AES-GCM to go faster across the whole OS, with >> SSH, etc., or do you have a specialized application that you want it >> for? If the latter, I'd encourage you to consider getting someone to >> throw together code to use the crypto coprocessor that's tailored to >> your application. >> > Well, at present I can't see the hardware crypto being used, even with > -engine cryptodev, unless the coprocessor is slower than a 1.8ghz atom fo= r > RC4 (which Cavium seem to indicate is supported by their SSL stuff, the > product brief isn't specific though, > http://www.cavium.com/css_ssl_sof_stk.html). We only have offload support in kernel for block ciphers and hashes, not RC= 4. > Unless of course support for > these isn't included in the GPL sdk, which wouldn't surprise me. You're buying Cavium's marketing a little too much :) The cnusers SDK includes everything needed to access (very nearly) all of the offload features, but it provides very primitive interfaces to do so. For kernel support, Cavium doesn't provide anything; we're currently using modified drivers from the Linux OCF port which make use of those primitive interfaces. Adding support for others is fairly easy. Cavium does provide a modified OpenSSL that's not part of the cnusers distribution, but it doesn't do anything special or exciting; anyone who has written crypto code could bang out an OpenSSL engine for Octeon in a week. Doing something one-off that's specific to an application is even easier. > In particular I was after support for openvpn, which should support the s= ame > ciphers as openssl supports - but openssl doesn't use the hardware for > aes-gcm as you say. I'm going off the product brief which says: > > =E2=80=A2 Support for IPsec, SSL, DH, SRTP, WLAN security, > DES, 3DES, AES (up to 256-bit including GCM), > SHA1, SHA-2 up to SHA-512, RSA, ECC, KASUMI, > and Data-at-rest security (AES-XTS) > > which would imply that AES-GCM is supported in hardware but again isn't > specific as to what is actually done in hardware and what is just a parti= al > helper. Look at Mikrotik's patches to OpenVPN. I recall there being some trivial things around Octeon offload in their OpenSSL or their OpenVPN, but I can't recall right now. > WRT RC4, the output I've got from openssl speed don't quite tally with wh= at > I'd expect: > > erl2# openssl speed -engine cryptodev: > type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 > bytes > rc4 17156.32k 21248.94k 22636.75k 23062.56k 23180.0= 5k > > same on an atom minus cryptodev: > type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 > bytes > rc4 66027.12k 84307.30k 90219.81k 92061.93k 92585.3= 9k > > The things I'd expect to be faster are much, much faster, eg aes-128-cbc,= I > also see similar for SHA1 et al, which is specifically supported by their > SSL stuff. I'm not clued up with what is/isn't supported by the GPL sdk > though. Again, the "GPL sdk" (which isn't GPL'd) has nothing to do with this really. Even if Cavium's OpenSSL is available under a license we can use (and I think it isn't, but I've never looked seriously), the changes were added fairly invasively, and one would nearly be better off doing a from-scratch implementation anyway. > Looking at the code for cryptoctean, would registering other supported > methods do the trick, or does it require extra code to actually work? It requires actual implementation of the required offload support. You could reach out to the ocf-linux-users mailing list or David McCullough directly to see if there's patches to the cryptocteon code to add RC4 support. I'm sure someone else has done it already, but whether they're interested in sharing their sources is likely a different question. Thanks, Juli. From owner-freebsd-mips@FreeBSD.ORG Tue Jun 25 23:55:48 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 77F1BC1D; Tue, 25 Jun 2013 23:55:48 +0000 (UTC) (envelope-from lists@rewt.org.uk) Received: from hosted.mx.as41113.net (hosted.mx.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id 7C7881D01; Tue, 25 Jun 2013 23:55:47 +0000 (UTC) Received: from [172.16.9.23] (bella.stf.rewt.org.uk [91.208.177.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3bg44x6T53z6C; Wed, 26 Jun 2013 00:55:45 +0100 (BST) Message-ID: <51CA2E01.9070908@rewt.org.uk> Date: Wed, 26 Jun 2013 00:55:45 +0100 From: Joe Holden User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Juli Mallett Subject: Re: AES-GCM/Hardware crypto for Octeon References: <51C9BFE6.20701@rewt.org.uk> <51C9F56A.5070401@rewt.org.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "freebsd-mips@FreeBSD.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 23:55:48 -0000 Juli Mallett wrote: > On Tue, Jun 25, 2013 at 12:54 PM, Joe Holden wrote: >> Juli Mallett wrote: >>> Rather than using a cryptodev, you can actually use the crypto >>> coprocessor from userland. I remember looking at AES-GCM once, and I >>> think it includes some instructions or coprocessor features that make >>> implementing GCM easier, but it's not like the hardware will directly >>> do AES in Galois Counter Mode for you. I could be misremembering. >>> >>> If you look at the cvmx-asm.h file in sys/contrib/octeon-sdk you can >>> see what the interfaces for crypto offload are like, and you can see >>> (somewhat convoluted) sample code using them in >>> sys/mips/cavium/cryptocteon. There are patches to OpenSSL to use the >>> crypto coprocessor directly, but they're certainly not in our tree, >>> and I don't think there's a version of OpenSSL that ships with them. >>> >>> Are you just wanting AES-GCM to go faster across the whole OS, with >>> SSH, etc., or do you have a specialized application that you want it >>> for? If the latter, I'd encourage you to consider getting someone to >>> throw together code to use the crypto coprocessor that's tailored to >>> your application. >>> >> Well, at present I can't see the hardware crypto being used, even with >> -engine cryptodev, unless the coprocessor is slower than a 1.8ghz atom for >> RC4 (which Cavium seem to indicate is supported by their SSL stuff, the >> product brief isn't specific though, >> http://www.cavium.com/css_ssl_sof_stk.html). > > We only have offload support in kernel for block ciphers and hashes, not RC4. > That explains that then! >> Unless of course support for >> these isn't included in the GPL sdk, which wouldn't surprise me. > > You're buying Cavium's marketing a little too much :) The cnusers SDK > includes everything needed to access (very nearly) all of the offload > features, but it provides very primitive interfaces to do so. For > kernel support, Cavium doesn't provide anything; we're currently using > modified drivers from the Linux OCF port which make use of those > primitive interfaces. Adding support for others is fairly easy. > Cavium does provide a modified OpenSSL that's not part of the cnusers > distribution, but it doesn't do anything special or exciting; anyone > who has written crypto code could bang out an OpenSSL engine for > Octeon in a week. Doing something one-off that's specific to an > application is even easier. > Someone lead me to believe the sdk was licensed as such, but it appears to actually be a 3-clause license - even better :) I've approached a few people about doing some work on it, but they aren't versed enough in either FreeBSD or crypto to actually achieve the (ideal) goal of having the full functionality available via cryptodev. >> In particular I was after support for openvpn, which should support the same >> ciphers as openssl supports - but openssl doesn't use the hardware for >> aes-gcm as you say. I'm going off the product brief which says: >> >> • Support for IPsec, SSL, DH, SRTP, WLAN security, >> DES, 3DES, AES (up to 256-bit including GCM), >> SHA1, SHA-2 up to SHA-512, RSA, ECC, KASUMI, >> and Data-at-rest security (AES-XTS) >> >> which would imply that AES-GCM is supported in hardware but again isn't >> specific as to what is actually done in hardware and what is just a partial >> helper. > > Look at Mikrotik's patches to OpenVPN. I recall there being some > trivial things around Octeon offload in their OpenSSL or their > OpenVPN, but I can't recall right now. > Will have a look at those, I wasn't aware Mikrotik were using any Octeon hardware, cheers. >> WRT RC4, the output I've got from openssl speed don't quite tally with what >> I'd expect: >> >> erl2# openssl speed -engine cryptodev: >> type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 >> bytes >> rc4 17156.32k 21248.94k 22636.75k 23062.56k 23180.05k >> >> same on an atom minus cryptodev: >> type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 >> bytes >> rc4 66027.12k 84307.30k 90219.81k 92061.93k 92585.39k >> >> The things I'd expect to be faster are much, much faster, eg aes-128-cbc, I >> also see similar for SHA1 et al, which is specifically supported by their >> SSL stuff. I'm not clued up with what is/isn't supported by the GPL sdk >> though. > > Again, the "GPL sdk" (which isn't GPL'd) has nothing to do with this > really. Even if Cavium's OpenSSL is available under a license we can > use (and I think it isn't, but I've never looked seriously), the > changes were added fairly invasively, and one would nearly be better > off doing a from-scratch implementation anyway. > Functionality avaialble via cryptodev would negate this requirement, right? The lack of /dev/crypto on Linux probably contributed to them doing it like that? >> Looking at the code for cryptoctean, would registering other supported >> methods do the trick, or does it require extra code to actually work? > > It requires actual implementation of the required offload support. > You could reach out to the ocf-linux-users mailing list or David > McCullough directly to see if there's patches to the cryptocteon code > to add RC4 support. I'm sure someone else has done it already, but > whether they're interested in sharing their sources is likely a > different question. I need to double check EdgeOS, but I'd be surprised if they don't have RC4 support, especially considering the application for PPTP etc (which is why I have been playing with it for some applications, MPPE would benefit from it) > > Thanks, > Juli. Cheers, Joe From owner-freebsd-mips@FreeBSD.ORG Tue Jun 25 23:57:17 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E2B03C58 for ; Tue, 25 Jun 2013 23:57:17 +0000 (UTC) (envelope-from lists@rewt.org.uk) Received: from hosted.mx.as41113.net (hosted.mx.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id AFE731D10 for ; Tue, 25 Jun 2013 23:57:17 +0000 (UTC) Received: from [172.16.9.23] (bella.stf.rewt.org.uk [91.208.177.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3bg46h5VjVz6F; Wed, 26 Jun 2013 00:57:16 +0100 (BST) Message-ID: <51CA2E5C.3010709@rewt.org.uk> Date: Wed, 26 Jun 2013 00:57:16 +0100 From: Joe Holden User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Warner Losh Subject: Re: AES-GCM/Hardware crypto for Octeon References: <51C9BFE6.20701@rewt.org.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-mips@FreeBSD.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 23:57:18 -0000 Warner Losh wrote: > On Jun 25, 2013, at 10:05 AM, Joe Holden wrote: > >> Hi, >> >> Is the hardware crypto used by OpenCrypto/OpenSSL on the Octeon Plus range? Other than specifying cryptodev engine, is there a way to make sure that it's being used? >> >> Also, according to the Cavium product brief, the coprocessor supports AES-GCM, I can't work out if it's actually supported in OpenSSL as the patches seem to be geared towards Intel's hardware assisted variant - is this supportable on the current tree, or will it require extra patches/work (perhaps upstream?) > > The Cavium crypto support is done as part of the open crypto framework. OpenSSL uses the open crypto framework to offload crypto calculations. The cavium coprocessor is used inside the open crypto framework in the kernel. It isn't used like intel's AES instructions in userland. > > Looking at the code, it appears we'd support using the Cavium Coprocessor in user space. However, a quick peek at the OpenSSL code in the tree today suggests that the MIPS optimized versions of the various crypto functions don't use the cavium coprocessor. > > I believe Cavium has patches to OpenSSL available on their cnusers.org web site that could be used to update the code in the FreeBSD tree, but I haven't looked closely lately at that stuff since the opencrypto support is plenty fast for my needs. > > Warner > I'll have to look at that, I registered a while ago but haven't perused their code yet. Thanks, Joe From owner-freebsd-mips@FreeBSD.ORG Wed Jun 26 12:07:10 2013 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 96DF2684 for ; Wed, 26 Jun 2013 12:07:10 +0000 (UTC) (envelope-from user@atena.prefo.pl) Received: from atena.prefo.pl (atena.prefo.pl [188.165.80.169]) by mx1.freebsd.org (Postfix) with ESMTP id 66FE211C5 for ; Wed, 26 Jun 2013 12:07:10 +0000 (UTC) Received: by atena.prefo.pl (Postfix, from userid 10025) id 63C9D1C22554; Wed, 26 Jun 2013 13:44:29 +0200 (CEST) To: freebsd-mips@freebsd.org Subject: =?utf-8?B?Xw==?= X-PHP-Originating-Script: 10025:actives.php From: =?utf-8?B?0JDQu9C10LrRgdCw0L3QtNGAICjRgdC70YPQttCx0LAg0YDQsNGB0L/RgNC+0YHRgtGA0LDQvdC10L3QuNGPINC+0LHRitGP0LLQu9C10L3QuNC5?= Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Date: Wed, 26 Jun 2013 13:44:29 +0200 (CEST) X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2013 12:07:10 -0000 Здравствуйте Меня зовут Александр. Я занимаюсь электронными рассылками. Предлагаю прорекламировать Ваше рекламное объявление по любой необходимой базе данных. Если Вам интересно - будет сформирована базу данных возможных потенциальных клиентов. Если это возможно - сообщите пожалуйста Ваш Ваш телефон или skype, я расскажу о рассылке подробнее. Заранее благодарен за ответ, Александр. From owner-freebsd-mips@FreeBSD.ORG Thu Jun 27 13:52:41 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D87B8175; Thu, 27 Jun 2013 13:52:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 97D7916C3; Thu, 27 Jun 2013 13:52:41 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r5RDqc9r044080; Thu, 27 Jun 2013 13:52:38 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r5RDqcRk044079; Thu, 27 Jun 2013 13:52:38 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 Jun 2013 13:52:38 GMT Message-Id: <201306271352.r5RDqcRk044079@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 13:52:41 -0000 TB --- 2013-06-27 12:35:43 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-06-27 12:35:43 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-06-27 12:35:43 - starting RELENG_9 tinderbox run for mips/mips TB --- 2013-06-27 12:35:43 - cleaning the object tree TB --- 2013-06-27 12:35:43 - /usr/local/bin/svn stat /src TB --- 2013-06-27 12:36:09 - At svn revision 252301 TB --- 2013-06-27 12:36:10 - building world TB --- 2013-06-27 12:36:10 - CROSS_BUILD_TESTING=YES TB --- 2013-06-27 12:36:10 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-27 12:36:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-27 12:36:10 - SRCCONF=/dev/null TB --- 2013-06-27 12:36:10 - TARGET=mips TB --- 2013-06-27 12:36:10 - TARGET_ARCH=mips TB --- 2013-06-27 12:36:10 - TZ=UTC TB --- 2013-06-27 12:36:10 - __MAKE_CONF=/dev/null TB --- 2013-06-27 12:36:10 - cd /src TB --- 2013-06-27 12:36:10 - /usr/bin/make -B buildworld >>> World build started on Thu Jun 27 12:36:11 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O -pipe -G0 -I/src/usr.sbin/tcpdump/tcpdump -I/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -DINET6 -DLBL_ALIGN -I/obj/mips.mipsel/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO -DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-olsr.c cc -O -pipe -G0 -I/src/usr.sbin/tcpdump/tcpdump -I/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -DINET6 -DLBL_ALIGN -I/obj/mips.mipsel/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO -DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-ospf.c cc -O -pipe -G0 -I/src/usr.sbin/tcpdump/tcpdump -I/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -DINET6 -DLBL_ALIGN -I/obj/mips.mipsel/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO -DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-otv.c cc -O -pipe -G0 -I/src/usr.sbin/tcpdump/tcpdump -I/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -DINET6 -DLBL_ALIGN -I/obj/mips.mipsel/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO -DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c: In function 'print_src_dst': /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c:330: error: 'tcpstates' undeclared (first use in this function) /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c:330: error: (Each undeclared identifier is reported only once /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c:330: error: for each function it appears in.) *** Error code 1 Stop in /src/usr.sbin/tcpdump/tcpdump. *** Error code 1 Stop in /src/usr.sbin/tcpdump. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-06-27 13:52:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-27 13:52:37 - ERROR: failed to build world TB --- 2013-06-27 13:52:37 - 3007.23 user 542.01 system 4614.02 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-mips-mips.full From owner-freebsd-mips@FreeBSD.ORG Thu Jun 27 19:19:10 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 71FFAC0C; Thu, 27 Jun 2013 19:19:10 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 3050D1A36; Thu, 27 Jun 2013 19:19:10 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r5RJJ9Pk001453; Thu, 27 Jun 2013 19:19:09 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r5RJJ91c001437; Thu, 27 Jun 2013 19:19:09 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 Jun 2013 19:19:09 GMT Message-Id: <201306271919.r5RJJ91c001437@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 19:19:10 -0000 TB --- 2013-06-27 18:02:11 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-06-27 18:02:11 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-06-27 18:02:11 - starting RELENG_9 tinderbox run for mips/mips TB --- 2013-06-27 18:02:11 - cleaning the object tree TB --- 2013-06-27 18:02:28 - /usr/local/bin/svn stat /src TB --- 2013-06-27 18:03:04 - At svn revision 252306 TB --- 2013-06-27 18:03:05 - building world TB --- 2013-06-27 18:03:05 - CROSS_BUILD_TESTING=YES TB --- 2013-06-27 18:03:05 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-27 18:03:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-27 18:03:05 - SRCCONF=/dev/null TB --- 2013-06-27 18:03:05 - TARGET=mips TB --- 2013-06-27 18:03:05 - TARGET_ARCH=mips TB --- 2013-06-27 18:03:05 - TZ=UTC TB --- 2013-06-27 18:03:05 - __MAKE_CONF=/dev/null TB --- 2013-06-27 18:03:05 - cd /src TB --- 2013-06-27 18:03:05 - /usr/bin/make -B buildworld >>> World build started on Thu Jun 27 18:03:06 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O -pipe -G0 -I/src/usr.sbin/tcpdump/tcpdump -I/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -DINET6 -DLBL_ALIGN -I/obj/mips.mipsel/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO -DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-olsr.c cc -O -pipe -G0 -I/src/usr.sbin/tcpdump/tcpdump -I/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -DINET6 -DLBL_ALIGN -I/obj/mips.mipsel/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO -DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-ospf.c cc -O -pipe -G0 -I/src/usr.sbin/tcpdump/tcpdump -I/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -DINET6 -DLBL_ALIGN -I/obj/mips.mipsel/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO -DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-otv.c cc -O -pipe -G0 -I/src/usr.sbin/tcpdump/tcpdump -I/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -DINET6 -DLBL_ALIGN -I/obj/mips.mipsel/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO -DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c: In function 'print_src_dst': /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c:330: error: 'tcpstates' undeclared (first use in this function) /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c:330: error: (Each undeclared identifier is reported only once /src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c:330: error: for each function it appears in.) *** Error code 1 Stop in /src/usr.sbin/tcpdump/tcpdump. *** Error code 1 Stop in /src/usr.sbin/tcpdump. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-06-27 19:19:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-27 19:19:09 - ERROR: failed to build world TB --- 2013-06-27 19:19:09 - 3001.25 user 540.77 system 4617.64 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-mips-mips.full From owner-freebsd-mips@FreeBSD.ORG Fri Jun 28 05:27:30 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2D5CEB14; Fri, 28 Jun 2013 05:27:30 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id D431C12C2; Fri, 28 Jun 2013 05:27:29 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r5S5RTCQ076417; Fri, 28 Jun 2013 01:27:29 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r5S5RTOl076403; Fri, 28 Jun 2013 05:27:29 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 28 Jun 2013 05:27:29 GMT Message-Id: <201306280527.r5S5RTOl076403@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 05:27:30 -0000 TB --- 2013-06-28 04:38:54 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-28 04:38:54 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-28 04:38:54 - starting HEAD tinderbox run for mips/mips TB --- 2013-06-28 04:38:54 - cleaning the object tree TB --- 2013-06-28 04:38:54 - /usr/local/bin/svn stat /src TB --- 2013-06-28 04:39:01 - At svn revision 252320 TB --- 2013-06-28 04:39:02 - building world TB --- 2013-06-28 04:39:02 - CROSS_BUILD_TESTING=YES TB --- 2013-06-28 04:39:02 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-28 04:39:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-28 04:39:02 - SRCCONF=/dev/null TB --- 2013-06-28 04:39:02 - TARGET=mips TB --- 2013-06-28 04:39:02 - TARGET_ARCH=mips TB --- 2013-06-28 04:39:02 - TZ=UTC TB --- 2013-06-28 04:39:02 - __MAKE_CONF=/dev/null TB --- 2013-06-28 04:39:02 - cd /src TB --- 2013-06-28 04:39:02 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Fri Jun 28 04:39:09 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc1: warnings being treated as errors /src/sbin/swapon/swapon.c: In function 'swap_on_off_gbde': /src/sbin/swapon/swapon.c:251: warning: declaration of 'devname' shadows a global declaration /obj/mips.mips/src/tmp/usr/include/stdlib.h:272: warning: shadowed declaration is here /src/sbin/swapon/swapon.c: In function 'swap_on_off_geli': /src/sbin/swapon/swapon.c:323: warning: declaration of 'devname' shadows a global declaration /obj/mips.mips/src/tmp/usr/include/stdlib.h:272: warning: shadowed declaration is here /src/sbin/swapon/swapon.c:394: warning: cast discards qualifiers from pointer target type *** Error code 1 Stop. make: stopped in /src/sbin/swapon *** Error code 1 Stop. make: stopped in /obj/mips.mips/src/rescue/rescue *** Error code 1 Stop. make: stopped in /src/rescue/rescue *** Error code 1 Stop. make: stopped in /src/rescue *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-28 05:27:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-28 05:27:29 - ERROR: failed to build world TB --- 2013-06-28 05:27:29 - 2100.08 user 524.52 system 2915.05 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-mips-mips.full From owner-freebsd-mips@FreeBSD.ORG Fri Jun 28 15:11:40 2013 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C3391227; Fri, 28 Jun 2013 15:11:40 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 8063C11D4; Fri, 28 Jun 2013 15:11:40 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r5SFBdfN002033; Fri, 28 Jun 2013 11:11:39 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r5SFBdr1002030; Fri, 28 Jun 2013 15:11:39 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 28 Jun 2013 15:11:39 GMT Message-Id: <201306281511.r5SFBdr1002030@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 15:11:40 -0000 TB --- 2013-06-28 14:22:25 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-28 14:22:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-28 14:22:25 - starting HEAD tinderbox run for mips/mips TB --- 2013-06-28 14:22:25 - cleaning the object tree TB --- 2013-06-28 14:23:24 - /usr/local/bin/svn stat /src TB --- 2013-06-28 14:23:34 - At svn revision 252337 TB --- 2013-06-28 14:23:35 - building world TB --- 2013-06-28 14:23:35 - CROSS_BUILD_TESTING=YES TB --- 2013-06-28 14:23:35 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-28 14:23:35 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-28 14:23:35 - SRCCONF=/dev/null TB --- 2013-06-28 14:23:35 - TARGET=mips TB --- 2013-06-28 14:23:35 - TARGET_ARCH=mips TB --- 2013-06-28 14:23:35 - TZ=UTC TB --- 2013-06-28 14:23:35 - __MAKE_CONF=/dev/null TB --- 2013-06-28 14:23:35 - cd /src TB --- 2013-06-28 14:23:35 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Fri Jun 28 14:23:42 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] (cd /src/rescue/rescue/../../sbin/swapon && /obj/src/make.amd64/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/swapon/ depend && /obj/src/make.amd64/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/swapon/ swapon.o) rm -f .depend CC='cc ' mkdep -f .depend -a -DRESCUE -std=gnu99 /src/sbin/swapon/swapon.c echo swapon: /obj/mips.mips/src/tmp/usr/lib/libc.a /obj/mips.mips/src/tmp/usr/lib/libutil.a >> .depend cc -O -pipe -G0 -DRESCUE -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c /src/sbin/swapon/swapon.c cc1: warnings being treated as errors /src/sbin/swapon/swapon.c: In function 'swap_on_off_geli': /src/sbin/swapon/swapon.c:394: warning: cast discards qualifiers from pointer target type *** Error code 1 Stop. make: stopped in /src/sbin/swapon *** Error code 1 Stop. make: stopped in /obj/mips.mips/src/rescue/rescue *** Error code 1 Stop. make: stopped in /src/rescue/rescue *** Error code 1 Stop. make: stopped in /src/rescue *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-28 15:11:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-28 15:11:39 - ERROR: failed to build world TB --- 2013-06-28 15:11:39 - 2099.95 user 535.33 system 2953.81 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-mips-mips.full