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

Also, it looks like a microcode update could fix this issue, have you
tried to look at that?


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...

> [...]
> 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

There should be an AESNI feature on this line, but clearly not...


> aesni0: No AESNI support.
> [...]

Which is why you get this...

  John-Mark Gurney                              Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."
freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to