Re: UFS problem?

On Wed, 26 Mar 2025 11:28:15 +0100
Milan Obuch <freebsd-questions@dino.sk> wrote:

> On Wed, 26 Mar 2025 10:56:05 +0100
> Mats Mellstrand <mats@exmandato.se> wrote:
> 
> > Hi
> > 
> > Hardware:
> > 
> > CPU: Intel(R) N100 (806.40-MHz K8-class CPU)
> >   Origin="GenuineIntel"  Id=0xb06e0  Family=0x6  Model=0xbe
> > Stepping=0
> > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> > Features2=0x7ffafbbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
> > AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM> AMD
> > Features2=0x121<LAHF,ABM,Prefetch> Structured Extended
> > Features=0x239ca7eb<FSGSBASE,TSCADJ,BMI1,AVX2,FDPEXC,SMEP,BMI2,ERMS,INVPCID,NFPUSG,PQE,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,SHA>
> > Structured Extended
> > Features2=0x98c007bc<UMIP,PKU,OSPKE,WAITPKG,GFNI,VAES,VPCLMULQDQ,RDPID,MOVDIRI,MOVDIR64B>
> > Structured Extended
> > Features3=0xfc184410<FSRM,MD_CLEAR,IBT,IBPB,STIBP,L1DFL,ARCH_CAP,CORE_CAP,SSBD>
> > XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
> > IA32_ARCH_CAPS=0x180fd6b<RDCL_NO,IBRS_ALL,SKIP_L1DFL_VME,MDS_NO,TAA_NO>
> > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state
> > invariant, performance statistics real memory  = 8589934592 (8192
> > MB) avail memory = 7981867008 (7612 MB) ….
> > 
> > As harddisk I use a NVME probed as:
> > nvme0: Allocated 127MB host memory buffer
> > 
> > When trying to install packages I receive:
> > 
> > Mar 26 09:42:03 xxx kernel: UFS /dev/nda0p2 (/) cg 75: bad magic
> > number 0x0 should be 0x90255 Mar 26 09:42:03 xxx kernel: /: bad dir
> > ino 6169868 at offset 0: mangled entry Mar 26 09:44:18 xxx kernel:
> > /: bad dir ino 6089939 at offset 0: mangled entry
> >   
> 
> Hi,
> 
> this issue is already known. You hit a CPU bug. It is discussed in
> thread titled 'UFS bad inode, mangled entry on Alder Lake-N(100)' on
> freebsd-current mailing list, starting at January 27th, 2025.
> 
> Basically, there are two sollutions - add a line
> 
> vm.pmap.pcid_enabled=0
> 
> to /boot/loader.conf file and reboot. Alternatively, you can install
> sysutils/cpu-microcode port and do CPU microcode update.
>

Adding pointer to discussion thread mentioned above, for more details:
https://lists.freebsd.org/archives/freebsd-current/2025-January/006981.html

Regards,
Milan