Has anyone noticed stability issues with kernel 6.5.13-3?

dw-cj

New Member
Apr 9, 2024
1
0
1
This is a long shot, but I figured I'd put it out there to see if anyone else is having the same issues.

I run a 6 node cluster, it's been running for 6 months or so with no issues on Proxmox VE 8. All nodes are using AMD EPYC 7713, 512GB / 1TB RAM, and Gigabyte MZ32-AR0 boards. About 2 weeks ago, I ran apt upgrade on all of the nodes and rebooted them all to load the updated kernel. I frequently update the nodes via apt, but this was the first time in a while that I had rebooted them, so a new kernel (6.5.13-3) was loaded.

Since upgrading these, I've had the same issue on 5 out of my 6 nodes. The issue is very strange, and random, but essentially the node just completely 'hangs' until the ipmi watchdog reboots it because it's timing out (or I force reboot it). dmesg shows no logs anytime before the reboot, and I can't find any other logs anywhere else. It doesn't seem to coincide with load at all, it's happened on nodes with 10% CPU / RAM used, and ones that are almost full.

Anyway, I'm sure this is some deeper hardware bug, but was just wondering if anyone else had issues with this specific kernel version. This is the only significant change that I would have guessed would cause something like this (or maybe the pve-firmware update also??). Before loading this kernel, I hadn't experienced anything like this. I updated them to 6.5.13-5 today, but debating updating to the 6.8 branch.
 
Hi,

I also had random freezes every 2-3 weeks with 6.5.13-3. Today I updated to 6.5.13-5. Fingers crossed.
 
Have you considered that this might be caused by random moderate IO?

Do you have a mix of SCSI Controller types?

If using the VirtIO SCSI Single adapter, what Async IO option are you using? Are you using iothread=1 too?

If this seems applicable, you may want to consider this bug report.
 
Have you considered that this might be caused by random moderate IO?

Do you have a mix of SCSI Controller types?

If using the VirtIO SCSI Single adapter, what Async IO option are you using? Are you using iothread=1 too?

If this seems applicable, you may want to consider this bug report.
I'm using VirtIO SCSI single with iothread=1 on all VMs (Windows, FreeBSD and Linux).
1714571681528.png

Does the bug also affects the host or only VMs?
My issue is that the complete host is crashing / is not responding.
 
Perhaps even:

You can possibly disable the writeback cache too. ==> You should probably disable the writeback cache too.
 
Just to be clear, the crashing and rebooting VMs (sometimes with chkdsk at boot) lead to a snowball of additional IO, which eventually (relatively quickly now I think about it) cause the host to crash or hang. In my case, I was attempting to mitigate the host crashing by shutting down VMs to bare minimum and immediately hard stopping unresponsive VMs. This was somewhat effective but obviously not a workable solution.
 
  • Like
Reactions: ksb

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!