Hm ... I monitor this thread since some years (!!) now and the intel platform has this issue since ages and it is in the Linux Kernel or in the Intel network drivers in the kernel!! And it is there for ages.
Yes it sometimes hit and sometimes not for ages, so I assume noone really knows how systems get affected after an update that worked a long time before - or it was just that short that you never noticed it before
I just wonder why there are expectations that Proxmox staff can fix this?
Yes it sometimes hit and sometimes not for ages, so I assume noone really knows how systems get affected after an update that worked a long time before - or it was just that short that you never noticed it before

I just wonder why there are expectations that Proxmox staff can fix this?