Recent content by KLez

Thanks for all the tips, but after long tries with no success i ended up by re-installing my Proxmox Server and restored all the LXC and VMs from backups. Sorry, that i have not found another solution for the problem.

Done, but for me there is no really useful information. Unfortunately the problem grows up, so that i can not install any new kernels :( The following package was automatically installed and is no longer required: proxmox-kernel-7.0.6-2-pve-signed Use 'apt autoremove' to remove it. Summary...

Sure. Here it is: root@pve:~# cat /etc/kernel/postrm.d/zz-proxmox-boot #! /bin/sh # shellcheck disable=SC2317 # Don't warn about unreachable commands in this file set -e # adapted from '/etc/kernel/postinst.d/zz-update-grub and # /usr/lib/kernel/install.d/90-loaderentry.install, see also #...

unfortunately this had no effect :( This is the output of your first command: root@pve:~# bash -x /etc/kernel/postrm.d/zz-proxmox-boot 6.17.13-13-pve /boot/vmlinuz-6.17.13-13-pve + set -e + command -V systemd-detect-virt + systemd-detect-virt --quiet --container + trap cleanup EXIT INT TERM...

Hello. I have some problems uninstalling an old kenel package proxmox-kernel-6.17.13-13-pve-signed apt autoremove shows this: root@pve:/# apt autoremove REMOVING: proxmox-kernel-6.17.13-13-pve-signed Summary: Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading...

Kernel 6.14.11-4-pve too. Seriously... Is there no way to do something against this bug? Reporting it to the Kernel Team maybe? It has nothing to do with Proxmox i guess.

Kernel 6.14.11-3-pve still has the problem.

Wow! No Shit? U wrote this post to publish a dirty workaround which was posted here 10.000 times already?

Is there a chance to open a support ticket @ Proxmox? Because it seems noone is working on this issue... I thought this would be a bug in a single kernel version, but there were many kernels released since 6.8.12-8-pve and ALL of them have this problem. Upgrading to VE 9 is no solution too.

You can downgrade the kernel to 6.8.12-8-pve. For me this is the best option actually. proxmox-boot-tool kernel pin 6.8.12-8-pve --next-boot

Problem still occurs with newest Kernel 6.8.12-12-pve... Please fix this shit!

As i said already: Disable offloading is NOT A FIX! It is a dirty workaround for a problem which should not exist!

This script is just a workaround but not a real solution!

Please check the syslog. If there are no "Detected Hardware Unit Hang" error messages in it, then u have another problem and u should open an own specific thread. This one here is about the "e1000 driver hang" problem only. The problem seems to relate to newer kernel versions than 6.8.12-8-pve...

I have the "Device Hang" issue too... Running on an older Intel NUC. Unfortunately i dont know after which update this problem came up. I realised it, as the NUC was not reachable anymore. I had to reconnect the ethernet cable to restore the network connection. I tried downgrading to...