From owner-freebsd-stable@freebsd.org  Wed Feb 17 10:28:45 2021
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9864C53AC70
 for <freebsd-stable@mailman.nyi.freebsd.org>;
 Wed, 17 Feb 2021 10:28:45 +0000 (UTC)
 (envelope-from doralitze@chaotikum.org)
Received: from mail.chaotikum.net (magrathea.chaotikum.net [138.201.66.177])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4DgYwD5Trhz55H6;
 Wed, 17 Feb 2021 10:28:44 +0000 (UTC)
 (envelope-from doralitze@chaotikum.org)
Received: from cryingsilvertomb.technikradio.org
 (pd9e04731.dip0.t-ipconnect.de [217.224.71.49])
 by mail.chaotikum.net (Postfix) with ESMTPSA id B6EAA1543338;
 Wed, 17 Feb 2021 11:28:28 +0100 (CET)
Subject: Re: Microcode update prevents boot
To: Konstantin Belousov <kostikbel@gmail.com>,
 Mark Johnston <markj@freebsd.org>
Cc: freebsd-stable@freebsd.org
References: <a7a76dc2-dcf6-7d3a-00ac-a8474126a30d@chaotikum.org>
 <YCm9XZLnJ6Uzrpc0@spy> <YCoJnJ2xu12HvUFD@kib.kiev.ua>
From: Leon Christopher Dietrich <doralitze@chaotikum.org>
Message-ID: <82ebe645-c742-210d-68ce-ab07277ec591@chaotikum.org>
Date: Wed, 17 Feb 2021 11:28:26 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <YCoJnJ2xu12HvUFD@kib.kiev.ua>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Rspamd-Queue-Id: 4DgYwD5Trhz55H6
X-Spamd-Bar: /
Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none;
 spf=none (mx1.freebsd.org: domain of doralitze@chaotikum.org has no SPF policy
 when checking 138.201.66.177) smtp.mailfrom=doralitze@chaotikum.org
X-Spamd-Result: default: False [-0.21 / 15.00]; RCVD_TLS_ALL(0.00)[];
 RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[];
 FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3];
 TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000];
 MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[chaotikum.org];
 ARC_NA(0.00)[]; AUTH_NA(1.00)[];
 NEURAL_SPAM_SHORT(0.89)[0.885];
 SPAMHAUS_ZRD(0.00)[138.201.66.177:from:127.0.2.255];
 TO_MATCH_ENVRCPT_SOME(0.00)[];
 RBL_DBL_DONT_QUERY_IPS(0.00)[138.201.66.177:from];
 NEURAL_HAM_MEDIUM(-1.00)[-1.000];
 R_SPF_NA(0.00)[no SPF record];
 FREEMAIL_TO(0.00)[gmail.com,freebsd.org];
 FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[];
 MIME_TRACE(0.00)[0:+];
 ASN(0.00)[asn:24940, ipnet:138.201.0.0/16, country:DE];
 RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-stable];
 RECEIVED_SPAMHAUS_PBL(0.00)[217.224.71.49:received]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2021 10:28:45 -0000


>> Could you see
>> if the hang persists when boot-time ucode loading is enabled and
>> vm.pmap.di_locked=1 is configured?

Hi,

I can confirm that setting vm.pmap.di_locked=1 and enabling the loading
of the cpu microcode at the same time does not cause any trouble.
Unfortunately I didn't had the time to patch and compile a custom kernel
yet.

Leon Dietrich