[SOLVED] Kernel crash (5.13.19-2-pve) a few hours after update

M

MalteP

Member
Dec 11, 2021
4
1
8
Germany
Hi,

my homelab Proxmox server crashed a few hours after updating to 5.13.19-2-pve kernel, i am unsure if 5.11 was running before but there weren't any stability issues with this system until now. Any help appreciated.

Best regards,
Malte

proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-8 (running version: 7.1-8/5b267f33)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
Click to expand...

Dec 10 20:07:22 proxmox kernel: ------------[ cut here ]------------
Dec 10 20:07:22 proxmox kernel: WARNING: CPU: 1 PID: 44 at arch/x86/kvm/mmu/mmu.c:550 mmu_spte_clear_track_bits+0x10e/0x120 [kvm]
Dec 10 20:07:22 proxmox kernel: Modules linked in: vfio_pci vfio_virqfd vfio_iommu_type1 vfio veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter nf_tables 8021q garp mrp bonding tls softdog nfnetlink_log nfnetlink snd_sof_pci_intel_apl snd_sof_intel_hda_common snd_hda_codec_hdmi soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci intel_rapl_msr intel_rapl_common snd_sof_xtensa_dsp snd_sof snd_hda_codec_realtek soundwire_bus snd_hda_codec_generic ledtrig_audio snd_soc_skl snd_soc_hdac_hda intel_pmc_bxt intel_telemetry_pltdrv snd_hda_ext_core intel_punit_ipc snd_soc_sst_ipc intel_telemetry_core x86_pkg_temp_thermal snd_soc_sst_dsp intel_powerclamp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core coretemp mei_hdcp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm snd_hda_intel mac80211 kvm_intel i915 libarc4 snd_intel_dspcfg snd_intel_sdw_acpi iwlwifi drm_kms_helper snd_hda_codec kvm snd_hda_core cec snd_hwdep
Dec 10 20:07:22 proxmox kernel: irqbypass rc_core ftdi_sio i2c_algo_bit snd_pcm fb_sys_fops crct10dif_pclmul syscopyarea snd_timer ghash_clmulni_intel sysfillrect usbserial btusb btrtl aesni_intel btbcm snd btintel crypto_simd bluetooth mei_me cryptd rapl sysimgblt soundcore intel_cstate mei ee1004 mac_hid cfg80211 ecdh_generic ecc efi_pstore pcspkr zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_net vhost vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi drm sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq hid_generic usbhid hid dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c crc32_pclmul i2c_i801 i2c_smbus xhci_pci xhci_pci_renesas sdhci_pci cqhci r8169 xhci_hcd sdhci realtek ahci libahci video
Dec 10 20:07:22 proxmox kernel: CPU: 1 PID: 44 Comm: khugepaged Tainted: P O 5.13.19-2-pve #1
Dec 10 20:07:22 proxmox kernel: Hardware name: GIGABYTE MZGLKAP-00/MZGLKAP-00, BIOS F6 03/19/2019
Dec 10 20:07:22 proxmox kernel: RIP: 0010:mmu_spte_clear_track_bits+0x10e/0x120 [kvm]
Dec 10 20:07:22 proxmox kernel: Code: d8 48 23 05 c4 0a 04 00 74 08 4c 89 e7 e8 2a 97 fb ff 83 e3 02 75 dd 5b b8 01 00 00 00 41 5c 41 5d 5d c3 48 85 c3 74 bb eb b1 <0f> 0b eb 85 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f 44 00
Dec 10 20:07:22 proxmox kernel: RSP: 0018:ffffb65ec01bbc28 EFLAGS: 00010246
Dec 10 20:07:22 proxmox kernel: RAX: 0000000000000000 RBX: 00000002d1a2a975 RCX: dead0000000000ff
Dec 10 20:07:22 proxmox kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00000000002d1a2a
Dec 10 20:07:22 proxmox kernel: RBP: ffffb65ec01bbc40 R08: 0000000000000001 R09: ffff8df644c57f50
Dec 10 20:07:22 proxmox kernel: R10: 000000000000000b R11: fffffa69d20f0000 R12: 00000000002d1a2a
Dec 10 20:07:22 proxmox kernel: R13: 0000000000000800 R14: ffffb65ec3c65000 R15: 0000000000000001
Dec 10 20:07:22 proxmox kernel: FS: 0000000000000000(0000) GS:ffff8dfbdfc80000(0000) knlGS:0000000000000000
Dec 10 20:07:22 proxmox kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 10 20:07:22 proxmox kernel: CR2: 00007ff6338bb000 CR3: 000000069d010000 CR4: 0000000000352ee0
Dec 10 20:07:22 proxmox kernel: Call Trace:
Dec 10 20:07:22 proxmox kernel: kvm_unmap_gfn_range+0x97/0x130 [kvm]
Dec 10 20:07:22 proxmox kernel: kvm_mmu_notifier_invalidate_range_start+0x17e/0x2b0 [kvm]
Dec 10 20:07:22 proxmox kernel: __mmu_notifier_invalidate_range_start+0x81/0x1a0
Dec 10 20:07:22 proxmox kernel: khugepaged+0x1f97/0x20b0
Dec 10 20:07:22 proxmox kernel: ? collapse_pte_mapped_thp+0x440/0x440
Dec 10 20:07:22 proxmox kernel: kthread+0x128/0x150
Dec 10 20:07:22 proxmox kernel: ? set_kthread_struct+0x50/0x50
Dec 10 20:07:22 proxmox kernel: ret_from_fork+0x1f/0x30
Dec 10 20:07:22 proxmox kernel: ---[ end trace c3bf75b3394f822a ]---
Click to expand...
1/2
 
