On 2025-01-28 06:23, Milan Obuch wrote:
On Mon, 27 Jan 2025 19:28:28 +0100
Yamagi wrote:
Hi,
sounds like the Alder Lakes PCID bug in N100 flavor. On the small
cores the INVLPG instruction is broken, failing to flush all
(global?) TLP entries leading to cache corruption. FreeBSD has a work
On Mon, 27 Jan 2025 19:28:28 +0100
Yamagi wrote:
> Hi,
>
> sounds like the Alder Lakes PCID bug in N100 flavor. On the small
> cores the INVLPG instruction is broken, failing to flush all
> (global?) TLP entries leading to cache corruption. FreeBSD has a work
> around for
> that:
> https://cgit
All,
I can confirm that the microcode loaded early fixes the issue.
Ian
On 2025-01-27 13:12, Patrick M. Hausen
wrote:
Hi all,
Am 27.01.2025 um 18:38 schrieb Milan Obuch :
On Mon, 27 Jan 2025 12:10:43 -0500
Ian FREISLICH
It might be timing related. UFS with a custom kernel (previously
GENERIC) is less prone and I got these building world on an microSD:
Jan 27 12:35:54 router kernel: /: inode 1286411: check-hash failed
Jan 27 12:35:54 router syslogd: last message repeated 1 times
Jan
Hi,
sounds like the Alder Lakes PCID bug in N100 flavor. On the small cores
the INVLPG instruction is broken, failing to flush all (global?) TLP
entries leading to cache corruption. FreeBSD has a work around for that:
https://cgit.freebsd.org/src/commit/?id=cde70e312c3fde5b37a29be1dacb7fde9a4
Hi all,
> Am 27.01.2025 um 18:38 schrieb Milan Obuch :
>
> On Mon, 27 Jan 2025 12:10:43 -0500
> Ian FREISLICH wrote:
>
>> 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 gettin
On Mon, 27 Jan 2025 12:10:43 -0500
Ian FREISLICH wrote:
> 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 shor
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 di
