From owner-freebsd-current@freebsd.org Fri Mar 17 11:36:29 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C0D1D0E40A for ; Fri, 17 Mar 2017 11:36:29 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C23DC17B7 for ; Fri, 17 Mar 2017 11:36:28 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MQeET-1ced2y3zpt-00U5Lf for ; Fri, 17 Mar 2017 12:36:26 +0100 Date: Fri, 17 Mar 2017 12:36:25 +0100 From: "O. Hartmann" To: freebsd-current Subject: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3 Message-ID: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:gNXboaAcqbuhFJFfu9oAEI/tSkYn8DutIO1wc+7mkFhFHY9juqI PjGQz8mxJM5e0EPj+iSa7lEsKIybRxzWflZWMvUSHzxWnMD+czNcYZeNZAIIXiDvkvOeo8b vm6O9cqyPHyyFRciK00JVpk0/6eK2ugCNQG8yUs/zHhMzWjNZy+dEZNpGV6HsGo9KPhHuHi MAMDb3ej3Yy31nFXKJPaA== X-UI-Out-Filterresults: notjunk:1;V01:K0:SGm8bVj+sHQ=:pjk7GI6nJoccDwBa4iuAIR Tl1Qxk1+6ojJgKU5fZqRhHQ8Nt2ykWNHJj1UAFyF7sTfYJfay3VD1nEU6jsYCs4IuMaysBabZ ffRLiFtPAhgecQUNfLEEDgrXKDdTdVqi2r9hC6LAcZYC/3PEpEeCe7oReGz06bfgA0RdtxcSI MTbJUTMEPnFWTNi2tKhS8qk8V/yJmyQ1GZbtkWPEMIjZf6wOmipusapLkmtY8ia0lsZnduC1f m/rMf7exUf3MZ8I+bxFXFA1fN/Y2SmjimmDQtZsMqh1uktDNq/7DDa+N8IMf/kRUF1tTebjG3 zZIsGV4+8gFii/ysqPAROi00YhbiqUvkzjj7PJv6uA3FFJkXpFvf+XaglOzHnYGm5Vqjw28lB B532hQSHbbmnr8mn3PJ3Mst4hnvhow9+ELWGqMzJpkTvByhE31C/h/2Dk3eQwixI/8L9GGCR8 ZHXn3cgDy5HlU6zfGRhNn18T7mbrwKAdITijeVQbkYi7cP9fqJJ/Dtam08WniwjwQepOs6n5h SrOaaPiwULZEBM6G3zRphL2zRFFWUWx5Ez3WconYzmiVydw33Prx4VfeXn4SeHP4/V++0PX4f QgbzauVwYdhH6pwjVpuYFsv49NZxS9PScRyUBWCE+fOmz6oos8RSBvLAacb2PAMxkHYGBqPrP DuXTFPFySlxfkJIQEBluT+xSsDAxFpvPzfJv4L/DMaZ4H4co3mV7rOqgYf+P3Q0fCpRxZJRXd fRCpn4hCrZWKdIxlQzqqoa/Fl9IzeJLfNxdsOA8jJff+y3zgwq8AR/dqIj58fPLPhyKEFK8ni DR72Gpg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 11:36:29 -0000 Running recent CURRENT on a Fujitsu Celsius M740 equipted with an Intel(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 feature, which is supposed to be a feature of this type of CPU: dmesg [...] FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM 4.0.0) VT(efifb): resolution 1920x1200 CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz (3491.99-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306f2 Family=0x6 Model=0x3f Stepping=2 Features=0xbfebfbff Features2=0x7dfefbff AMD Features=0x2c100800 AMD Features2=0x21 Structured Extended Features=0x37ab XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 32990359552 (31462 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs FreeBSD/SMP: 1 package(s) x 6 core(s) x 2 hardware threads Security policy loaded: TrustedBSD MAC/BSD Extended (mac_bsdextended) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard SMP: AP CPU #1 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #8 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #3 Launched! random: entropy device external interface kbd0 at kbdmux0 netmap: loaded module random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 cryptosoft0: on motherboard aesni0: No AESNI support. [...] This system has the most recent firmware I could find on fujitsu.com. Recent dmidecode doesn't work, it reports [...] root@furor:~ # dmidecode # dmidecode 3.0 Scanning /dev/mem for entry point. # No SMBIOS nor DMI entry point found, sorry. A while ago, I filed a report to Fujitsu's customer service. They stupidly ansered with an extraction of Intel's ARK information regarding the CPU type indicating that the CPU does have AES-NI - they completely ignored the fact that I claimed that this is an hardware malfunction. So, after I reported in I've been using FreeBSD UNIX as the operating system, I received a short answer: UNIX is not supported. So, I'll ask here for some advice and will check the possibility whether FreeBSD is incapable of enabling those features or whether this is a firmware/hardware bug I want Fujitsu to fix. Can someone sched some light on this, please? Are there Haswell XEONs known for bugs like this? Thank you very much in advance, Oliver