Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Mar 2017 18:31:11 +0100
From:      "O. Hartmann" <ohartmann@walstatt.org>
To:        Slawa Olhovchenkov <slw@zxy.spb.ru>
Cc:        "O. Hartmann" <ohartmann@walstatt.org>, 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:  <20170317183111.3a80f358@thor.intern.walstatt.dynvpn.de>
In-Reply-To: <20170317170735.GO70430@zxy.spb.ru>
References:  <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de> <20170317120429.GX15630@zxy.spb.ru> <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de> <20170317170735.GO70430@zxy.spb.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/mE3R_Z4p_+.7jfIsOz8p6j4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Am Fri, 17 Mar 2017 20:07:35 +0300
Slawa Olhovchenkov <slw@zxy.spb.ru> schrieb:

> On Fri, Mar 17, 2017 at 05:53:24PM +0100, O. Hartmann wrote:
>=20
> > 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:
> > >  =20
> > > > Running recent CURRENT on a Fujitsu Celsius M740 equipted with an I=
ntel(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 fea=
ture, which
> > > > is supposed to be a feature of this type of CPU:   =20
> > >=20
> > > What reassons to detect AES-NI by FreeBSD? =20
> >=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
>=20
> This sample can have disabled AES-NI by vendor, in BIOS, for example.
> As I show by links this is posible.
>=20
> CPUID in you example don't show AES-NI capabilities, for example
> 1650v4 w/ AES-NI
>=20
> CPU: Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz (3600.07-MHz K8-class CPU)
>   Origin=3D"GenuineIntel"  Id=3D0x406f1  Family=3D0x6  Model=3D0x4f  Step=
ping=3D1
>   Features=3D0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,=
PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>   Features2=3D0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2=
,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,T=
SCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
>                                                                          =
                                                                           =
   ^^^^^^
>   AMD Features=3D0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
>   AMD Features2=3D0x121<LAHF,ABM,Prefetch>
>   Structured Extended
> Features=3D0x21cbfbb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID=
,RTM,PQM,NFPUSG,PQE,RDSEED,ADX,SMAP,PROCTRACE>
> XSAVE Features=3D0x1<XSAVEOPT> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,Po=
stIntr
>   TSC: P-state invariant, performance statistics
>=20
> In you sample: "TSCDLT,XSAVE"
>=20
> May be AES-NI disabled by vendor and FreeBSD correct show this. Or some b=
ug in FreeBSD,
> AES-NI work and other OS show AES-NI capabilities.
>=20
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

We have some LGA1151 XEON based 19 inch rack server, also equipted with Has=
well
E3-12XX-v3 XEONs and FreeBSD, also CURRENT, does show AES-NI.

You're right, the vendor could have disabled AES-NI by intention - but they=
 offered this
box especially with AES-NI capabilities.=20

See here:

  http://freebsd.1045724.x6.nabble.com/r285947-broken-AESNI-support-No-aesn=
i0-on-Intel-XEON-E5-1650-v3-on-Fujitsu-Celsius-M740-td6028895.html

I feel a bit pissed off right now due to Fujitsu, because we started testin=
g some
encrypting features and I'd like to use AES-NI and I run into this issue ag=
ain.

I need to know that FreeBSD is not the issue with this specific CPU type. I=
'm still
frustrated by that stupid comment "UNIX is not supoorted" I got that time t=
hen when I
reported 2015 the issue to Fujitsu.

--=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_/mE3R_Z4p_+.7jfIsOz8p6j4
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWMwdXwAKCRDS528fyFhY
lPbeAf4s2Q/Pr9/YJqUTUpdZtqiOo6Ch10ZkQeCSEaVjIi+zzkxkMgg5Kqooj8YD
G+JFqLX4jhsojeWoLg/09EfWUbIfAf9sAQc+PylLTB/nhFwtUpuKSt3ViTO9MPee
PHcUxPN2RF0I82LyQV9cUcPE9kvnCTj/aYnnfC4Tuui7x3juqi/1
=oxwG
-----END PGP SIGNATURE-----

--Sig_/mE3R_Z4p_+.7jfIsOz8p6j4--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170317183111.3a80f358>