Re: UFS bad inode, mangled entry on Alder Lake-N(100)

From: Ian FREISLICH <ianfreislich_at_gmail.com>
Date: Mon, 27 Jan 2025 20:23:51 UTC 
<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    All,<br>
    <br>
    I can confirm that the microcode loaded early fixes the issue.<br>
    <br>
    Ian<br>
    <br>
    <div class="moz-cite-prefix">On 2025-01-27 13:12, Patrick M. Hausen
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:B05C0A41-76C0-4BFF-8A26-0E49440B820C@hausen.com">
      <pre wrap="" class="moz-quote-pre">Hi all,

</pre>
      <blockquote type="cite">
        <pre wrap="" class="moz-quote-pre">Am 27.01.2025 um 18:38 schrieb Milan Obuch <a class="moz-txt-link-rfc2396E" href="mailto:freebsd-current@dino.sk">&lt;freebsd-current@dino.sk&gt;</a>:

On Mon, 27 Jan 2025 12:10:43 -0500
Ian FREISLICH <a class="moz-txt-link-rfc2396E" href="mailto:ianfreislich@gmail.com">&lt;ianfreislich@gmail.com&gt;</a> wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="" class="moz-quote-pre">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.

kernel: /: bad dir ino 4567815 at offset 0: mangled entry

[...]
</pre>
        </blockquote>
        <pre wrap="" class="moz-quote-pre">
Just a "me too" message - I did test another device with the same CPU,
mine is SZBOX.
[...]
</pre>
      </blockquote>
      <pre wrap="" class="moz-quote-pre">
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
</pre>
    </blockquote>
    <br>
  </body>
</html>