Dec 10 20:07:22 proxmox kernel: ------------[ cut here ]------------
Dec 10 20:07:22 proxmox kernel: WARNING: CPU: 1 PID: 44 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:171 kvm_is_zone_device_pfn+0x54/0x60 [kvm]
Dec 10 20:07:22 proxmox kernel: Modules linked in: vfio_pci vfio_virqfd vfio_iommu_type1 vfio veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter nf_tables 8021q garp mrp bonding tls softdog nfnetlink_log nfnetlink snd_sof_pci_intel_apl snd_sof_intel_hda_common snd_hda_codec_hdmi soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci intel_rapl_msr intel_rapl_common snd_sof_xtensa_dsp snd_sof snd_hda_codec_realtek soundwire_bus snd_hda_codec_generic ledtrig_audio snd_soc_skl snd_soc_hdac_hda intel_pmc_bxt intel_telemetry_pltdrv snd_hda_ext_core intel_punit_ipc snd_soc_sst_ipc intel_telemetry_core x86_pkg_temp_thermal snd_soc_sst_dsp intel_powerclamp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core coretemp mei_hdcp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm snd_hda_intel mac80211 kvm_intel i915 libarc4 snd_intel_dspcfg snd_intel_sdw_acpi iwlwifi drm_kms_helper snd_hda_codec kvm snd_hda_core cec snd_hwdep
Dec 10 20:07:22 proxmox kernel: irqbypass rc_core ftdi_sio i2c_algo_bit snd_pcm fb_sys_fops crct10dif_pclmul syscopyarea snd_timer ghash_clmulni_intel sysfillrect usbserial btusb btrtl aesni_intel btbcm snd btintel crypto_simd bluetooth mei_me cryptd rapl sysimgblt soundcore intel_cstate mei ee1004 mac_hid cfg80211 ecdh_generic ecc efi_pstore pcspkr zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_net vhost vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi drm sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq hid_generic usbhid hid dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c crc32_pclmul i2c_i801 i2c_smbus xhci_pci xhci_pci_renesas sdhci_pci cqhci r8169 xhci_hcd sdhci realtek ahci libahci video
Dec 10 20:07:22 proxmox kernel: CPU: 1 PID: 44 Comm: khugepaged Tainted: P W O 5.13.19-2-pve #1
Dec 10 20:07:22 proxmox kernel: Hardware name: GIGABYTE MZGLKAP-00/MZGLKAP-00, BIOS F6 03/19/2019
Dec 10 20:07:22 proxmox kernel: RIP: 0010:kvm_is_zone_device_pfn+0x54/0x60 [kvm]
Dec 10 20:07:22 proxmox kernel: Code: 42 ff 83 e2 01 48 0f 44 c3 8b 40 34 85 c0 74 1a 48 8b 03 48 c1 e8 33 83 e0 07 83 f8 04 41 0f 94 c0 48 8b 5d f8 44 89 c0 c9 c3 <0f> 0b eb f3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41
Dec 10 20:07:22 proxmox kernel: RSP: 0018:ffffb65ec01bbbf0 EFLAGS: 00010246
Dec 10 20:07:22 proxmox kernel: RAX: 0000000000000000 RBX: fffffa69cb468a80 RCX: 0000000000000000
Dec 10 20:07:22 proxmox kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00000000002d1a2a
Dec 10 20:07:22 proxmox kernel: RBP: ffffb65ec01bbbf8 R08: 0000000000000000 R09: ffff8df644c57f50
Dec 10 20:07:22 proxmox kernel: R10: 000000000000000b R11: fffffa69d20f0000 R12: 00000000002d1a2a
Dec 10 20:07:22 proxmox kernel: R13: 0000000000000800 R14: ffffb65ec3c65000 R15: 0000000000000001
Dec 10 20:07:22 proxmox kernel: FS: 0000000000000000(0000) GS:ffff8dfbdfc80000(0000) knlGS:0000000000000000
Dec 10 20:07:22 proxmox kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 10 20:07:22 proxmox kernel: CR2: 00007ff6338bb000 CR3: 000000069d010000 CR4: 0000000000352ee0
Dec 10 20:07:22 proxmox kernel: Call Trace:
Dec 10 20:07:22 proxmox kernel: kvm_set_pfn_accessed+0x53/0x70 [kvm]
Dec 10 20:07:22 proxmox kernel: mmu_spte_clear_track_bits+0xc7/0x120 [kvm]
Dec 10 20:07:22 proxmox kernel: kvm_unmap_gfn_range+0x97/0x130 [kvm]
Dec 10 20:07:22 proxmox kernel: kvm_mmu_notifier_invalidate_range_start+0x17e/0x2b0 [kvm]
Dec 10 20:07:22 proxmox kernel: __mmu_notifier_invalidate_range_start+0x81/0x1a0
Dec 10 20:07:22 proxmox kernel: khugepaged+0x1f97/0x20b0
Dec 10 20:07:22 proxmox kernel: ? collapse_pte_mapped_thp+0x440/0x440
Dec 10 20:07:22 proxmox kernel: kthread+0x128/0x150
Dec 10 20:07:22 proxmox kernel: ? set_kthread_struct+0x50/0x50
Dec 10 20:07:22 proxmox kernel: ret_from_fork+0x1f/0x30
Dec 10 20:07:22 proxmox kernel: ---[ end trace c3bf75b3394f822b ]---
Dec 10 20:10:54 proxmox kernel: perf: interrupt took too long (4967 > 4966), lowering kernel.perf_event_max_sample_rate to 40250
Dec 10 20:17:01 proxmox CRON[52124]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 10 20:17:01 proxmox CRON[52125]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 10 20:17:01 proxmox CRON[52124]: pam_unix(cron:session): session closed for user root
Dec 10 20:33:04 proxmox kernel: BUG: Bad page map in process pve-firewall pte:8000000124abf867 pmd:476277067
Dec 10 20:33:04 proxmox kernel: page:0000000032cb12ca refcount:0 mapcount:-1 mapping:0000000000000000 index:0x1 pfn:0x124abf
Dec 10 20:33:04 proxmox kernel: flags: 0x17ffffc000000a(referenced|dirty|node=0|zone=2|lastcpupid=0x1fffff)
Dec 10 20:33:04 proxmox kernel: raw: 0017ffffc000000a fffffa69c535e108 fffffa69ca9d1948 0000000000000000
Dec 10 20:33:04 proxmox kernel: raw: 0000000000000001 0000000000000000 00000000fffffffe 0000000000000000
Dec 10 20:33:04 proxmox kernel: page dumped because: bad pte
Dec 10 20:33:04 proxmox kernel: addr:0000555e36a5b000 vm_flags:08100073 anon_vma:ffff8df6808e21b8 mapping:0000000000000000 index:555e36a5b
Dec 10 20:33:04 proxmox kernel: file:(null) fault:0x0 mmap:0x0 readpage:0x0
Dec 10 20:33:04 proxmox kernel: CPU: 3 PID: 55225 Comm: pve-firewall Tainted: P W O 5.13.19-2-pve #1
Dec 10 20:33:04 proxmox kernel: Hardware name: GIGABYTE MZGLKAP-00/MZGLKAP-00, BIOS F6 03/19/2019
Dec 10 20:33:04 proxmox kernel: Call Trace:
Dec 10 20:33:04 proxmox kernel: dump_stack+0x7d/0x9c
Dec 10 20:33:04 proxmox kernel: print_bad_pte.cold+0x6b/0xc3
Dec 10 20:33:04 proxmox kernel: ? __mod_lruvec_page_state+0x98/0xb0
Dec 10 20:33:04 proxmox kernel: unmap_page_range+0x922/0xe80
Dec 10 20:33:04 proxmox kernel: unmap_single_vma+0x7f/0xf0
Dec 10 20:33:04 proxmox kernel: unmap_vmas+0x77/0xf0
Dec 10 20:33:04 proxmox kernel: exit_mmap+0xab/0x1f0
Dec 10 20:33:04 proxmox kernel: mmput+0x5f/0x140
Dec 10 20:33:04 proxmox kernel: begin_new_exec+0x4d7/0xa50
Dec 10 20:33:04 proxmox kernel: load_elf_binary+0x730/0x16f0
Dec 10 20:33:04 proxmox kernel: ? __kernel_read+0x19d/0x2c0
Dec 10 20:33:04 proxmox kernel: ? aa_get_task_label+0x49/0xd0
Dec 10 20:33:04 proxmox kernel: ? ima_bprm_check+0x89/0xb0
Dec 10 20:33:04 proxmox kernel: bprm_execve+0x27c/0x660
Dec 10 20:33:04 proxmox kernel: do_execveat_common+0x192/0x1c0
Dec 10 20:33:04 proxmox kernel: __x64_sys_execve+0x39/0x50
Dec 10 20:33:04 proxmox kernel: do_syscall_64+0x61/0xb0
Dec 10 20:33:04 proxmox kernel: ? handle_mm_fault+0xda/0x2c0
Dec 10 20:33:04 proxmox kernel: ? exit_to_user_mode_prepare+0x37/0x1b0
Dec 10 20:33:04 proxmox kernel: ? irqentry_exit_to_user_mode+0x9/0x20
Dec 10 20:33:04 proxmox kernel: ? irqentry_exit+0x19/0x30
Dec 10 20:33:04 proxmox kernel: ? exc_page_fault+0x8f/0x170
Dec 10 20:33:04 proxmox kernel: ? asm_exc_page_fault+0x8/0x30
Dec 10 20:33:04 proxmox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
Dec 10 20:33:04 proxmox kernel: RIP: 0033:0x7f47ed8126c7
Dec 10 20:33:04 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x7f47ed81269d.
Dec 10 20:33:04 proxmox kernel: RSP: 002b:00007ffde9fda008 EFLAGS: 00000202 ORIG_RAX: 000000000000003b
Dec 10 20:33:04 proxmox kernel: RAX: ffffffffffffffda RBX: 0000555e342d82c0 RCX: 00007f47ed8126c7
Dec 10 20:33:04 proxmox kernel: RDX: 0000555e32374a00 RSI: 0000555e3432bee0 RDI: 00007ffde9fda010
Dec 10 20:33:04 proxmox kernel: RBP: 00007ffde9fda0a0 R08: 000000000000fefc R09: 0000555e31e3bd2a
Dec 10 20:33:04 proxmox kernel: R10: 0000555e31e3cd00 R11: 0000000000000202 R12: 0000555e3432bee0
Dec 10 20:33:04 proxmox kernel: R13: 0000555e32374a00 R14: 00007ffde9fda010 R15: 0000555e31e3bd25
Dec 10 20:33:04 proxmox kernel: BUG: Bad page map in process pve-firewall pte:8000000124abf867 pmd:472b19067
Dec 10 20:33:04 proxmox kernel: page:0000000032cb12ca refcount:0 mapcount:-1 mapping:0000000000000000 index:0x1 pfn:0x124abf
Dec 10 20:33:04 proxmox kernel: flags: 0x17ffffc000000a(referenced|dirty|node=0|zone=2|lastcpupid=0x1fffff)
Dec 10 20:33:04 proxmox kernel: raw: 0017ffffc000000a fffffa69c53cc0c8 fffffa69c6d1b4c8 0000000000000000
Dec 10 20:33:04 proxmox kernel: raw: 0000000000000001 0000000000000000 00000000fffffffe 0000000000000000
Dec 10 20:33:04 proxmox kernel: page dumped because: bad pte
Dec 10 20:33:04 proxmox kernel: addr:0000555e36500000 vm_flags:08100073 anon_vma:ffff8df61399fe70 mapping:0000000000000000 index:555e36500
Dec 10 20:33:04 proxmox kernel: file:(null) fault:0x0 mmap:0x0 readpage:0x0
Dec 10 20:33:04 proxmox kernel: CPU: 3 PID: 55226 Comm: pve-firewall Tainted: P B W O 5.13.19-2-pve #1
Dec 10 20:33:04 proxmox kernel: Hardware name: GIGABYTE MZGLKAP-00/MZGLKAP-00, BIOS F6 03/19/2019
Dec 10 20:33:04 proxmox kernel: Call Trace:
Dec 10 20:33:04 proxmox kernel: dump_stack+0x7d/0x9c
Dec 10 20:33:04 proxmox kernel: print_bad_pte.cold+0x6b/0xc3
Dec 10 20:33:04 proxmox kernel: ? __mod_lruvec_page_state+0x98/0xb0
Dec 10 20:33:04 proxmox kernel: unmap_page_range+0x922/0xe80
Dec 10 20:33:04 proxmox kernel: unmap_single_vma+0x7f/0xf0
Dec 10 20:33:04 proxmox kernel: unmap_vmas+0x77/0xf0
Dec 10 20:33:04 proxmox kernel: exit_mmap+0xab/0x1f0
Dec 10 20:33:04 proxmox kernel: mmput+0x5f/0x140
Dec 10 20:33:04 proxmox kernel: begin_new_exec+0x4d7/0xa50
Dec 10 20:33:04 proxmox kernel: load_elf_binary+0x730/0x16f0
Dec 10 20:33:04 proxmox kernel: ? __kernel_read+0x19d/0x2c0
Dec 10 20:33:04 proxmox kernel: ? aa_get_task_label+0x49/0xd0
Dec 10 20:33:04 proxmox kernel: ? ima_bprm_check+0x89/0xb0
Dec 10 20:33:04 proxmox kernel: bprm_execve+0x27c/0x660
Dec 10 20:33:04 proxmox kernel: do_execveat_common+0x192/0x1c0
Dec 10 20:33:04 proxmox kernel: __x64_sys_execve+0x39/0x50
Dec 10 20:33:04 proxmox kernel: do_syscall_64+0x61/0xb0
Dec 10 20:33:04 proxmox kernel: ? handle_mm_fault+0xda/0x2c0
Dec 10 20:33:04 proxmox kernel: ? exit_to_user_mode_prepare+0x37/0x1b0
Dec 10 20:33:04 proxmox kernel: ? irqentry_exit_to_user_mode+0x9/0x20
Dec 10 20:33:04 proxmox kernel: ? irqentry_exit+0x19/0x30
Dec 10 20:33:04 proxmox kernel: ? exc_page_fault+0x8f/0x170
Dec 10 20:33:04 proxmox kernel: ? asm_exc_page_fault+0x8/0x30
Dec 10 20:33:04 proxmox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
Dec 10 20:33:04 proxmox kernel: RIP: 0033:0x7f47ed8126c7
Dec 10 20:33:04 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x7f47ed81269d.
Dec 10 20:33:04 proxmox kernel: RSP: 002b:00007ffde9fda018 EFLAGS: 00000203 ORIG_RAX: 000000000000003b
Dec 10 20:33:04 proxmox kernel: RAX: ffffffffffffffda RBX: 0000555e342d82c0 RCX: 00007f47ed8126c7
Dec 10 20:33:04 proxmox kernel: RDX: 0000555e32374a00 RSI: 0000555e36a5e110 RDI: 00007ffde9fda020
Dec 10 20:33:04 proxmox kernel: RBP: 00007ffde9fda0b0 R08: 000000000000000e R09: 0000555e31e3bd2a
Dec 10 20:33:04 proxmox kernel: R10: 0000555e31e3cd00 R11: 0000000000000203 R12: 0000555e36a5e110
Dec 10 20:33:04 proxmox kernel: R13: 0000555e32374a00 R14: 00007ffde9fda020 R15: 0000555e31e3bd25
Dec 10 20:33:14 proxmox kernel: BUG: Bad page map in process pve-firewall pte:8000000124abf845 pmd:4763d6067
Dec 10 20:33:14 proxmox kernel: page:0000000032cb12ca refcount:1 mapcount:-1 mapping:0000000000000000 index:0x382 pfn:0x124abf
Dec 10 20:33:14 proxmox kernel: memcg:ffff8df48a027000
Dec 10 20:33:14 proxmox kernel: anon flags: 0x17ffffc0080014(uptodate|lru|swapbacked|node=0|zone=2|lastcpupid=0x1fffff)
Dec 10 20:33:14 proxmox kernel: raw: 0017ffffc0080014 fffffa69c5aa1288 fffffa69c656e648 ffff8df6a6409899
Dec 10 20:33:14 proxmox kernel: raw: 0000000000000382 0000000000000000 00000001fffffffe ffff8df48a027000
Dec 10 20:33:14 proxmox kernel: page dumped because: bad pte
Dec 10 20:33:14 proxmox kernel: addr:0000555e33fa7000 vm_flags:08100073 anon_vma:ffff8df6a6409bb0 mapping:0000000000000000 index:555e33fa7
Dec 10 20:33:14 proxmox kernel: file:(null) fault:0x0 mmap:0x0 readpage:0x0
Click to expand...
2/2
 
