pve host restart automatic from time to time,please help me.

[skyshe]

I found that my PVE host will restart automatically, and it will restart irregularly, usually every few hours, but I can't find the problem.

I really don't know why. I uploaded the log, and the attachment was packed with rar and changed to a zip suffix

Thank you.

 

[mikeinnyc]

Feb 19 01:17:10 pve2 kernel: [ 2.385888] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042F (\GPE0) (20210730/utaddress-204)
Feb 19 01:17:10 pve2 kernel: [ 2.385899] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 01:17:10 pve2 kernel: [ 2.385903] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000052F (\_SI.SIOR) (20210730/utaddress-204)
Feb 19 01:17:10 pve2 kernel: [ 2.385908] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 01:17:10 pve2 kernel: [ 2.385940] lpc_ich: Resource conflict(s) found affecting gpio_ich



and again


Feb 19 02:03:43 pve2 kernel: [ 2.377141] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042F (\GPE0) (20210730/utaddress-204)
Feb 19 02:03:43 pve2 kernel: [ 2.377154] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 02:03:43 pve2 kernel: [ 2.377159] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000052F (\_SI.SIOR) (20210730/utaddress-204)
Feb 19 02:03:43 pve2 kernel: [ 2.377165] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 02:03:43 pve2 kernel: [ 2.377221] lpc_ich: Resource conflict(s) found affecting gpio_ich

and one more time


Feb 19 12:07:41 pve2 kernel: [ 2.356902] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042F (\GPE0) (20210730/utaddress-204)
Feb 19 12:07:41 pve2 kernel: [ 2.356914] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 12:07:41 pve2 kernel: [ 2.356919] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000052F (\_SI.SIOR) (20210730/utaddress-204)
Feb 19 12:07:41 pve2 kernel: [ 2.356925] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 12:07:41 pve2 kernel: [ 2.356989] lpc_ich: Resource conflict(s) found affecting gpio_ich

 

[mikeinnyc]

The log message provided indicates a resource conflict in the system's I/O address space. Specifically, it appears that the SystemIO range 0x0000000000000428-0x000000000000042F is conflicting with the OpRegion 0x0000000000000428-0x000000000000042F (\GPE0). This conflict is triggering an ACPI warning indicating that the driver lacks ACPI support.
Based on this error message, it is possible that there is an issue with the ACPI implementation in the system. ACPI (Advanced Configuration and Power Interface) is a standard for power management and configuration of hardware devices, and issues with ACPI can lead to various hardware-related problems.
To troubleshoot this issue, you may want to try updating your system's firmware, including the BIOS and any other relevant firmware, to ensure that they are up-to-date and support ACPI correctly. You can also try disabling ACPI in the system BIOS, but this may limit the functionality of some power management features.
If the issue persists after updating the firmware, you may want to consult the hardware maker forums for further assistance or contact the Proxmox support team for more specific troubleshooting steps.

My money is on the bios. when in doubt use the bios ACPI default settings and go from there.

 

[skyshe]

Feb 19 01:17:10 pve2 kernel: [ 2.385888] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042F (\GPE0) (20210730/utaddress-204)
Feb 19 01:17:10 pve2 kernel: [ 2.385899] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 01:17:10 pve2 kernel: [ 2.385903] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000052F (\_SI.SIOR) (20210730/utaddress-204)
Feb 19 01:17:10 pve2 kernel: [ 2.385908] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 01:17:10 pve2 kernel: [ 2.385940] lpc_ich: Resource conflict(s) found affecting gpio_ich



and again


Feb 19 02:03:43 pve2 kernel: [ 2.377141] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042F (\GPE0) (20210730/utaddress-204)
Feb 19 02:03:43 pve2 kernel: [ 2.377154] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 02:03:43 pve2 kernel: [ 2.377159] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000052F (\_SI.SIOR) (20210730/utaddress-204)
Feb 19 02:03:43 pve2 kernel: [ 2.377165] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 02:03:43 pve2 kernel: [ 2.377221] lpc_ich: Resource conflict(s) found affecting gpio_ich

and one more time


Feb 19 12:07:41 pve2 kernel: [ 2.356902] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042F (\GPE0) (20210730/utaddress-204)
Feb 19 12:07:41 pve2 kernel: [ 2.356914] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 12:07:41 pve2 kernel: [ 2.356919] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000052F (\_SI.SIOR) (20210730/utaddress-204)
Feb 19 12:07:41 pve2 kernel: [ 2.356925] ACPI: OSL: Resource conflict; ACPI support missing from driver?
Feb 19 12:07:41 pve2 kernel: [ 2.356989] lpc_ich: Resource conflict(s) found affecting gpio_ich

Sorry, I don't understand. What's the reason?

It has just restarted,

This is just the log file,and the attachment was packed with rar and changed to a zip suffix

 

[mikeinnyc]

# apt update && apt upgrade -y
then if that won't help you will have to go to your Bios and specifically go to ahci. turn it off as a last resort if #1 below won't help.

1) try updating your system's firmware, including the BIOS and any other relevant firmware, to ensure that they are up-to-date and support ACPI correctly.
2) You can also try disabling ACPI in the system BIOS

 

[skyshe]

# apt update && apt upgrade -y
then if that won't help you will have to go to your Bios and specifically go to ahci. turn it off as a last resort if #1 below won't help.

1) try updating your system's firmware, including the BIOS and any other relevant firmware, to ensure that they are up-to-date and support ACPI correctly.
2) You can also try disabling ACPI in the system BIOS

[root@pve2 ~]# dmidecode -t 0
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.5 present.

Handle 0x0005, DMI type 0, 24 bytes
BIOS Information
Vendor: Intel Corp.
Version: S5500.86B.01.00.0050.050620101605
Release Date: 05/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8 MB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.18
Firmware Revision: 0.0

[root@pve3 ~]# dmidecode -t 0
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.5 present.

Handle 0x0005, DMI type 0, 24 bytes
BIOS Information
Vendor: Intel Corp.
Version: S5500.86B.01.00.0050.050620101605
Release Date: 05/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8 MB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.18
Firmware Revision: 0.0



The bios information of the two PVE servers is consistent. Only PVE2 will crash and restart.
The memory size of the two servers is the same, the bios setting is the same, and the number of hard disks is the same. The only difference is that the server that will crash and restart is two physical CPUs, but there is a problem. If the server motherboard is a single CPU, it will not be able to power up.