From owner-freebsd-current@freebsd.org Tue Aug 18 04:59:45 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 73D439BB929 for ; Tue, 18 Aug 2015 04:59:45 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 275536EE for ; Tue, 18 Aug 2015 04:59:44 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZRYzn-003Xfj-9o>; Tue, 18 Aug 2015 06:59:35 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZRYzm-002WMY-Vt>; Tue, 18 Aug 2015 06:59:35 +0200 Date: Tue, 18 Aug 2015 06:59:29 +0200 From: "O. Hartmann" To: John-Mark Gurney Cc: freebsd-current Subject: Re: r285947: broken AESNI support? No aesni0 on Intel XEON E5-1650-v3 on Fujitsu Celsius M740 Message-ID: <20150818065929.06562ff6@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20150729151934.GE78154@funkthat.com> References: <20150729073950.2d09ea6b@freyja.zeit4.iv.bundesimmobilien.de> <20150729073616.GB78154@funkthat.com> <20150729102046.5f85c014@freyja.zeit4.iv.bundesimmobilien.de> <20150729151934.GE78154@funkthat.com> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 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: Tue, 18 Aug 2015 04:59:45 -0000 On Wed, 29 Jul 2015 08:19:34 -0700 John-Mark Gurney wrote: > 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... > Hello. I contacted the Fujitsu support in Munich, explained the problem of missing AES-NI and TXT facility and also explained the fact, that he most recent firmware for the Celsius M-740 does not allow enabling TXT in the firmware - it switches back to disabled all the time I reboot the box. I made myself very clear that I expect those features on the CPU built in. The service wrote me an email back that is more than disappointing - and a kind of scaring! The translation is done very simple - as the answer was very simple: a) the CPU has feature AES-NI b) the CPU has feature TXT c) UNIX is no supported OS (I told I'm faciliating FreeBSD as OS uppon the question what OS I use since I guess Fujitsu would run their "diagnostics program" to confirm my reported issue) Well, my understanding is that the firmware is responsible for detecting CPU features and provide those in a suitable way the overlaying operating system for further use. I deduce this from the fact that someone can disable features of the CPU, like VT-d, in the firmware/BIOS and then such disabled features are not seen by the OS anymore. At this point I need to be 100% sure that FreeBSD isn't the culprit before escalating this boring show with Fujitsu. Thanks in advance and best regards, O. Hartmann