Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Mar 2017 13:02:53 -0400
From:      Allan Jude <allanjude@freebsd.org>
To:        freebsd-current@freebsd.org
Subject:   Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3
Message-ID:  <de47e9ad-dc57-edab-eab9-1aebefff5028@freebsd.org>
In-Reply-To: <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de>
References:  <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de> <20170317120429.GX15630@zxy.spb.ru> <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tmRUgt3UNqJJDDqxXnHO3IUnxk5uNW1n6
Content-Type: multipart/mixed; boundary="SEkoLj3kKdmu3SMnwHi54hm2hgBsGTXLl";
 protected-headers="v1"
From: Allan Jude <allanjude@freebsd.org>
To: freebsd-current@freebsd.org
Message-ID: <de47e9ad-dc57-edab-eab9-1aebefff5028@freebsd.org>
Subject: Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU
 E5-1650 v3
References: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de>
 <20170317120429.GX15630@zxy.spb.ru>
 <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de>
In-Reply-To: <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de>

--SEkoLj3kKdmu3SMnwHi54hm2hgBsGTXLl
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 2017-03-17 12:53, O. Hartmann wrote:
> Am Fri, 17 Mar 2017 15:04:29 +0300
> Slawa Olhovchenkov <slw@zxy.spb.ru> schrieb:
>=20
>> On Fri, Mar 17, 2017 at 12:36:25PM +0100, O. Hartmann wrote:
>>
>>> Running recent CURRENT on a Fujitsu Celsius M740 equipted with an Int=
el(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 featu=
re, which
>>> is supposed to be a feature of this type of CPU: =20
>>
>> What reassons to detect AES-NI by FreeBSD?
>=20
> What do you mean? I do not understand! FreeBSD is supposed to read the =
CPUID and
> therefore the capabilities as every other OS, too. But there may some c=
ircumstances why
> FBSD won't. I do not know, that is the reason why I'm asking here.
>=20
>> Other OS detect AES-NI on this server?
>=20
> I havn't ried so far, the box is in heavy use. I'd like to check with s=
ome live USB drive
> versions and report later.
>=20
>>
>> AES-NI may be disabled by BIOS/vendor/BIOS settings
>=20
> There is no option for that, I'm looking for several time for that righ=
t now. Even with
> TPM enabled - which is considered to be necessary on several firmwares =
- there is no
> change.
>=20
>>
>> https://forums.lenovo.com/t5/ThinkPad-11e-Windows-13-E-and/AES-NI-is-d=
isabled-on-my-13-New-S2/td-p/3498468
>> http://h17007.www1.hpe.com/docs/iss/proliant_uefi/UEFI_Gen9_060216/s_e=
nable_AES-NI.html
>> http://en.community.dell.com/support-forums/servers/f/956/t/19509653
>=20
> 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=
 feature.
>=20

I have used the E5-1650 v3 in the FreeBSD test cluster, and AES-NI works
fine.

I had to enable it in the BIOS though. It is on the CPU features page,
and may have an odd name, rather than "AES-NI"

AES-NI is unrelated to TPM.

--=20
Allan Jude


--SEkoLj3kKdmu3SMnwHi54hm2hgBsGTXLl--

--tmRUgt3UNqJJDDqxXnHO3IUnxk5uNW1n6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (MingW32)

iQIcBAEBAgAGBQJYzBbBAAoJEBmVNT4SmAt+TEYP/1KnejcBjV9j8dPs9pw9xQkA
+4x01NSDSoudimACgjNgOemLGOLOUiO5tsakF9ZXIaKKi/jeXYxnIsjfsPmhFkJm
U1oC8lhjxiFdclZZufpEL88Krtp9lTVFnqDFy8OZ/ZRj4yjwe/lgxUJsMX9WjVwq
RrScf99DMn5DpltMSUTpZ4cDlE3tAKsA7vv2yHnq07PetBDNtOlTQWh94sjkPjI9
D0MLlPMHt1yLEdM7E/ZU1Vv+Ux0CpAS+ntqAxrIKz96/6bqq0wJp4ng2nvITKMJ5
ST7ZXlW6oOZRn0aXi0i0rsiVojQyZBeD31srT7fDQOULrHJ/JMQ4oRHf5W25oUhQ
CqA0ENYF0y8ziCB+cFnP2YTD+5QQn3DOwmaPDQdeqUxLbetmcE58r7H3DsFi6/X/
9CZj4nzfqHH9BoS9kTtue31jfqMpUVAoOV6lDHu9AS+xYcNCNPZGR0fONG/meRLI
0Y3eIw0ZGBIB+cUdNwBNQi9dc+2xCH6fbLnRToxN2KpZ4syu5IxzHnPnblujPm6G
yt54fMVhMbYRFeOU1RHYTseQMaMB3CGSY8XruWUo87jXd3lYsZkIcQafCUvH7jN0
dr9kyN0+dgQ/EKe9clPZ399MDfJ/YmI76fGLCF3kFxFLrDTI9fy6MKjD284ujSOb
A0exaT3mGUYmTo2SAonK
=JqAf
-----END PGP SIGNATURE-----

--tmRUgt3UNqJJDDqxXnHO3IUnxk5uNW1n6--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?de47e9ad-dc57-edab-eab9-1aebefff5028>