My pve 8.1.3 had a reboot error

mmotk2016

New Member
Jan 12, 2024
3
0
1
Hi everybody! I need help. My system reboots after an irregular amount of time, sometimes 5 minutes, sometimes 30 minutes, and sometimes just 1 minute.

I use MSI Motar Wifi B560M motherboard with new fw bios 7D17v1C, card network BCM5720 and h310 card raid it mode

how to fix it, I read the log but don't understand, please help me, thank you!



Code:
Jan 13 05:48:46 sg kernel: ACPI: button: Sleep Button [SLPB]
Jan 13 05:48:46 sg kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
Jan 13 05:48:46 sg kernel: ACPI: button: Power Button [PWRB]
Jan 13 05:48:46 sg kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Jan 13 05:48:46 sg kernel: ACPI: button: Power Button [PWRF]
Jan 13 05:48:46 sg kernel: thermal LNXTHERM:00: registered as thermal_zone0
Jan 13 05:48:46 sg kernel: ACPI: thermal: Thermal Zone [TZ00] (28 C)
Jan 13 05:48:46 sg kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jan 13 05:48:46 sg kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jan 13 05:48:46 sg kernel: Linux agpgart interface v0.103
Jan 13 05:48:46 sg kernel: loop: module loaded
Jan 13 05:48:46 sg kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 13 05:48:46 sg kernel: PPP generic driver version 2.4.2
Jan 13 05:48:46 sg kernel: i8042: PNP: No PS/2 controller found.
Jan 13 05:48:46 sg kernel: mousedev: PS/2 mouse device common for all mice
Jan 13 05:48:46 sg kernel: rtc_cmos rtc_cmos: RTC can wake from S4
Jan 13 05:48:46 sg kernel: rtc_cmos rtc_cmos: registered as rtc0
Jan 13 05:48:46 sg kernel: rtc_cmos rtc_cmos: setting system clock to 2024-01-12T22:48:35 UTC (1705099715)
Jan 13 05:48:46 sg kernel: rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram
Jan 13 05:48:46 sg kernel: i2c_dev: i2c /dev entries driver
Jan 13 05:48:46 sg kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Jan 13 05:48:46 sg kernel: device-mapper: uevent: version 1.0.3
Jan 13 05:48:46 sg kernel: device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
Jan 13 05:48:46 sg kernel: platform eisa.0: Probing EISA bus 0
Jan 13 05:48:46 sg kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Jan 13 05:48:46 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Jan 13 05:48:46 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Jan 13 05:48:46 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Jan 13 05:48:46 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Jan 13 05:48:46 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Jan 13 05:48:46 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Jan 13 05:48:46 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Jan 13 05:48:46 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Jan 13 05:48:46 sg kernel: platform eisa.0: EISA: Detected 0 cards
Jan 13 05:48:46 sg kernel: intel_pstate: Intel P-state driver initializing
Jan 13 05:48:46 sg kernel: intel_pstate: HWP enabled
Jan 13 05:48:46 sg kernel: ledtrig-cpu: registered to indicate activity on CPUs
Jan 13 05:48:46 sg kernel: intel_pmc_core INT33A1:00:  initialized
Jan 13 05:48:46 sg kernel: drop_monitor: Initializing network drop monitor service
Jan 13 05:48:46 sg kernel: NET: Registered PF_INET6 protocol family
Jan 13 05:48:46 sg kernel: Freeing initrd memory: 59076K
Jan 13 05:48:46 sg kernel: Segment Routing with IPv6
Jan 13 05:48:46 sg kernel: In-situ OAM (IOAM) with IPv6
Jan 13 05:48:46 sg kernel: NET: Registered PF_PACKET protocol family
Jan 13 05:48:46 sg kernel: Bridge firewalling registered
Jan 13 05:48:46 sg kernel: Key type dns_resolver registered
Jan 13 05:48:46 sg kernel: mce: [Hardware Error]: Machine check events logged
Jan 13 05:48:46 sg kernel: mce: [Hardware Error]: Machine check events logged
Jan 13 05:48:46 sg kernel: microcode: Microcode Update Driver: v2.2.
Jan 13 05:48:46 sg kernel: IPI shorthand broadcast: enabled
Jan 13 05:48:46 sg kernel: sched_clock: Marking stable (940001542, 733826)->(951558968, -10823600)
Jan 13 05:48:46 sg kernel: registered taskstats version 1
Jan 13 05:48:46 sg kernel: Loading compiled-in X.509 certificates
Jan 13 05:48:46 sg kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 5f62c01e151a6e5c897562915c74e8abeac20e1f'
Jan 13 05:48:46 sg kernel: Key type .fscrypt registered
Jan 13 05:48:46 sg kernel: Key type fscrypt-provisioning registered
Jan 13 05:48:46 sg kernel: Key type trusted registered
Jan 13 05:48:46 sg kernel: Key type encrypted registered
Jan 13 05:48:46 sg kernel: AppArmor: AppArmor sha1 policy hashing enabled
Jan 13 05:48:46 sg kernel: integrity: Loading X.509 certificate: UEFI:db
Jan 13 05:48:46 sg kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
Jan 13 05:48:46 sg kernel: integrity: Loading X.509 certificate: UEFI:db
Jan 13 05:48:46 sg kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
Jan 13 05:48:46 sg kernel: integrity: Revoking X.509 certificate: UEFI:dbx
Jan 13 05:48:46 sg kernel: blacklist: Revoked X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0'
Jan 13 05:48:46 sg kernel: integrity: Revoking X.509 certificate: UEFI:dbx
Jan 13 05:48:46 sg kernel: blacklist: Revoked X.509 cert 'Debian Secure Boot Signer: 00a7468def'
Jan 13 05:48:46 sg kernel: blacklist: Duplicate blacklisted hash bin:47ff1b63b140b6fc04ed79131331e651da5b2e2f170f5daef4153dc2fbc532b1
Jan 13 05:48:46 sg kernel: blacklist: Duplicate blacklisted hash bin:5391c3a2fb112102a6aa1edc25ae77e19f5d6f09cd09eeb2509922bfcd5992ea
Jan 13 05:48:46 sg kernel: blacklist: Duplicate blacklisted hash bin:80b4d96931bf0d02fd91a61e19d14f1da452e66db2408ca8604d411f92659f0a
Jan 13 05:48:46 sg kernel: blacklist: Duplicate blacklisted hash bin:992d359aa7a5f789d268b94c11b9485a6b1ce64362b0edb4441ccc187c39647b
Jan 13 05:48:46 sg kernel: blacklist: Duplicate blacklisted hash bin:c452ab846073df5ace25cca64d6b7a09d906308a1a65eb5240e3c4ebcaa9cc0c
Jan 13 05:48:46 sg kernel: blacklist: Duplicate blacklisted hash bin:e051b788ecbaeda53046c70e6af6058f95222c046157b8c4c1b9c2cfc65f46e5
Jan 13 05:48:46 sg kernel: Loading compiled-in module X.509 certificates
Jan 13 05:48:46 sg kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 5f62c01e151a6e5c897562915c74e8abeac20e1f'
Jan 13 05:48:46 sg kernel: ima: Allocated hash algorithm: sha1
Jan 13 05:48:46 sg kernel: ima: No architecture policies found
Jan 13 05:48:46 sg kernel: evm: Initialising EVM extended attributes:
Jan 13 05:48:46 sg kernel: evm: security.selinux
Jan 13 05:48:46 sg kernel: evm: security.SMACK64
Jan 13 05:48:46 sg kernel: evm: security.SMACK64EXEC
Jan 13 05:48:46 sg kernel: evm: security.SMACK64TRANSMUTE
Jan 13 05:48:46 sg kernel: evm: security.SMACK64MMAP
Jan 13 05:48:46 sg kernel: evm: security.apparmor
 
