From owner-freebsd-current@freebsd.org Fri Mar 17 16:53:36 2017 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 01FB8D10C32 for ; Fri, 17 Mar 2017 16:53:36 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A56D1356 for ; Fri, 17 Mar 2017 16:53:34 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.168.50]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MFu0Y-1d1aKD2YiM-00Etv8; Fri, 17 Mar 2017 17:53:31 +0100 Date: Fri, 17 Mar 2017 17:53:24 +0100 From: "O. Hartmann" To: Slawa Olhovchenkov Cc: "O. Hartmann" , freebsd-current Subject: Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3 Message-ID: <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170317120429.GX15630@zxy.spb.ru> References: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de> <20170317120429.GX15630@zxy.spb.ru> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/yI9ma.EAvgiALh__OfIuIeR"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:cuUbmObyu3suE2Rwy+t6YunYaAZ/afIrBJb386d2NcHBcexJTv5 P7xdEIQpmoNXk0OVWaxZwDpW+tdO0FW9gPG4dNO7PgXaL2a/3heWYAVeC/uYDP0Uz/Mb7Ke k2F3iNYuCclTePl/c35LYD8tWqXVFEiluh8rLpiasZkTOmR+MYsuUC5/8XaKCfds/dB+Dzn oBs4Zk4xVKEBGL6QZ09Eg== X-UI-Out-Filterresults: notjunk:1;V01:K0:1r1SEZIRg7g=:iAMwtbnNPdg5Ig5os3o/VI GKMQMGFGGHh1HpVzRAPoDhI4FP5kh95AneDWyDfjU/GiUS/VovI6EADEyNfTuTHtj9GSfYQAO rdBy5LMg0hBwBHofuEoV3ip2EIEmkBcaA9IyRKQyLlfF4KjdZd9ZeDXlmbOoOFQHohmJl0RHy 1rAHy89t9dL+opYCF5BZNA+Qbbp9JZM5F7jhYk7izRLvKtDxHzrwE73P6/6MAt7HEkU5ajIKi f1fZELen3s6gW5ZzNMXg2GbMF9qwXuAkcf4hP4i4opiTx29JI9WcJnTIiq+qKIloo8ooTmM0O XwgnjxrmdDy3FbnWQdN0J9d4Mi0ajLz97Tk5Nd2nrt3iWTZtBHlSnGLNAY04a5JWDRv++5MRI QdYT/7NoooI2hJgwf0X9l12mukBgFd+5Xf3wrSGx2bzlZMoIHOk+5Y/RfGQ3xRQ62RxOT1PIA P9FRtBRSOm5YXaRwKA6VVgSyDO6tI9ynS43fpe1KdfM4v0tMEdXvvnIXDPhyqP9611WXT53Oc FjwdRZ3AhAaNMmrAg7VTXzLsHqVgNH/dhU3x1VOvmSJcsAKSwtb4At/DcH99Fiq4JMhDL/aHH lldbvVC/NaAnOe614CzhnkjErePyQi8+EyONFwtdAhKbOcEH2JcykY6sSpGQKa7ZhDyPG1bku jQsTNJkULYRJNYdAG3wmJmEkK3q2rJAkEVv1L2YeKDrZ7FFTVihtsenS0xz6g+FjSw8ujVdXx rpYwXl6xzzmSOjIphFqbikNYf6+FTeOTv2hKtSgiG+JI13IxpqwOzvVjAOs= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 17 Mar 2017 16:53:36 -0000 --Sig_/yI9ma.EAvgiALh__OfIuIeR Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Fri, 17 Mar 2017 15:04:29 +0300 Slawa Olhovchenkov schrieb: > On Fri, Mar 17, 2017 at 12:36:25PM +0100, O. Hartmann wrote: >=20 > > Running recent CURRENT on a Fujitsu Celsius M740 equipted with an Intel= (R) > > Xeon(R) CPU E5-1650 v3 @ 3.50GHz CPU makes me some trouble. > >=20 > > FreeBSD does not report the existence or availability of AES-NI feature= , which > > is supposed to be a feature of this type of CPU: =20 >=20 > What reassons to detect AES-NI by FreeBSD? What do you mean? I do not understand! FreeBSD is supposed to read the CPUI= D and therefore the capabilities as every other OS, too. But there may some circu= mstances why FBSD won't. I do not know, that is the reason why I'm asking here. > Other OS detect AES-NI on this server? I havn't ried so far, the box is in heavy use. I'd like to check with some = live USB drive versions and report later. >=20 > AES-NI may be disabled by BIOS/vendor/BIOS settings There is no option for that, I'm looking for several time for that right no= w. Even with TPM enabled - which is considered to be necessary on several firmwares - th= ere is no change. >=20 > https://forums.lenovo.com/t5/ThinkPad-11e-Windows-13-E-and/AES-NI-is-disa= bled-on-my-13-New-S2/td-p/3498468 > http://h17007.www1.hpe.com/docs/iss/proliant_uefi/UEFI_Gen9_060216/s_enab= le_AES-NI.html > http://en.community.dell.com/support-forums/servers/f/956/t/19509653 As I said, even with the brand new firmware from January of this year (2017= ) there is no change - the firmware prior to that showed the same non-existing AES-NI fea= ture. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/yI9ma.EAvgiALh__OfIuIeR Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWMwUhAAKCRDS528fyFhY lJvNAgCAEGi7jlaiAmUNDrZugYBJCm0geufYkKRIgAc7ZT9RIthYnx0I9V6yTBOX AkUcCmTmISV9G4VNalH8h6ytQNerAf9eiYv6T1paKIi7usAd163iEyhVm9gbykOm xbNhL+6jIlynSmNvnO1q9CeeMUV8YLyl9KBCoXNZVGqq3F1pwMvP =0RZC -----END PGP SIGNATURE----- --Sig_/yI9ma.EAvgiALh__OfIuIeR--