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> In-Reply-To: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de> References: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170317120429.GX15630>