or like this

Code:
Jan 13 05:45:48 sg kernel: mousedev: PS/2 mouse device common for all mice
Jan 13 05:45:48 sg kernel: rtc_cmos rtc_cmos: RTC can wake from S4
Jan 13 05:45:48 sg kernel: rtc_cmos rtc_cmos: registered as rtc0
Jan 13 05:45:48 sg kernel: rtc_cmos rtc_cmos: setting system clock to 2024-01-12T22:45:37 UTC (1705099537)
Jan 13 05:45:48 sg kernel: rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram
Jan 13 05:45:48 sg kernel: i2c_dev: i2c /dev entries driver
Jan 13 05:45:48 sg kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Jan 13 05:45:48 sg kernel: device-mapper: uevent: version 1.0.3
Jan 13 05:45:48 sg kernel: device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
Jan 13 05:45:48 sg kernel: platform eisa.0: Probing EISA bus 0
Jan 13 05:45:48 sg kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Jan 13 05:45:48 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Jan 13 05:45:48 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Jan 13 05:45:48 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Jan 13 05:45:48 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Jan 13 05:45:48 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Jan 13 05:45:48 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Jan 13 05:45:48 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Jan 13 05:45:48 sg kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Jan 13 05:45:48 sg kernel: platform eisa.0: EISA: Detected 0 cards
Jan 13 05:45:48 sg kernel: intel_pstate: Intel P-state driver initializing
Jan 13 05:45:48 sg kernel: intel_pstate: HWP enabled
Jan 13 05:45:48 sg kernel: ledtrig-cpu: registered to indicate activity on CPUs
Jan 13 05:45:48 sg kernel: intel_pmc_core INT33A1:00:  initialized
Jan 13 05:45:48 sg kernel: drop_monitor: Initializing network drop monitor service
Jan 13 05:45:48 sg kernel: NET: Registered PF_INET6 protocol family
Jan 13 05:45:48 sg kernel: Freeing initrd memory: 59076K
Jan 13 05:45:48 sg kernel: Segment Routing with IPv6
Jan 13 05:45:48 sg kernel: In-situ OAM (IOAM) with IPv6
Jan 13 05:45:48 sg kernel: NET: Registered PF_PACKET protocol family
Jan 13 05:45:48 sg kernel: Bridge firewalling registered
Jan 13 05:45:48 sg kernel: Key type dns_resolver registered
Jan 13 05:45:48 sg kernel: mce: [Hardware Error]: Machine check events logged
Jan 13 05:45:48 sg kernel: microcode: Microcode Update Driver: v2.2.
Jan 13 05:45:48 sg kernel: IPI shorthand broadcast: enabled
Jan 13 05:45:48 sg kernel: sched_clock: Marking stable (934383168, 738012)->(944959505, -9838325)
Jan 13 05:45:48 sg kernel: registered taskstats version 1
Jan 13 05:45:48 sg kernel: Loading compiled-in X.509 certificates
Jan 13 05:45:48 sg kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 5f62c01e151a6e5c897562915c74e8abeac20e1f'
Jan 13 05:45:48 sg kernel: Key type .fscrypt registered
Jan 13 05:45:48 sg kernel: Key type fscrypt-provisioning registered
Jan 13 05:45:48 sg kernel: Key type trusted registered
Jan 13 05:45:48 sg kernel: Key type encrypted registered
Jan 13 05:45:48 sg kernel: AppArmor: AppArmor sha1 policy hashing enabled
Jan 13 05:45:48 sg kernel: integrity: Loading X.509 certificate: UEFI:db
Jan 13 05:45:48 sg kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
Jan 13 05:45:48 sg kernel: integrity: Loading X.509 certificate: UEFI:db
Jan 13 05:45:48 sg kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
Jan 13 05:45:48 sg kernel: integrity: Revoking X.509 certificate: UEFI:dbx
Jan 13 05:45:48 sg kernel: blacklist: Revoked X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0'
Jan 13 05:45:48 sg kernel: integrity: Revoking X.509 certificate: UEFI:dbx
Jan 13 05:45:48 sg kernel: blacklist: Revoked X.509 cert 'Debian Secure Boot Signer: 00a7468def'
Jan 13 05:45:48 sg kernel: blacklist: Duplicate blacklisted hash bin:47ff1b63b140b6fc04ed79131331e651da5b2e2f170f5daef4153dc2fbc532b1
Jan 13 05:45:48 sg kernel: blacklist: Duplicate blacklisted hash bin:5391c3a2fb112102a6aa1edc25ae77e19f5d6f09cd09eeb2509922bfcd5992ea
Jan 13 05:45:48 sg kernel: blacklist: Duplicate blacklisted hash bin:80b4d96931bf0d02fd91a61e19d14f1da452e66db2408ca8604d411f92659f0a
Jan 13 05:45:48 sg kernel: blacklist: Duplicate blacklisted hash bin:992d359aa7a5f789d268b94c11b9485a6b1ce64362b0edb4441ccc187c39647b
Jan 13 05:45:48 sg kernel: blacklist: Duplicate blacklisted hash bin:c452ab846073df5ace25cca64d6b7a09d906308a1a65eb5240e3c4ebcaa9cc0c
Jan 13 05:45:48 sg kernel: blacklist: Duplicate blacklisted hash bin:e051b788ecbaeda53046c70e6af6058f95222c046157b8c4c1b9c2cfc65f46e5
Jan 13 05:45:48 sg kernel: Loading compiled-in module X.509 certificates
Jan 13 05:45:48 sg kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 5f62c01e151a6e5c897562915c74e8abeac20e1f'
Jan 13 05:45:48 sg kernel: ima: Allocated hash algorithm: sha1
Jan 13 05:45:48 sg kernel: ima: No architecture policies found
Jan 13 05:45:48 sg kernel: evm: Initialising EVM extended attributes:
Jan 13 05:45:48 sg kernel: evm: security.selinux
 
use cmd check error


Code:
root@sg:~# dmesg | grep -i mce
[    0.939757] mce: [Hardware Error]: Machine check events logged
[    0.939759] mce: [Hardware Error]: Machine check events logged
root@sg:~# dmesg | grep -i error
[    0.939757] mce: [Hardware Error]: Machine check events logged
[    0.939759] mce: [Hardware Error]: Machine check events logged
[    0.982937] RAS: Correctable Errors collector initialized.
[   12.433000] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
root@sg:~# dmesg | grep -i warning
[    0.000000] Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
root@sg:~# dmesg | grep -i fail
[   12.433000] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   12.433004] cfg80211: failed to load regulatory.db
[   12.989649] thermal thermal_zone1: failed to read out thermal zone (-61)
 

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!

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!