On Proxmox GUI, there is always a Help button that you can click that will open a link to internal docs. Alternatively you can visit https://pve.proxmox.com/pve-docs/Not sure what you mean by this? The wiki is out of date yes but are you saying there is more up to date info in the actual Proxmox server help files?
Nope! I’ve left the c-states as is and haven’t had another crash even though I’ve experimented both with putting the suspect node under load and completely free for prolonged periods of time... still no crash...No I didn't because I'm so happy that it works have you tried disabling your c-states?
I switched back do 4.14.18-17-pve just to try it out. I still cannot use netconsole because it's a dedicated server at a hoster and i dont wan't to rent another one with vlan...I’ve had no problems for the last few weeks and, just before reading this post, I updated to the following kernel.
Linux pve-host1 4.15.18-18-pve #1 SMP PVE 4.15.18-44 (Wed, 03 Jul 2019 11:19:13 +0200) x86_64 GNU/Linux
I’ve got netconsole running in case of any similar kernel panics and will post any results here but my setup has been solid for the last few weeks...
(Reading database ... 91643 files and directories currently installed.) Preparing to unpack .../kdump-tools_1%3a1.6.5-1_amd64.deb ... Unpacking kdump-tools (1:1.6.5-1) ... Setting up kdump-tools (1:1.6.5-1) ... Creating config file /etc/default/kdump-tools with new version dpkg: error processing package kdump-tools (--configure): installed kdump-tools package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.8.5-2) ... Processing triggers for systemd (241-5) ... Errors were encountered while processing: kdump-tools E: Sub-process /usr/bin/dpkg returned an error code (1)
I can’t really recall now. I was only getting crashes every so often on 5.4 and after I put netconsole on, I didn’t see any further crashes (I’m not suggesting netconsole affected this), even after I did the kernel upgrade to the last 5.4 version I mentioned above. I do recall doing some BIOS updates around the time so perhaps that could have improved the situation?