From owner-freebsd-current@freebsd.org Wed Jul 29 15:19:36 2015 Return-Path: Delivered-To: freebsd-current@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 6D2BA9AEAB3 for ; Wed, 29 Jul 2015 15:19:36 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5114B1B65 for ; Wed, 29 Jul 2015 15:19:35 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t6TFJZm0006980 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jul 2015 08:19:35 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id t6TFJYwQ006979; Wed, 29 Jul 2015 08:19:34 -0700 (PDT) (envelope-from jmg) Date: Wed, 29 Jul 2015 08:19:34 -0700 From: John-Mark Gurney To: "O. Hartmann" Cc: freebsd-current Subject: Re: r285947: broken AESNI support? No aesni0 on Intel XEON E5-1650-v3 on Fujitsu Celsius M740 Message-ID: <20150729151934.GE78154@funkthat.com> References: <20150729073950.2d09ea6b@freyja.zeit4.iv.bundesimmobilien.de> <20150729073616.GB78154@funkthat.com> <20150729102046.5f85c014@freyja.zeit4.iv.bundesimmobilien.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150729102046.5f85c014@freyja.zeit4.iv.bundesimmobilien.de> X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Wed, 29 Jul 2015 08:19:35 -0700 (PDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2015 15:19:36 -0000 O. Hartmann wrote this message on Wed, Jul 29, 2015 at 10:20 +0200: > On Wed, 29 Jul 2015 00:36:16 -0700 > John-Mark Gurney wrote: > > > O. Hartmann wrote this message on Wed, Jul 29, 2015 at 07:39 +0200: > > > Running a workstation with CURRENT (FreeBSD 11.0-CURRENT #5 r285947: Tue > > > Jul 28 13:39:03 CEST 2015 amd64) equipted with an Intel XEON E5-1650 v3, > > > see the extraction from recent "dmesg" below. > > > > > > I double checked the UEFI settings (the box is a Fujitsu Celsius M740 with > > > most recent firmware 1.8.0) and I didn't find anything indicating that > > > AES-NI has been deactivated. > > > > > > I checked the data sheet at Intel, the CPU should support AES-NI. > > > > > > I also filed a PR: Bug 201960 > > > > > > I'd like to know whether this is by intention, by bug (feature mask wrong?) > > > or by a faulty firmware? Any hints? > > > > Can you send me the output of cpuid-etallen? It's pretty long, so > > maybe off list would be better... It's from a port of the same > > name... > > I'm sorry, since I work in a pretty restricted area, I can not offer > webspace-similar download areas, but if it is not offending the list, i could > provide a compressed output. > > Find the output attached xz-compressed ... I cleared intentionally the serial > number, just as a notice. Yep, this confirms that AES-NI is off: AES instruction = false Which isn't a surprise from our other data points. Just wanted to make sure... > > Also, it looks like a microcode update could fix this issue, have you > > tried to look at that? > > > > https://albertveli.wordpress.com/2013/03/05/aes-ni-enabled/ > > > > Looks very similar to your issue, though it's a different microarch.. > > Your's is a Haswell that has the TSX bug in it, and it could be that > > the bios is disabling too many feature bits... > > > > Have you made sure that your machine has the latest BIOS? A newer > > BIOS could reenable the feature too... > > I just checked this moment again, but the latest UEFI firmware Fujitsu is > offering is version 1.8.0 from April of this year. I would complain to the vendor of your machine... I'd contact them and try to return the machine as defective... It clearly is... > > > [...] > > > FreeBSD clang version 3.6.1 (tags/RELEASE_361/final 237755) 20150525 > > > VT: running with driver "efifb". > > > CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz (3491.98-MHz K8-class CPU) > > > Origin="GenuineIntel" Id=0x306f2 Family=0x6 Model=0x3f Stepping=2 > > > Features=0xbfebfbff > > > Features2=0x7dfefbff > > > > There should be an AESNI feature on this line, but clearly not... > > On another machine, also Fujitsu, but a 19 inch rack server module with a low > energy XEON E5-12XXv3, I can clearly see the AESNI feature in Feature2 list > and, conclusively, the aesni0 device is present and reported. > > > > > [...] > > > > > aesni0: No AESNI support. > > > [...] > > > > Which is why you get this... > > > > I applied the port sysutils/cpuid to another system, runnin a i5-4200M mobile > CPU (Lenovo notebook). The rows indicating > > family = Intel ... > (simple synth) = ... > > look much more "modern" for my opinion as the output I provided shows on the > CPU in question. It is just a hunch ... Seems, I've bought Intel(ian) crap ;-) > with no features and from another mellenium ... Yep... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."