On Wed, 29 Jul 2015 00:36:16 -0700
John-Mark Gurney <j...@funkthat.com> wrote:

> O. Hartmann wrote this message on Wed, Jul 29, 2015 at 07:39 +0200:
> > Running a workstation with CURRENT (FreeBSD 11.0-CURRENT #5 r285947: Tue
> > Jul 28 13:39:03 CEST 2015 amd64) equipted with an Intel XEON E5-1650 v3,
> > see the extraction from recent "dmesg" below.
> > 
> > I double checked the UEFI settings (the box is a Fujitsu Celsius M740 with
> > most recent firmware 1.8.0) and I didn't find anything indicating that
> > AES-NI has been deactivated.
> > 
> > I checked the data sheet at Intel, the CPU should support AES-NI.
> > 
> > I also filed a PR: Bug 201960 
> > 
> > I'd like to know whether this is by intention, by bug (feature mask wrong?)
> > or by a faulty firmware? Any hints?
> 
> Can you send me the output of cpuid-etallen?  It's pretty long, so
> maybe off list would be better...  It's from a port of the same
> name...

I'm sorry, since I work in a pretty restricted area, I can not offer
webspace-similar download areas, but if it is not offending the list, i could
provide a compressed output.

Find the output attached xz-compressed ... I cleared intentionally the serial
number, just as a notice.


> 
> Also, it looks like a microcode update could fix this issue, have you
> tried to look at that?
> 
> https://albertveli.wordpress.com/2013/03/05/aes-ni-enabled/
> 
> Looks very similar to your issue, though it's a different microarch..
> Your's is a Haswell that has the TSX bug in it, and it could be that
> the bios is disabling too many feature bits...
> 
> Have you made sure that your machine has the latest BIOS?  A newer
> BIOS could reenable the feature too...

I just checked this moment again, but the latest UEFI firmware Fujitsu is
offering is version 1.8.0 from April of this year.

> 
> > [...]
> > FreeBSD clang version 3.6.1 (tags/RELEASE_361/final 237755) 20150525
> > VT: running with driver "efifb".
> > CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz (3491.98-MHz K8-class CPU)
> >   Origin="GenuineIntel"  Id=0x306f2  Family=0x6  Model=0x3f  Stepping=2
> >   
> > Features=0xbfebfbff<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=0x7dfefbff<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,TSCDLT,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
> 
> There should be an AESNI feature on this line, but clearly not...

On another machine, also Fujitsu, but a 19 inch rack server module with a low
energy XEON E5-12XXv3, I can clearly see the AESNI feature in Feature2 list
and, conclusively, the aesni0 device is present and reported.

> 
> [...]
> 
> > aesni0: No AESNI support.
> > [...]
> 
> Which is why you get this...
> 

I applied the port sysutils/cpuid to another system, runnin a i5-4200M mobile
CPU (Lenovo notebook). The rows indicating

family          = Intel ...
(simple synth)  = ...

look much more "modern" for my opinion as the output I provided shows on the
CPU in question. It is just a hunch ... Seems, I've bought Intel(ian) crap ;-)
with no features and from another mellenium ...

oh

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to