On 2022-07-17, Tobias Fiebig <tob...@reads-this-mailinglist.com> wrote: > Also, the voltages do not necessarily look overly healthy... but that might > just be a fluke.
Sensors sometimes give incorrect values depending on how the motherboard is designed - they may use e.g. different values of resistor which means they may need some scaling or offset to be applied. There's no way to provide the information needed to the OS with these simple sensor ICs. They may be displayed correctly in the BIOS setup pages somewhere. > systat : > 1 users Load 0.81 0.66 0.60 xxxxxxx.xxxxxxxxxxx 22:46:56 > > memory totals (in KB) PAGING SWAPPING Interrupts real virtual free in out in > out total Active ops clock All pages acpi0 inteldrm Proc:r d s w Csw Trp Sys > Int Sof Flt forks ehci0 fkppw em0 fksvm em2 . %Int . %Spn . %Sys . %Usr . > %Idle pwait em5 >| | | | | | | | | | | relck ehci1 > rlkok ahci0 > noram > Namei Sys-cache Proc-cache No-cache ndcpy Calls hits % hits % miss % fltcp > zfod cow Disks sd0 fmin seeks ftarg xfers itarg speed wired sec pdfre pdscn > pzidl IPKTS kmape OPKTS This is mangled and doesn't have any of the actual information, just the names. You nees to wait for the numbers to be filled in on the first update. It may be easier to copy if you hit p to pause the display. If it's an OS problem rather than a hardware problem there might be something useful in "netstat -m", "vmstat -m", or "systat mbuf". Currently I don't think there is enough information to tell whether it's more likely to be OS or hardware. It would probably be worth running a few cycles of memtest86 to see if that shows any problems (either reported errors or freezes). -- Please keep replies on the mailing list.
