Article ID: 000037237 Content Type: Product Information & Documentation Last Reviewed: 07/29/2021

Why is AES-NI not Detected by the "lscpu" Command?

Environment

linux

BUILT IN - ARTICLE INTRO SECOND COMPONENT
Summary

Information about the Linux "lscpu" command not reporting AES-NI

Description

All the documentation states that Advanced Encryption Standard New Instructions (AES-NI) is supported by the processor. However, it is not represented in the cpu flags.

NoteData Plane Development Kit (DPDK) does not compile.


See an lscpu command output below as an example (no AES-IN in the bold Flags line):

lscpu 
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 63
Model name: Intel(R) Xeon(R) CPU E5-1630 v3 @ 3.70GHz
Stepping: 2
CPU MHz: 1201.777
CPU max MHz: 3800.0000
CPU min MHz: 1200.0000
BogoMIPS: 7399.67
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 10240K
NUMA node0 CPU(s): 0-7
►Flags: 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 ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm epb invpcid_single ibrs ibpb stibp kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts


 

Resolution

See if the processor model is listed among those supporting AES-NI. For this, go to our Product Specifications Advanced Search. If it is, then, if the Intel® Processor Identification Utility (Bootable Version) does not detect AES-NI still, contact Support with this utility report for diagnosis.

Disclaimer

1

All postings and use of the content on this site are subject to Intel.com Terms of Use.