Search results

Fix which helped in /etc/default/grub file change following line GRUB_CMDLINE_LINUX_DEFAULT="quiet" to GRUB_CMDLINE_LINUX_DEFAULT="quiet rcu_nocbs=0-11 processor.max_cstate=1" rcu_nocbs=0-N processor.max_cstate=1 (where N is the number of CPUs you have minus one.) after execute...

For me it looks like complete some kind of complete I/O fail (not totally freeze). 1) Any way to dump kernel panic logs to some remote host? In case of such failure? 2) Some king of watchdog to automatically reboot server in case of unresponsiveness?

Thanks for effort @guruevi but to (at least for proxmox 8.2.4 aka debian 12.7) /var/log doesn't contains such files: ryzen-vtn-proxmox:/var/log# ls -altr total 345 drwxr-xr-x 2 root root 2 May 5 2023 lxc drwxr-xr-x 2 root root 2 May 7 2023...

dmesg - messages since last boot up. I cannot check prev. dmesg and cannot get to console when it "freezes" /var/log/messages - is missing. As i understand now days `journalctl` - fills his place. Sep 16 05:25:29 ryzen-vtn-proxmox pvestatd[2099]: status update time (12.891 seconds) Sep 16...

Previously i was running i7-3770 and it was working 24/7 for 365 days a year. No issues with uptime unless i decided to update or reboot it. As i use this host for my-lab maximum memory of 32GB was not enough for me. I upgraded hardware to Ryzen 5 PRO 4650G with 128 GB ECC (4x32 GB Kingston)...