From owner-freebsd-stable@freebsd.org Sun Feb 14 13:01:24 2021 Return-Path: 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 3D3A552F0BC for ; Sun, 14 Feb 2021 13:01:24 +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 4DdnRk6ZQ5z3H3P for ; Sun, 14 Feb 2021 13:01:22 +0000 (UTC) (envelope-from doralitze@chaotikum.org) Received: from [10.0.8.169] (pd9e04731.dip0.t-ipconnect.de [217.224.71.49]) by mail.chaotikum.net (Postfix) with ESMTPSA id B77A81542E76 for ; Sun, 14 Feb 2021 14:01:14 +0100 (CET) To: freebsd-stable@freebsd.org From: Leon Dietrich Subject: Microcode update prevents boot X-Pep-Version: 2.0 Message-ID: Date: Sun, 14 Feb 2021 14:01:14 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 Content-Language: en-US X-Rspamd-Queue-Id: 4DdnRk6ZQ5z3H3P 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 [-2.09 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_ATTACHMENT(0.00)[]; TO_DN_NONE(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.991]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[138.201.66.177:from]; ASN(0.00)[asn:24940, ipnet:138.201.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[217.224.71.49:received]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/mixed,text/plain,application/pgp-keys]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[138.201.66.177:from:127.0.2.255]; DMARC_NA(0.00)[chaotikum.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Feb 2021 13:01:24 -0000 Hi there, I already worked around the issue myself. I'm just writing this here in case someone else may have the same issue and is seeking an answer. I recently upgraded the intel cpu microcode update package. Since then the boot process hang at the stage where the other cpu cores where enabled (shortly after enabling acpi). In order to resolve the issue one has to boot in safe mode (not single user mode!) and comment (or remove) the lines enabling the cpu microcode update on boot in /boot/loader.conf. One can and should reboot then. After making these changes the system boots again and all cores are started and SMT works as well. One should note that one's not running the newer microcode (including some security-) fixes. Having microcode_update_enable=3D"YES" in /etc/rc.conf doesn't prevent booting and does not cause noticeable instability. For reference: Im running FreeBSD 12.1 on a supermicro embedded board with intel xeon E3-1585L v5 cpus. I hope someone will find this info useful. Leon Dietrich