Minisforum ms-01 i9-13900H 96GB with Proxmox
- Thread starter homelabenthusiast
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I have the same issue with the system freezing while running Proxmox.I have the 13900H Version running Proxmox VE 8.2.2 with Microcode 0x411c disabled C States and enabled efficiency cores. The system passed memtest86. Occasionally the system is able to save kernel logs to journald before freezing.
I recently updated the microcode to 0x4121 and I am now waiting for the next crash. I'll report back.
Code:
Apr 14 14:51:19 pve kernel: BUG: Bad page map in process pvestatd pte:80000002d85e5865 pmd:1593fd067`
`Apr 14 14:51:19 pve kernel: addr:0000615e50745000 vm_flags:08100073 anon_vma:ffff96f5117bc068 mapping:0000000000000000 index:615e50745`
`Apr 14 14:51:19 pve kernel: file:(null) fault:0x0 mmap:0x0 read_folio:0x0`
`Apr 14 14:51:19 pve kernel: CPU: 10 PID: 1526759 Comm: pvestatd Tainted: P D O 6.5.13-3-pve #1`
`Apr 14 14:51:19 pve kernel: Hardware name: Micro Computer (HK) Tech Limited Venus Series/AHWSA, BIOS AHWSA.1.17 12/14/2023`
`Apr 14 14:51:19 pve kernel: Call Trace:`
`Apr 14 14:51:19 pve kernel: <TASK>`
`Apr 14 14:51:19 pve kernel: dump_stack_lvl+0x48/0x70`
`Apr 14 14:51:19 pve kernel: dump_stack+0x10/0x20`
`Apr 14 14:51:19 pve kernel: print_bad_pte+0x1ca/0x2a0`
`Apr 14 14:51:19 pve kernel: ? __pte_offset_map_lock+0xa3/0x120`
`Apr 14 14:51:19 pve kernel: vm_normal_page+0xf6/0x110`
`Apr 14 14:51:19 pve kernel: copy_page_range+0x7b3/0x1540`
`Apr 14 14:51:19 pve kernel: dup_mmap+0x5c7/0x760`
`Apr 14 14:51:19 pve kernel: copy_process+0x1c7f/0x1d50`
`Apr 14 14:51:19 pve kernel: kernel_clone+0xbd/0x440`
`Apr 14 14:51:19 pve kernel: ? wp_page_reuse+0x67/0x90`
`Apr 14 14:51:19 pve kernel: __do_sys_clone+0x66/0xa0`
`Apr 14 14:51:19 pve kernel: __x64_sys_clone+0x25/0x40`
`Apr 14 14:51:19 pve kernel: do_syscall_64+0x58/0x90`
`Apr 14 14:51:19 pve kernel: ? __set_task_blocked+0x29/0x80`
`Apr 14 14:51:19 pve kernel: ? sigprocmask+0xb4/0xe0`
`Apr 14 14:51:19 pve kernel: ? exit_to_user_mode_prepare+0x39/0x190`
`Apr 14 14:51:19 pve kernel: ? syscall_exit_to_user_mode+0x37/0x60`
`Apr 14 14:51:19 pve kernel: ? do_syscall_64+0x67/0x90`
`Apr 14 14:51:19 pve kernel: ? irqentry_exit_to_user_mode+0x17/0x20`
`Apr 14 14:51:19 pve kernel: ? irqentry_exit+0x43/0x50`
`Apr 14 14:51:19 pve kernel: ? exc_page_fault+0x94/0x1b0`
`Apr 14 14:51:19 pve kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8`
`Apr 14 14:51:19 pve kernel: RIP: 0033:0x789732055293`
`Apr 14 14:51:19 pve kernel: Code: 00 00 00 00 00 66 90 64 48 8b 04 25 10 00 00 00 45 31 c0 31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 89 c2 85 c0 75 2c 64 48 8b 04 25 10 00 00`
`Apr 14 14:51:19 pve kernel: RSP: 002b:00007ffde646c018 EFLAGS: 00000246 ORIG_RAX: 0000000000000038`
`Apr 14 14:51:19 pve kernel: RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 0000789732055293`
`Apr 14 14:51:19 pve kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011`
`Apr 14 14:51:19 pve kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000`
`Apr 14 14:51:19 pve kernel: R10: 0000789731f42a10 R11: 0000000000000246 R12: 0000000000000001`
`Apr 14 14:51:19 pve kernel: R13: 00007ffde646c130 R14: 00007ffde646c1b0 R15: 000078973227c020`
`Apr 14 14:51:19 pve kernel: </TASK>`
`Apr 14 14:51:19 pve kernel: BUG: Bad rss-counter state mm:0000000074e6b477 type:MM_ANONPAGES val:-1
Code:
Apr 24 19:30:11 pve kernel: ================================================================================
Apr 24 19:30:11 pve kernel: UBSAN: invalid-load in arch/x86/kvm/x86.h:103:36
Apr 24 19:30:11 pve kernel: load of value 167 is not a valid value for type '_Bool'
Apr 24 19:30:11 pve kernel: CPU: 10 PID: 84229 Comm: CPU 1/KVM Kdump: loaded Tainted: P O 6.5.13-5-pve #1
Apr 24 19:30:11 pve kernel: Hardware name: Micro Computer (HK) Tech Limited Venus Series/AHWSA, BIOS AHWSA.1.17 12/14/2023
Apr 24 19:30:11 pve kernel: Call Trace:
Apr 24 19:30:11 pve kernel: <TASK>
Apr 24 19:30:11 pve kernel: dump_stack_lvl+0x48/0x70
Apr 24 19:30:11 pve kernel: dump_stack+0x10/0x20
Apr 24 19:30:11 pve kernel: __ubsan_handle_load_invalid_value+0xce/0x120
Apr 24 19:30:11 pve kernel: kvm_vcpu_has_events.cold+0x25/0x54 [kvm]
Apr 24 19:30:11 pve kernel: kvm_arch_vcpu_runnable+0x39/0x60 [kvm]
Apr 24 19:30:11 pve kernel: kvm_vcpu_check_block+0x2b/0xb0 [kvm]
Apr 24 19:30:11 pve kernel: kvm_vcpu_block+0x6e/0xc0 [kvm]
Apr 24 19:30:11 pve kernel: kvm_vcpu_halt+0xde/0x460 [kvm]
Apr 24 19:30:11 pve kernel: kvm_arch_vcpu_ioctl_run+0xbcf/0x17f0 [kvm]
Apr 24 19:30:11 pve kernel: ? __pfx_kvm_set_ioapic_irq+0x10/0x10 [kvm]
Apr 24 19:30:11 pve kernel: ? __pfx_kvm_set_pic_irq+0x10/0x10 [kvm]
Apr 24 19:30:11 pve kernel: kvm_vcpu_ioctl+0x297/0x800 [kvm]
Apr 24 19:30:11 pve kernel: ? kvm_vm_ioctl_irq_line+0x27/0x60 [kvm]
Apr 24 19:30:11 pve kernel: ? kvm_vm_ioctl+0x34b/0x1110 [kvm]
Apr 24 19:30:11 pve kernel: ? __fget_light+0xa5/0x120
Apr 24 19:30:11 pve kernel: __x64_sys_ioctl+0xa0/0xf0
Apr 24 19:30:11 pve kernel: do_syscall_64+0x58/0x90
Apr 24 19:30:11 pve kernel: ? __fget_light+0xa5/0x120
Apr 24 19:30:11 pve kernel: ? exit_to_user_mode_prepare+0x39/0x190
Apr 24 19:30:11 pve kernel: ? syscall_exit_to_user_mode+0x37/0x60
Apr 24 19:30:11 pve kernel: ? do_syscall_64+0x67/0x90
Apr 24 19:30:11 pve kernel: ? exit_to_user_mode_prepare+0x39/0x190
Apr 24 19:30:11 pve kernel: ? syscall_exit_to_user_mode+0x37/0x60
Apr 24 19:30:11 pve kernel: ? do_syscall_64+0x67/0x90
Apr 24 19:30:11 pve kernel: ? do_syscall_64+0x67/0x90
Apr 24 19:30:11 pve kernel: ? do_syscall_64+0x67/0x90
Apr 24 19:30:11 pve kernel: ? do_syscall_64+0x67/0x90
Apr 24 19:30:11 pve kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Apr 24 19:30:11 pve kernel: RIP: 0033:0x7ee795f79c5b
Apr 24 19:30:11 pve kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
Apr 24 19:30:11 pve kernel: RSP: 002b:00007ee791223f30 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Apr 24 19:30:11 pve kernel: RAX: ffffffffffffffda RBX: 000059567cdb9c70 RCX: 00007ee795f79c5b
Apr 24 19:30:11 pve kernel: RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000001b
Apr 24 19:30:11 pve kernel: RBP: 000000000000ae80 R08: 000059567b5e6c90 R09: 0000000000000000
Apr 24 19:30:11 pve kernel: R10: 05448eb08190d241 R11: 0000000000000246 R12: 0000000000000000
Apr 24 19:30:11 pve kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Apr 24 19:30:11 pve kernel: </TASK>
Apr 24 19:30:11 pve kernel: ================================================================================
Apr 24 19:30:33 pve pmxcfs[1962]: [status] notice: received log
Apr 24 19:30:33 pve pmxcfs[1962]: [status] notice: received log
Code:
May 13 13:28:39 pve pmxcfs[2032]: [status] notice: received log
May 13 13:29:11 pve pvedaemon[116541]: worker exit
May 13 13:29:11 pve pvedaemon[2222]: worker 116541 finished
May 13 13:29:11 pve pvedaemon[2222]: starting 1 worker(s)
May 13 13:29:11 pve pvedaemon[2222]: worker 261548 started
May 13 13:29:14 pve pmxcfs[2032]: [status] notice: received log
May 13 13:29:28 pve pmxcfs[2032]: [status] notice: received log
May 13 13:29:35 pve pmxcfs[2032]: [status] notice: received log
May 13 13:29:41 pve pmxcfs[2032]: [status] notice: received log
May 13 13:30:04 pve pmxcfs[2032]: [status] notice: received log
May 13 13:30:14 pve pmxcfs[2032]: [status] notice: received log
May 13 13:30:41 pve pmxcfs[2032]: [status] notice: received log
May 13 13:31:24 pve pmxcfs[2032]: [status] notice: received log
May 13 13:31:28 pve pmxcfs[2032]: [status] notice: received log
May 13 13:32:02 pve pvescheduler[263338]: 114-0: got unexpected replication job error - missing replicate feature on volume 'local:114/vm-114-disk-0.raw'
May 13 13:32:30 pve pmxcfs[2032]: [status] notice: received log
May 13 13:32:30 pve pmxcfs[2032]: [status] notice: received log
May 13 13:33:01 pve pmxcfs[2032]: [status] notice: received log
May 13 13:33:01 pve pmxcfs[2032]: [status] notice: received log
May 13 13:33:09 pve pmxcfs[2032]: [status] notice: received log
May 13 13:33:12 pve pmxcfs[2032]: [status] notice: received log
May 13 13:33:23 pve pmxcfs[2032]: [status] notice: received log
May 13 13:34:07 pve pmxcfs[2032]: [status] notice: received log
May 13 13:34:23 pve pmxcfs[2032]: [status] notice: received log
May 13 13:34:54 pve pmxcfs[2032]: [status] notice: received log
May 13 13:35:21 pve pmxcfs[2032]: [status] notice: received log
May 13 13:35:25 pve pmxcfs[2032]: [status] notice: received log
May 13 13:35:27 pve pmxcfs[2032]: [status] notice: received log
May 13 13:35:28 pve pmxcfs[2032]: [status] notice: received log
May 13 13:36:20 pve pmxcfs[2032]: [status] notice: received log
May 13 13:36:46 pve pvedaemon[127469]: <root@pam> update VM 106: -agent 1
May 13 13:36:55 pve pmxcfs[2032]: [status] notice: received log
May 13 13:37:03 pve pmxcfs[2032]: [status] notice: received log
May 13 13:37:44 pve pmxcfs[2032]: [status] notice: received log
May 13 13:37:50 pve pmxcfs[2032]: [status] notice: received log
May 13 13:49:32 pve pmxcfs[2032]: [dcdb] notice: data verification successful
May 13 13:57:40 pve pvedaemon[127469]: worker exit
May 13 13:57:40 pve pvedaemon[2222]: worker 127469 finished
May 13 13:57:40 pve pvedaemon[2222]: starting 1 worker(s)
May 13 13:57:40 pve pvedaemon[2222]: worker 278862 started
May 13 13:58:21 pve pmxcfs[2032]: [status] notice: received log
May 13 14:02:02 pve pvescheduler[281594]: 114-0: got unexpected replication job error - missing replicate feature on volume 'local:114/vm-114-disk-0.raw'
May 13 14:02:45 pve pmxcfs[2032]: [status] notice: received log
May 13 14:17:01 pve CRON[290653]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 13 14:17:01 pve CRON[290654]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 13 14:17:01 pve CRON[290653]: pam_unix(cron:session): session closed for user root
May 13 14:26:57 pve kernel: VERIFY3(remove_reference(hdr, hdr) > 0) failed (0 > 0)
May 13 14:26:57 pve kernel: PANIC at arc.c:6610:arc_write_done()
May 13 14:26:57 pve kernel: Showing stack for process 1321
May 13 14:26:57 pve kernel: CPU: 3 PID: 1321 Comm: z_wr_int_0 Kdump: loaded Tainted: P O 6.8.4-2-pve #1
May 13 14:26:57 pve kernel: Hardware name: Micro Computer (HK) Tech Limited Venus Series/AHWSA, BIOS AHWSA.1.22 04/01/2024
May 13 14:26:57 pve kernel: Call Trace:
May 13 14:26:57 pve kernel: <TASK>
May 13 14:26:57 pve kernel: dump_stack_lvl+0x48/0x70
May 13 14:26:57 pve kernel: dump_stack+0x10/0x20
May 13 14:26:57 pve kernel: spl_dumpstack+0x29/0x40 [spl]
May 13 14:26:57 pve kernel: spl_panic+0xfc/0x120 [spl]
May 13 14:26:57 pve kernel: arc_write_done+0x44f/0x550 [zfs]I recently updated the microcode to 0x4121 and I am now waiting for the next crash. I'll report back.
Last edited:
Oh sorry I forgot to mention, I am already running BIOS V1.23 after I got in touch with your customer support.
These error is so different from this post. Could you upload all of your logs and search it is there have any mce memory error?
MCE memory error should be fixed with reflash BIOS.
I search your error from internet. It said, may problem from PVE version 7 to 8.
Done.
It still says 1.22 version in the BIOS like before but hopefully there is something different from the 1.22 BIOS that it came with from the factory.
@JaxJiang Do you recommend any bios settings along with the reflash? I am leaving everything default for now, but should I be disabling c-states? efficiency cores? etc?