watchdog: BUG: soft lockup - CPU#0 stuck for XXs!

[Poet]

Hi together,

I'd a problem this morning. I got the message CPU stuck for 82s. Here is a screenshot and a few log files:

Maybe this is a BIOS or driver problem?

journalctl

https://gist.github.com/hardcore/88a5de290c810517e6f61f453a6e1d58

screenshot of remote console:

dmesg log:

https://gist.github.com/hardcore/ed9b11e8f2beefe7041d098dd43793e0


I hope someone can help me

Thanks!

 

[Poet]

I have identify the VM: its a debian vm with pihole running.

I started the pihole vm (100) and proxmox crashed:

here is the proxmox journalctl:

Oct 26 16:43:42 proxmox pvedaemon[2413]: <root@pam> starting task UPID:proxmox:00004AB8:0001390B:6359479E:qmstart:100:root@pam:
Oct 26 16:43:42 proxmox pvedaemon[19128]: start VM 100: UPID:proxmox:00004AB8:0001390B:6359479E:qmstart:100:root@pam:
Oct 26 16:43:42 proxmox systemd[1]: Created slice qemu.slice.
Oct 26 16:43:42 proxmox systemd[1]: Started 100.scope.
Oct 26 16:43:42 proxmox systemd-udevd[19141]: Using default interface naming scheme 'v247'.
Oct 26 16:43:42 proxmox systemd-udevd[19141]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Oct 26 16:43:42 proxmox kernel: device tap100i0 entered promiscuous mode
Oct 26 16:43:42 proxmox systemd-udevd[19144]: Using default interface naming scheme 'v247'.
Oct 26 16:43:42 proxmox systemd-udevd[19144]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Oct 26 16:43:42 proxmox systemd-udevd[19144]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Oct 26 16:43:42 proxmox systemd-udevd[19141]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Oct 26 16:43:42 proxmox kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Oct 26 16:43:42 proxmox kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Oct 26 16:43:42 proxmox kernel: device fwpr100p0 entered promiscuous mode
Oct 26 16:43:42 proxmox kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Oct 26 16:43:42 proxmox kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Oct 26 16:43:42 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Oct 26 16:43:42 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Oct 26 16:43:42 proxmox kernel: device fwln100i0 entered promiscuous mode
Oct 26 16:43:42 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Oct 26 16:43:42 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Oct 26 16:43:42 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Oct 26 16:43:42 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Oct 26 16:43:42 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Oct 26 16:43:42 proxmox kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Oct 26 16:43:42 proxmox pvedaemon[2413]: <root@pam> end task UPID:proxmox:00004AB8:0001390B:6359479E:qmstart:100:root@pam: OK
Oct 26 16:43:46 proxmox pvedaemon[2413]: <root@pam> starting task UPID:proxmox:00004D50:00013A81:635947A2:vncproxy:100:root@pam:
Oct 26 16:43:46 proxmox pvedaemon[19792]: starting vnc proxy UPID:proxmox:00004D50:00013A81:635947A2:vncproxy:100:root@pam:
-- Boot 49c7e3c63abe4509b8adeb2c13b4e207 --

journalctl from pihole vm (100) after boot:

Oct 26 14:43:58 pihole systemd[828]: Startup finished in 47ms.
Oct 26 14:43:59 pihole snapd[601]: daemon.go:521: gracefully waiting for running hooks
Oct 26 14:43:59 pihole snapd[601]: daemon.go:523: done waiting for running hooks
Oct 26 14:43:59 pihole snapd[601]: overlord.go:504: Released state lock file
Oct 26 14:43:59 pihole snapd[601]: daemon stop requested to wait for socket activation
Oct 26 14:43:59 pihole systemd[1]: snapd.service: Deactivated successfully.
Oct 26 14:44:19 pihole systemd[1]: systemd-fsckd.service: Deactivated successfully.
Oct 26 14:44:24 pihole systemd-timesyncd[550]: Initial synchronization to time server [2620:2d:4000:1::3f]:123 (ntp.ubuntu.com).
Oct 26 14:44:24 pihole systemd[1]: systemd-timedated.service: Deactivated successfully.
Oct 26 14:45:31 pihole CRON[586]: pam_unix(cron:session): session closed for user root
Oct 26 14:45:42 pihole systemd-timesyncd[550]: Timed out waiting for reply from [2620:2d:4000:1::3f]:123 (ntp.ubuntu.com).
Oct 26 14:45:52 pihole systemd-timesyncd[550]: Timed out waiting for reply from [2620:2d:4000:1::41]:123 (ntp.ubuntu.com).
Oct 26 14:46:03 pihole systemd-timesyncd[550]: Timed out waiting for reply from [2620:2d:4000:1::40]:123 (ntp.ubuntu.com).
-- Boot ea3ab0005fb1481ebe8564a7a3cadf85 --

I hope someone can help