From nobody Sat Jun 07 06:19:11 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 4bDp1M1bSkz5xCK0 for ; Sat, 07 Jun 2025 06:19:19 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bDp1L6bgcz3SQN for ; Sat, 07 Jun 2025 06:19:18 +0000 (UTC) (envelope-from ianfreislich@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1034.google.com with SMTP id 98e67ed59e1d1-30e542e4187so2252684a91.3 for ; Fri, 06 Jun 2025 23:19:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749277152; x=1749881952; darn=freebsd.org; h=mime-version:subject:user-agent:references:in-reply-to:message-id :date:to:from:from:to:cc:subject:date:message-id:reply-to; bh=9hDOOfUlLQ2i0SBR4qbHIOjgPETTCgM2DZIWvrz74uU=; b=ftYoJ+tpDuGF2D0Y5ob89cfrjXZ5EkY+Rw+0k5eFoW/XmZGxvwKiw/lNOTpQpdDK5D DLqfsWBCIW4N2zvmbwJpbreLoe/P0kHs26h7yKRg4j8X0qhzevbXlWi+rG+BIaN6MqD0 chriunbiOmO8wX3pZMVyhh7LwIFOut5IJHywD9C+QU2TLOZcyyUyXRQX5Bm499bU8rfL efp7PytEWntPiWZktb5un5Dx/hpbxmv0DTAtMfZV21saQeZxAosJiWPvHE4QffYqzaJ3 5SczGTmPLeUn5nLyg+kKt0mcV6PMmK/m5IbQLIPi4+RNP1/A8OWO7mgSwvIsLf836RtM bWRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749277152; x=1749881952; h=mime-version:subject:user-agent:references:in-reply-to:message-id :date:to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9hDOOfUlLQ2i0SBR4qbHIOjgPETTCgM2DZIWvrz74uU=; b=jW6uQ9QvH+s+CFhfXhuSDC8MpPfHGqOvuYpJFwCs6S7qmoRXtSg7ZFJ3z3iysf6zhK W6MdjoirxxgQEngyeLis9wNW8NojlweCNThnAwa/gmjBXxSIYwGX3d4f6+zb+1fFaLLG Mz/T3mygf+Et8tJFEUduLyz2rM57f9aMXftBkoDkEF0gxKzwRn4dFyfKovp63Coa3JQ6 nii67pwFpb0CaCMtxp2FcD2bcnqnc31zbnIQN6rU5vKL/37UHO2AC596Zn4DC67ULiiW Cs+GDoZt/PBXSQD9wytIHw8boB6VuZ57VQ0+sDVadUVzq/Rhln5NmFDN1wimeHYoyEpP kyVQ== X-Forwarded-Encrypted: i=1; AJvYcCWIhph1V6rMu6s7c3FSy3H3UTAwuGSz3PePvg4QBG7HjKMSDTLnOaI8w9OjC5VwLdIfXOXq3GpLvA8UU9cvh0g=@freebsd.org X-Gm-Message-State: AOJu0YyAMMOYksn6XLe06banYzRFrgtf5ttw+712nqaOTC+QNv8f6hRj ucGPACQa8PUB1F03s5BfAdEwYLNJzQytsc35AUbFAxBMgOSzDutZnlqcKSiRzw== X-Gm-Gg: ASbGncvogZ81SAZHgbMb2/w/1CXVE0hO8sTIdwOdEp1rMvErqwgZVM/hU9J0El/PGDx aZkMp1ux8wcYhQYlOz91HtjL8llJpKPXJzJe6owmkbRjKukJS0/16hx8cvHUube2w3ii0WTiDAB 391GMiVctsEMV9E0E0X/EWWj14FdEjsUKx6qHEvi2udwGBG4YyzoBBJqG2JB4Z9DZP7KCwWhO1X BNEOOOBxRujUTuW8X6+VptoWE0lyvXneMREf4Sv1jj4fzrNevgtco7KWwgeJDyhOPUsWpbSpR9q UFs5zDSYhVlEbEel7zpIsMf8FVX6vdybTPHy+9xcdGu/f6b8qo0h+CpvkQ== X-Google-Smtp-Source: AGHT+IFXA7mLMqqO8rkCpuM10oK/YsmDYmcZqUlH+7AED/As5WUVaBel/VqEbYJeh+/grONa5N6BCw== X-Received: by 2002:a17:90b:540c:b0:313:27cc:69cd with SMTP id 98e67ed59e1d1-31346b29bbbmr11286700a91.12.1749277152118; Fri, 06 Jun 2025 23:19:12 -0700 (PDT) Received: from [192.168.1.105] ([172.92.92.146]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-31349f17bd2sm2229051a91.5.2025.06.06.23.19.11 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Fri, 06 Jun 2025 23:19:11 -0700 (PDT) From: Ian FREISLICH To: , Date: Sat, 07 Jun 2025 02:19:11 -0400 Message-ID: <197490b0f18.2762.64e08aff09ba5a21b2fc9010d26a90e5@gmail.com> In-Reply-To: <20250607074739.31a7116b@gema.dino.sk> References: <6530f044-486d-4128-9e23-ee03e6686aa9@yamagi.org> <20250128122345.74075269.25648751.10101138@dino.sk> <6024769d-1cac-439b-874d-c624112d30c9@gmail.com> <20250607074739.31a7116b@gema.dino.sk> User-Agent: AquaMail/1.55.1 (build: 105501552) Subject: Re: UFS bad inode, mangled entry on Alder Lake-N(100) 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 Content-Type: multipart/alternative; boundary="197490b109d9b627622d1370c" X-Rspamd-Queue-Id: 4bDp1L6bgcz3SQN 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:15169, ipnet:2607:f8b0::/32, country:US] This is a multi-part message in MIME format. --197490b109d9b627622d1370c Content-Type: text/plain; format=flowed; charset="us-ascii" Content-Transfer-Encoding: 8bit On June 7, 2025 01:47:56 freebsd-current@dino.sk wrote: > On Tue, 28 Jan 2025 15:33:30 -0500 > Ian FREISLICH wrote: > >> On 2025-01-28 06:23, Milan Obuch wrote: > > [ snip ] > >>> It looks like the right thing, in my case adding >>> vm.pmap.pcid_enabled=0 to /boot/loader.conf helps. I consider this >>> easier than installing port for microcode update... >>> >>> That being said, could someone add some more pro/cons for those two >>> approaches? >>> >>> Additionally, I am using M.2 SATA drive at the moment. While NVMe >>> drive worked to some extent, if fsck was necessary for some reason, >>> it was unpleasant - some 'waiting for nvme reset' event occured, >>> this led to nvme drive detach, and the only way to fix it was >>> unscrew the drive, put it in USB-NVMe converter, do fsck via USB >>> drive, then mount it back into box... not acceptable. >> >> I chose microcode but that was hard to do because I only have one >> nvme slot and the installer panicked trying to install the package at >> the final part of the install. I had to install onto an SD and then >> use another FreeBSD install to do a pkg chroot install onto that >> temporary media and then use that to boot with the firmware update >> and chroot install the firmware and edit loader.conf on the nvme. >> >> The microcode update fixed it for me. I inferred from reading that >> enable PCID might have a performance advantage. > > Well, I run with microcode update and NVMe on my Alder Lake box with no > problem. Yesterday, however, the symptoms were back - bad inode error > for filesystem, fsck necessary. Probably some data loss... (not a big > problem, this was still device under test, and I can easily get the > somewhat important things from drive) > > What may be relevant is it happened after system upgrade to more recent > 14.3-STABLE from some a bit older 14.3-PRERELEASE, but I think > microcode update binary is OS independent, or is there some dependency? > > I am going to try reinstall with disabled PCID and test it again. I'm running 15.0-CURRENT #24 main-n277779-2a5841795fb7: Fri Jun 6 22:06:35 EDT 2025 and rebuilding all my ports without issue. I'm on the latest microcode (0x1d) as well. Ian --197490b109d9b627622d1370c Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
On June 7, 2025 01:47:56= freebsd-current@dino.sk wrote:

On Tue, 28 Jan 2025 15:33:30 -0500
Ian FREISLICH <ianfreislich@gmail.com> wrote:

On 2025-01-28 06:23, Milan Obuch wrote:

[ snip ]

It looks like the right thing, in my case adding
vm.pmap.pcid_enabled=3D0 to /boot/loader.conf helps. I co= nsider this
easier than installing port for microcode update...

That being said, could someone add some more pro/cons for= those two
approaches?

Additionally, I am using M.2 SATA drive at the moment. Wh= ile NVMe
drive worked to some extent, if fsck was necessary for so= me reason,
it was unpleasant - some 'waiting for nvme reset' event o= ccured,
this led to nvme drive detach, and the only way to fix it= was
unscrew the drive, put it in USB-NVMe converter, do fsck = via USB
drive, then mount it back into box... not acceptable. &nb= sp;

I chose microcode but that was hard to do because I only = have one
nvme slot and the installer panicked trying to install th= e package at
the final part of the install. I had to install onto an S= D and then
use another FreeBSD install to do a pkg chroot install on= to that
temporary media and then use that to boot with the firmwa= re update
and chroot install the firmware and edit loader.conf on t= he nvme.

The microcode update fixed it for me. I inferred from rea= ding that 
enable PCID might have a performance advantage.


Well, I run with microcode update and NVMe on my Alder La= ke box with no
problem. Yesterday, however, the symptoms were back - bad= inode error
for filesystem, fsck necessary. Probably some data loss..= . (not a big
problem, this was still device under test, and I can easi= ly get the
somewhat important things from drive)

What may be relevant is it happened after system upgrade = to more recent
14.3-STABLE from some a bit older 14.3-PRERELEASE, but I = think
microcode update binary is OS independent, or is there so= me dependency?

I am going to try reinstall with disabled PCID and test i= t again.

I'm running 15.0-CURRENT #24 main-n277779-2a5841795fb7: Fri Jun 6 22:06= :35 EDT 2025
and rebuilding all my ports without iss= ue. I'm on the latest microcode (0x1d) as well.

=
Ian
--197490b109d9b627622d1370c--