[SOLVED] Probleme mit GIGABYTE MW34-SP0?

[Poet]

Problem mit neuem Kernel gelöst:

https://forum.proxmox.com/threads/probleme-mit-gigabyte-mw34-sp0.117159/#post-507618






Hi zusammen,

mein Server läuft idR nie länger als 24 Stunden. Ich benutze ein relativ neues Board: GIGABYTE MW34-SP0 mit ECC RAM.
Der RAM war im Test unauffällig.

Heute habe ich Windows 11 installiert und der Server ist wieder komplett gestorben.
Hier das Log journalctl:

Eigentlich sind nur die letzten 3 Zeilen wichtig!

Oct 27 12:40:03 proxmox kernel: x86/split lock detection: #AC: kvm/997009 took a split_lock trap at address: 0xfffff807372152df
Oct 27 12:42:42 proxmox pveproxy[2456]: worker 988996 finished
Oct 27 12:42:42 proxmox pveproxy[2456]: starting 1 worker(s)
Oct 27 12:42:42 proxmox pveproxy[2456]: worker 1294545 started
Oct 27 12:42:42 proxmox pveproxy[1294541]: got inotify poll request in wrong process - disabling inotify
Oct 27 12:43:18 proxmox kernel: x86/split lock detection: #AC: kvm/997010 took a split_lock trap at address: 0xfffff8061e6152df
Oct 27 12:44:14 proxmox pvedaemon[997984]: VM 103 qmp command failed - VM 103 qmp command 'guest-shutdown' failed - got timeout
Oct 27 12:44:14 proxmox pvedaemon[997984]: VM quit/powerdown failed
Oct 27 12:44:14 proxmox pvedaemon[988786]: <root@pam> end task UPID:proxmox:000F3A60:00601ED8:635A5EA6:qmshutdown:103:root@pam: VM quit/powerdown failed
Oct 27 12:48:03 proxmox pvedaemon[988786]: <root@pam> update VM 103: -net0 virtio=02:FC:EB:6B:6C:AB,bridge=vmbr0,firewall=1,link_down=1
Oct 27 12:48:27 proxmox pvedaemon[997608]: <root@pam> successful auth for user 'root@pam'
-- Boot a8d2026a363f44809b860da7ab08d684 --

Hier noch ganz frische Logs:

root@proxmox:~#
Message from syslogd@proxmox at Oct 27 13:34:46 ...
 kernel:[ 2533.989024] NMI watchdog: Watchdog detected hard LOCKUP on cpu 6

Message from syslogd@proxmox at Oct 27 13:34:46 ...
 kernel:[ 2535.551303] NMI watchdog: Watchdog detected hard LOCKUP on cpu 3

Message from syslogd@proxmox at Oct 27 13:34:46 ...
 kernel:[ 2536.301251] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0

Message from syslogd@proxmox at Oct 27 13:34:46 ...
 kernel:[ 2540.467210] watchdog: BUG: soft lockup - CPU#14 stuck for 26s! [kvm:23977]

Message from syslogd@proxmox at Oct 27 13:34:46 ...
 kernel:[ 2548.459039] watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [kvm:23975]

Message from syslogd@proxmox at Oct 27 13:35:02 ...
 kernel:[ 2552.221736] NMI watchdog: Watchdog detected hard LOCKUP on cpu 14

Message from syslogd@proxmox at Oct 27 13:35:02 ...
 kernel:[ 2564.454699] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! [kworker/8:1:209]

Message from syslogd@proxmox at Oct 27 13:35:14 ...
 kernel:[ 2576.458443] watchdog: BUG: soft lockup - CPU#10 stuck for 48s! [kvm:23975]

Message from syslogd@proxmox at Oct 27 13:35:30 ...
 kernel:[ 2592.454103] watchdog: BUG: soft lockup - CPU#8 stuck for 49s! [kworker/8:1:209]

Message from syslogd@proxmox at Oct 27 13:35:42 ...
 kernel:[ 2604.457847] watchdog: BUG: soft lockup - CPU#10 stuck for 74s! [kvm:23975]

Message from syslogd@proxmox at Oct 27 13:35:58 ...
 kernel:[ 2620.453506] watchdog: BUG: soft lockup - CPU#8 stuck for 75s! [kworker/8:1:209]

Message from syslogd@proxmox at Oct 27 13:36:10 ...
 kernel:[ 2632.457251] watchdog: BUG: soft lockup - CPU#10 stuck for 100s! [kvm:23975]
client_loop: send disconnect: Broken pipe

Hier noch das dmesg Log:

https://gist.github.com/hardcore/9500a2672c4b51e15be39124afe4258d (leider zu lange für einen Post hier im Forum)

Vielen Dank

 

[Poet]

Ich habe das Problem gefixt, indem ich den aktuellen 6.x Kernel installiert habe.

Es gibt zum Glück ein Github Repo, welches die Installation und Konfiguration übernimmt:
https://github.com/fabianishere/pve-edge-kernel

Der Server läuft seitdem nun über eine Woche ohne Probleme. Davor gab es mindestens alle 6-7 Stunden Kernel Panics.