[fixed] Random reboots on a new Alder Lake System

[nullinger]

Hi,

i am planning to replace my current Kaby-Lake-based installation with a new Alder-Lake based system. Alder Lake is very new, so i expected some sort of trouble and made preparations so i can instantly switch back to the "old" system.

Steps:
- made a config backup of the old system (22.1.5 ufs)
- installed the new system with 22.1.5 zfs
- manually edited the backup file to represent new interface names (igb to re)
- imported the edited backup file
- fixed plugins and packages
- did health checks

So far, the system is up and running blazing fast without any problems. Some ACPI errors while booting, but they look negligible.

But after a while, after 20-30 hours uptime, the system reboots randomly without any trace in the logs or /var/crash. Usually that would indicate some hardware problems, but after intense tests i think the problem must be somewhere else. the system is 24 hours memtest-stable, Windows and a current Debian 11 don't show these problems. So, i am well aware that alder lake is very new and that running a BSD or Linux OS may be a bit gambling, so this thread is more about ideas and discussion and not about support.

I tried different things, like disabling powersaving mechanisms in UEFI, but currently without success. Tomorrow i'll connect a KVM switch to the machine, maybe i can record the screen in the moment of a reboot.

system info:

Intel i5-12400 on Gigabyte B660M Chipset
2x 8GB DDR4-3200 RAM (via XMP)
1x 250 GB Samsung 970 Evo Plus NVME SSD
1x Realtek 2.5 GbE onboard NIC
1x 4-Port 1 GbE Realtek NIC
Maybe there is a newer kernel or something like that i can try.

[nullinger]

fixed by replacing the quad port realtek nic with an intel counterpart. System is up and running for 7 days without any problems.

The power usage is with 33W idle quite bad with freebsd, the same system runs with 19W idle on Windows 11. Let's see with 22.7 / FreeBSD14 ;)

Only the 2x25 GbE fibre card is missing now.

[GPz1100]

Did you ever get your power usage issue figured out?