From nobody Mon Jan 27 18:12:08 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Yhc2g3Ykrz5m3NB for ; Mon, 27 Jan 2025 18:12:27 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from mail2.pluspunkthosting.de (mail2.pluspunkthosting.de [217.29.33.228]) (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 4Yhc2f6JkSz3nVk for ; Mon, 27 Jan 2025 18:12:26 +0000 (UTC) (envelope-from pmh@hausen.com) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (87.138.185.145) by mail2.pluspunkthosting.de (Axigen) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA id 123052; Mon, 27 Jan 2025 19:12:18 +0100 Content-Type: text/plain; charset=us-ascii List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: UFS bad inode, mangled entry on Alder Lake-N(100) From: "Patrick M. Hausen" In-Reply-To: <20250127183803.23683162.25648751.59233766@dino.sk> Date: Mon, 27 Jan 2025 19:12:08 +0100 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20250127183803.23683162.25648751.59233766@dino.sk> To: Milan Obuch X-Mailer: Apple Mail (2.3776.700.51) X-Rspamd-Queue-Id: 4Yhc2f6JkSz3nVk X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16188, ipnet:217.29.32.0/20, country:DE] Hi all, > Am 27.01.2025 um 18:38 schrieb Milan Obuch : >=20 > On Mon, 27 Jan 2025 12:10:43 -0500 > Ian FREISLICH wrote: >=20 >> I recently bought one of those mini-pc firewall devices (Topton 12th >> gen N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg >> or buildkernel without getting a slew of these messages, inode number >> changing and a panic shortly thereafter. >>=20 >> kernel: /: bad dir ino 4567815 at offset 0: mangled entry >>=20 >> [...] >=20 > Just a "me too" message - I did test another device with the same CPU, > mine is SZBOX. > [...] In the OPNsense community we had frequent reports of UFS corruption with Alder Lake and Raptor Lake CPUs. Lots of embedded devices of varying manufacture and quality in use, apparently. The problems were fixed in all cases that I am aware of by applying the = current Intel microcode update (sysutils/cpu-microcode). Make sure to activate = early loading via /boot/loader.conf(.local). HTH, kind regards, Patrick=