From owner-freebsd-current@freebsd.org Tue Sep 11 00:41:22 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 5806D10A048C for ; Tue, 11 Sep 2018 00:41:22 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC06A7C4C0 for ; Tue, 11 Sep 2018 00:41:21 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf1-x441.google.com with SMTP id j26-v6so11304060pfi.10 for ; Mon, 10 Sep 2018 17:41:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=0P8kChDrL2bcosXuU7taomEGNa74TioRELVVEfCB7w0=; b=hQ3bs6iY066JoN63x2I8m1FVKgMiUmp2ONLqJA7CcEQFLLBIGbe3UUrq4bd4E+a3we e+dVnP5q/RLTNezAmDRjgClcDDxlVlflt3p6OaViF0vRmY0t8GMSbJwQXZcrFpXlwqSF Z7huJOp0t4Ea7j8kmjmX10AiYM9nlWXETFoCsW6nOpBuJq7IZP3FGBg3n1fe+6Cd05zf VBAFznH1e/sUsrpa0+ObcfjAugQwhbQ+8l5lDxRBNNmgZUvu5OyURQyfNihiHdpmpA6K 3NEuLYldaO1PGlBsyMh1Gn3k2GGeXKtbqfGKQspThrMYLG4KLZo5/XT5mVme4RoKwwLE cJmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=0P8kChDrL2bcosXuU7taomEGNa74TioRELVVEfCB7w0=; b=mEyj7Sm2jnKirOZ7/sUmRVPrQ8PxnWk1d1PdQQnN2JyMg6OJAFrPspxVglxQw8ypdS Lp5v+SGyXwzmBvNp8uBbQcUud3jfwBD1PA0e6Q9cJlelhP0fvxci7vW/OeL0dC5q4uLL PU2a3udlYoAZmjDkahN9qMwmp2El5sWVuj+guO+8SO+DISMq27cHUqvDcTc0jHGDlEez Af9fHu0H1rwCxPVvZLCJJAC/u8WVfDVLs1CPf1K7YYspFITHDN9K02LQd/UBGd+UhFIx SGqK6/5qw1jfpX034LSX+UgYGajIb6mqmVE7a2MsZWmSBz5zYPepkLaoTElap9lNhe9Q Y4Bg== X-Gm-Message-State: APzg51Cdq+bs3HKrKF6aUsFRzFlRw419I9NuSgkx05jcqiq3IVp+TcvG ICzS4VLAcnDDbsVr5RQcxhMil7Xk X-Google-Smtp-Source: ANB0VdYrljU1GZ72GeHzDXLS7/Hky3u/cOakR38IS/IXGFTq2UbMmgLbw438Oifsra76Jxcj/xSXGg== X-Received: by 2002:a63:3cc:: with SMTP id 195-v6mr24700260pgd.229.1536626480677; Mon, 10 Sep 2018 17:41:20 -0700 (PDT) Received: from raichu (toroon0560w-lp130-01-174-88-78-8.dsl.bell.ca. [174.88.78.8]) by smtp.gmail.com with ESMTPSA id q25-v6sm22900683pfh.113.2018.09.10.17.41.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Sep 2018 17:41:19 -0700 (PDT) Sender: Mark Johnston Date: Mon, 10 Sep 2018 20:41:17 -0400 From: Mark Johnston To: Pete Wright Cc: freebsd-current@freebsd.org Subject: Re: testing early microcode loading Message-ID: <20180911004117.GE2849@raichu> References: <20180910182655.GA2849@raichu> <812c75e6-e77b-7559-3d0e-06085df10d0f@nomadlogic.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <812c75e6-e77b-7559-3d0e-06085df10d0f@nomadlogic.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Tue, 11 Sep 2018 00:41:22 -0000 On Mon, Sep 10, 2018 at 12:48:56PM -0700, Pete Wright wrote: > > > On 9/10/18 11:26 AM, Mark Johnston wrote: > > Hi, > > > > Support for boot-time loading of Intel microcode updates has landed in > > the kernel in r337715, and in the sysutils/devcpu-data port as of 1.20. > > I'd like to solicit some testing of the feature ahead of 12.0. > > Hey there Mark, > So I've just tested this on a kabylake system running a kernel/world > from Sept 7th which I believe is recent enough. > > After updating /boot/loader.conf as per your email I am not sure if any > microcode updates are being applied.  I'm not seeing any messages > regarding firmware updates being applied in the dmesg buffer.  Right, we currently print something only if an update was configured but failed to apply. We should probably print something either way, perhaps only if the kernel is booted with -v. > running x86info results in the following: > > $ sudo kldload -n cpuctl && sudo x86info -a | grep Micro > Microcode version: 0x000000000000008e > > this is after rebooting with the updated loader.conf as well as running > the rc script by hand.  i didn't think to compare the output of x86info > before running the rc script, i can do that later today. Thanks. If the boot-time update succeeded, the rc script should have been a no-op. Can you check for "updating cpu /dev/cpuctl..." messages in /var/log/messages? That would indicate that the rc script applied an update, which would imply that the boot-time update failed somehow. > for reference here is my dmesg: > https://gist.github.com/nomadlogic/bfc54315b97d374a7818d29bfc93223e