From owner-freebsd-current@freebsd.org  Fri Mar 17 12:04:32 2017
Return-Path: <owner-freebsd-current@freebsd.org>
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 B0A0FD0F600
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 17 Mar 2017 12:04:32 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (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 72E4D1CA7
 for <freebsd-current@freebsd.org>; Fri, 17 Mar 2017 12:04:32 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1coqcP-000HkV-8x; Fri, 17 Mar 2017 15:04:29 +0300
Date: Fri, 17 Mar 2017 15:04:29 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: "O. Hartmann" <ohartmann@walstatt.org>
Cc: freebsd-current <freebsd-current@freebsd.org>
Subject: Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU
 E5-1650 v3
Message-ID: <20170317120429.GX15630@zxy.spb.ru>
References: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 12:04:32 -0000

On Fri, Mar 17, 2017 at 12:36:25PM +0100, O. Hartmann wrote:

> 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.
> 
> FreeBSD does not report the existence or availability of AES-NI feature, which
> is supposed to be a feature of this type of CPU:

What reassons to detect AES-NI by FreeBSD?
Other OS detect AES-NI on this server?

AES-NI may be disabled by BIOS/vendor/BIOS settings

https://forums.lenovo.com/t5/ThinkPad-11e-Windows-13-E-and/AES-NI-is-disabled-on-my-13-New-S2/td-p/3498468
http://h17007.www1.hpe.com/docs/iss/proliant_uefi/UEFI_Gen9_060216/s_enable_AES-NI.html
http://en.community.dell.com/support-forums/servers/f/956/t/19509653