I have a similar issue - once I perform a proxmox backup, I get a similar kernel crash. After this update too..
 
That's interesting because i have two similar Gigabyte BLCE-4105 barebones and i was moving everything to the second system (to do some hardware checks on the first) after the crash on friday. While doing that some of my backups seemed to be corrupted:

progress 95% (read 142807662592 bytes, duration 678 sec)
progress 96% (read 144310927360 bytes, duration 679 sec)
progress 97% (read 145814192128 bytes, duration 680 sec)
_11-01_18_31.vma.zst : Decoding error (36) : Restored data doesn't match checksum
progress 98% (read 147317391360 bytes, duration 690 sec)
progress 99% (read 148820656128 bytes, duration 690 sec)
progress 100% (read 150323855360 bytes, duration 690 sec)
total bytes read 150323855360, sparse bytes 76087300096 (50.6%)
space reduction due to 4K zero blocks 0.379%
Logical volume "vm-403-disk-0" successfully removed
temporary volume 'local-lvm:vm-403-disk-0' sucessfuly removed
Logical volume "vm-403-disk-1" successfully removed
temporary volume 'local-lvm:vm-403-disk-1' sucessfuly removed
no lock found trying to remove 'create' lock
error before or during data restore, some or all disks were not completely restored. VM 403 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zstd -q -d -c /mnt/pve/backup-nas/dump/vzdump-qemu-403-2021_12_11-01_18_31.vma.zst | vma extract -v -r /var/tmp/vzdumptmp106823.fifo - /var/tmp/vzdumptmp106823' failed: exit code 1
Click to expand...

So i ran fsck inside the VMs but the filesystem had no issues. Did another backup and i was finally able to import them. Currently running Kernel 5.11.22-7-pve, no problems so far.

What's your hardware configuration?
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom