From owner-freebsd-current@freebsd.org Sun Feb 18 10:41:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E599F24D7E for ; Sun, 18 Feb 2018 10:41:39 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 130E570334 for ; Sun, 18 Feb 2018 10:41:39 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id CBA43F24D7D; Sun, 18 Feb 2018 10:41:38 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7E1BF24D7C for ; Sun, 18 Feb 2018 10:41:38 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D63270330 for ; Sun, 18 Feb 2018 10:41:38 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1enMPZ-000GFD-IA for current@freebsd.org; Sun, 18 Feb 2018 11:41:37 +0100 Date: Sun, 18 Feb 2018 11:41:37 +0100 From: Kurt Jaeger To: current@freebsd.org Subject: How to find CPU microcode version ? Message-ID: <20180218104137.GA32429@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 18 Feb 2018 10:41:39 -0000 Hi! How do I find the microcode version a Intel CPU is currently using ? Background: When Spectre/Meltdown hit, Intel released new microcode around 20180108. I've used the devcpu-data port at that time to update the microcode at that time, and the box in question developed strange instability issues approx. since 14th of Februar. It had two updates since 8th of January, to r328013 on the 16th of Jan. and to r328899 on the 6th of February. Around the 14th, processes started to be killed for out of swapspace, even if the box had almost no load at all. pid 1056 (mutt), uid 104, was killed: out of swap space pid 536 (devd), uid 0, was killed: out of swap space pid 15093 (exim), uid 26, was killed: out of swap space pid 91868 (mutt), uid 104, was killed: out of swap space pid 1086 (sshd), uid 104, was killed: out of swap space Reboot of the box and waiting a few hours and the problem re-occured. The box has 32 GB RAM and 34 GB swap, which never was utilized beyond a few hundred MBs. Moving the two disks involved to a very similar hardware and the 'dying' stopped. The 'strange box' runs a debian version now for 24 hours, no problems. -- pi@opsec.eu +49 171 3101372 2 years to go !