Currently using the latest kernel (5.3.8-arch1-1).
kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aEventBlock: 32/16 (20190703/tbfadt-564)
kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/PmTimerBlock: 32/24 (20190703/tbfadt-564)
kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 16, using default 32 (20190703/tbfadt-669)
kernel: ACPI BIOS Warning (bug): Invalid length for FADT/PmTimerBlock: 24, using default 32 (20190703/tbfadt-669)
kernel: core: CPUID marked event: 'bus cycles' unavailable
kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
kernel: #2 #3 #4 #5 #6 #7
kernel: ata2.00: supports DRM functions and may not be fully accessible
kernel: ata2.00: supports DRM functions and may not be fully accessible
systemd-udevd[342]: /usr/lib/udev/rules.d/11-dm-lvm.rules:40 Invalid value for OPTIONS key, ignoring: 'event_timeout=180'
systemd-udevd[342]: /usr/lib/udev/rules.d/11-dm-lvm.rules:40 The line takes no effect, ignoring.
kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000518-0x000000000000051B (\GPBL) (20190703/utaddress-204)
kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x000000000000050C-0x000000000000050F (\GPLV) (20190703/utaddress-204)
kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000504-0x0000000000000507 (\GPIS) (20190703/utaddress-204)
kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000503 (\GPUS) (20190703/utaddress-204)
kernel: nvidia: loading out-of-tree module taints kernel.
kernel: nvidia: module license 'NVIDIA' taints kernel.
kernel: Disabling lock debugging due to kernel taint
kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019
kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
They seem more likely to happen after leaving the system logged off but idle over weekend (done so that I can ssh to it from other computers). Something else to note is that there was a power outage at the computer's location yesterday. However, I believe a freeze happened before the outage (could not ssh).
At this point, I do not want to spend more time on this problem. I will be replacing the computer. All the parts except PSU are fairly old anyway. Thanks for your inputs.
]]>I am not sure why the problem only started after a kernel update, however. I have been using this set of hardware for much longer.
]]>]]>Ironically, freezes seem more likely when idle.
Ironically, freezes seem more likely when idle.
]]>I noticed that, so far, all freezes happened when the system was not doing much in particular. I don't know enough about how kernels and OS work to make any intelligent diagnoses, but perhaps there is something wrong with how the kernel handles low processing load. Although this is a desktop PC, maybe some kind of power management went wrong?
]]>