There are some error logs that I don't understand on a newly installed PVE7.4

G

Gridsah

Member
Mar 16, 2021
11
0
6
26
I have a Dell PowerEdge R220 (with H310 raid card in non-raid mode, BCM 5720 dual port onboard NIC). And I see some error logs in jrounalctl -b. Can someone tell me what these errors mean?

1. Is this an error? What does this mean?

Code: 
Sep 12 07:46:36 r220 kernel: Kernel command line: initrd=\EFI\proxmox\5.15.111-1-pve\initrd.img-5.15.111-1-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs
Sep 12 07:46:36 r220 kernel: Unknown kernel command line parameters "boot=zfs", will be passed to user space.

2. It seems that it is Intel's fault. I can not fix it. Right?

Code: 
Sep 12 07:46:36 r220 kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.

3. What does it mean?

Code: 
Sep 12 07:46:36 r220 kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

4. A VPD problem. Google tells me it just means VPD is disabled, I can ignore it. And I can not fix it. Right?

Code: 
Sep 12 07:46:36 r220 kernel: pci 0000:01:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format)

5. What does it mean? How can I fix it?

Code: 
Sep 12 07:46:36 r220 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorde>
Sep 12 07:46:36 r220 kernel: device-mapper: uevent: version 1.0.3
Sep 12 07:46:36 r220 kernel: device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.com
Sep 12 07:46:36 r220 kernel: platform eisa.0: Probing EISA bus 0
Sep 12 07:46:36 r220 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Sep 12 07:46:36 r220 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Sep 12 07:46:36 r220 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Sep 12 07:46:36 r220 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Sep 12 07:46:36 r220 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Sep 12 07:46:36 r220 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Sep 12 07:46:36 r220 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Sep 12 07:46:36 r220 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Sep 12 07:46:36 r220 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Sep 12 07:46:36 r220 kernel: platform eisa.0: EISA: Detected 0 cards

6. What does it mean? How can I fix it?

Code: 
Sep 12 07:46:36 r220 kernel: ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion  0x0000000000001800-0x000000000000187F (\PMIO) (20210730/utaddress-204)
Sep 12 07:46:36 r220 kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver?
Sep 12 07:46:36 r220 kernel: ACPI Warning: SystemIO range 0x00000000000008C0-0x00000000000008CF conflicts with OpRegion 0x0000000000000880-0x0000000000000C7F (\GPR) (20210730/utaddress-204)
Sep 12 07:46:36 r220 kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver?
Sep 12 07:46:36 r220 kernel: ACPI Warning: SystemIO range 0x00000000000008B0-0x00000000000008BF conflicts with OpRegion  0x0000000000000880-0x00000000000008BF (\GPRL) (20210730/utaddress-204)
Sep 12 07:46:36 r220 kernel: ACPI Warning: SystemIO range 0x00000000000008B0-0x00000000000008BF conflicts with OpRegion  0x0000000000000880-0x0000000000000C7F (\GPR) (20210730/utaddress-204)
Sep 12 07:46:36 r220 kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver?
Sep 12 07:46:36 r220 kernel: ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008AF conflicts with OpRegion  0x0000000000000880-0x00000000000008BF (\GPRL) (20210730/utaddress-204)
Sep 12 07:46:36 r220 kernel: ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008AF conflicts with OpRegion  0x0000000000000880-0x0000000000000C7F (\GPR) (20210730/utaddress-204)
Sep 12 07:46:36 r220 kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver?
Sep 12 07:46:36 r220 kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 12 07:46:36 r220 kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt

7. It seems I installed a SATA2 disk on a SATA3 port. Can I ignore it?

Code: 
Sep 12 07:46:36 r220 kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 12 07:46:36 r220 kernel: ata2: COMRESET failed (errno=-16)
Sep 12 07:46:36 r220 kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 12 07:46:36 r220 kernel: ata2: COMRESET failed (errno=-16)
Sep 12 07:46:36 r220 kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 12 07:46:36 r220 kernel: ata2: COMRESET failed (errno=-16)
Sep 12 07:46:36 r220 kernel: ata2: limiting SATA link speed to 1.5 Gbps
Sep 12 07:46:36 r220 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 12 07:46:36 r220 kernel: ata2.00: ATA-7: SSDSA2SH064G1GC INTEL, 045C8860, max UDMA/133
Sep 12 07:46:36 r220 kernel: ata2.00: 125045424 sectors, multi 1: LBA48 NCQ (depth 31)
Sep 12 07:46:36 r220 kernel: ata2.00: configured for UDMA/133
Sep 12 07:46:36 r220 kernel: scsi 2:0:0:0: Direct-Access     ATA      SSDSA2SH064G1GC  8860 PQ: 0 ANSI: 5
Sep 12 07:46:36 r220 kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Sep 12 07:46:36 r220 kernel: sd 2:0:0:0: [sdc] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
Sep 12 07:46:36 r220 kernel: sd 2:0:0:0: [sdc] Write Protect is off
Sep 12 07:46:36 r220 kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Sep 12 07:46:36 r220 kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 12 07:46:36 r220 kernel:  sdc: sdc1 sdc2 sdc3
Sep 12 07:46:36 r220 kernel: sd 2:0:0:0: [sdc] Attached SCSI disk

8. I guess it is not an error, and I can ignore it. Right?

Code: 
Sep 12 07:46:36 r220 kernel: spl: loading out-of-tree module taints kernel.
Sep 12 07:46:36 r220 kernel: znvpair: module license 'CDDL' taints kernel.
Sep 12 07:46:36 r220 kernel: Disabling lock debugging due to kernel taint
Sep 12 07:46:36 r220 kernel: ZFS: Loaded module v2.1.11-pve1, ZFS pool version 5000, ZFS filesystem version 5

9. What does this error mean? How can I fix it?

Code: 
Sep 12 07:46:36 r220 kernel: ipmi_si dmi-ipmi-si.0: Removing SMBIOS-specified kcs state machine in favor of ACPI
Sep 12 07:46:36 r220 kernel: ipmi_si: Adding ACPI-specified kcs state machine
Sep 12 07:46:36 r220 kernel: ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca8, slave address 0x20, irq 0
Sep 12 07:46:36 r220 kernel: ACPI Error: No handler for Region [ECF2] (000000008cb9ec7a) [EmbeddedControl] (20210730/evregion-130)
Sep 12 07:46:36 r220 kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210730/exfldio-261)
Sep 12 07:46:36 r220 kernel: 
Sep 12 07:46:36 r220 kernel: No Local Variables are initialized for Method [ECWT]
Sep 12 07:46:36 r220 kernel: 
Sep 12 07:46:36 r220 kernel: Initialized Arguments for Method [ECWT]:  (2 arguments defined for method invocation)
Sep 12 07:46:36 r220 kernel:   Arg0:   00000000ec4c60fe <Obj>           Integer 0000000000000000
Sep 12 07:46:36 r220 kernel:   Arg1:   0000000020d22690 [RefOf] <Node>          Name PB10 RegionField 00000000cdc47c66
Sep 12 07:46:36 r220 kernel: 
Sep 12 07:46:36 r220 kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.H_EC.ECWT due to previous error (AE_NOT_EXIST) (20210730/psparse-529)

10. It seems this error was caused by the previous one. Right?

Code: 
Sep 12 07:46:36 r220 kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.H_EC.VGBI.VBDL due to previous error (AE_NOT_EXIST) (20210730/psparse-529)
Sep 12 07:46:36 r220 kernel: cryptd: max_cpu_qlen set to 1000

11. What does this mean? How can I fix it?

Code: 
Sep 12 07:46:36 r220 kernel: intel-vbtn INT33D6:00: Error VBDL failed with ACPI status 6

12. What does this mean? It seems it is just some warnings.

Code: 
Sep 12 07:46:36 r220 kernel: pstore: ignoring unexpected backend 'efi'
Sep 12 07:46:36 r220 kernel: at24 0-0050: supply vcc not found, using dummy regulator
Sep 12 07:46:36 r220 kernel: at24 0-0050: 256 byte spd EEPROM, read-only
Sep 12 07:46:36 r220 kernel: at24 0-0051: supply vcc not found, using dummy regulator
Sep 12 07:46:36 r220 kernel: ipmi_si IPI0001:00: IPMI message handler: Found new BMC (man_id: 0x0002a2, prod_id: 0x0100, dev_id: 0x20)
Sep 12 07:46:36 r220 kernel: at24 0-0051: 256 byte spd EEPROM, read-only
Sep 12 07:46:36 r220 kernel: at24 0-0052: supply vcc not found, using dummy regulator
Sep 12 07:46:36 r220 kernel: at24 0-0052: 256 byte spd EEPROM, read-only
Sep 12 07:46:36 r220 kernel: at24 0-0053: supply vcc not found, using dummy regulator
Sep 12 07:46:36 r220 kernel: at24 0-0053: 256 byte spd EEPROM, read-only
Sep 12 07:46:36 r220 kernel: Console: switching to colour dummy device 80x25
Sep 12 07:46:36 r220 kernel: mgag200 0000:06:00.0: vgaarb: deactivate vga console
Sep 12 07:46:36 r220 kernel: [drm] Initialized mgag200 1.0.0 20110418 for 0000:06:00.0 on minor 0
Sep 12 07:46:36 r220 kernel: fbcon: mgag200drmfb (fb0) is primary device
Sep 12 07:46:36 r220 kernel: mgag200 0000:06:00.0: [drm] drm_plane_enable_fb_damage_clips() not called

Attachment has full logs.
 

Attachments

  • boot.log
    125.3 KB · Views: 0
I updated BIOS, iDRAC, and NIC driver of R220, and upgraded PVE to 8. But nothing changed.
 
Gridsah said:
3. What does it mean?

Code: 
Sep 12 07:46:36 r220 kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Click to expand...
For this question, I added acpi_osi=Linux to /etc/kernel/cmdline, and I got this now:
Code: 
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query honored via cmdline
 
Wow ... a lot of questions and you can't do anything about it. This are hardware errors built into your machine and they are normal. All of them. You can get rid of some of them by buying new hardware, yet that'll introduce new errors then or down the line when new hardware errors or strange behavior is detected and fixes were introduced in new kernel versions.

Welcome to the real world of hardware interaction that is full of errors, bugs and fixes in software. Best to NOT look at all of those errors.
 
LnxBil said:
Wow ... a lot of questions and you can't do anything about it. This are hardware errors built into your machine and they are normal. All of them. You can get rid of some of them by buying new hardware, yet that'll introduce new errors then or down the line when new hardware errors or strange behavior is detected and fixes were introduced in new kernel versions.

Welcome to the real world of hardware interaction that is full of errors, bugs and fixes in software. Best to NOT look at all of those errors.
Click to expand...
Can I pretend not to know these problems and continue using PVE?
Which problem I mentioned above can not be ignored?
:p
 
It seems I only need to care about errors:

Code: 
root@r220:~# dmesg --level=err
[   10.339032] ACPI Error: No handler for Region [ECF2] (0000000048f2285f) [EmbeddedControl] (20221020/evregion-130)
[   10.352744] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20221020/exfldio-261)
[   10.421554] ACPI Error: Aborting method \_SB.PCI0.LPCB.H_EC.ECWT due to previous error (AE_NOT_EXIST) (20221020/psparse-529)
[   10.435380] ACPI Error: Aborting method \_SB.PCI0.LPCB.H_EC.VGBI.VBDL due to previous error (AE_NOT_EXIST) (20221020/psparse-529)
[   10.449523] intel-vbtn INT33D6:00: Error VBDL failed with ACPI status 6
 
Gridsah said:
It seems I only need to care about errors:

Code: 
root@r220:~# dmesg --level=err
[   10.339032] ACPI Error: No handler for Region [ECF2] (0000000048f2285f) [EmbeddedControl] (20221020/evregion-130)
[   10.352744] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20221020/exfldio-261)
[   10.421554] ACPI Error: Aborting method \_SB.PCI0.LPCB.H_EC.ECWT due to previous error (AE_NOT_EXIST) (20221020/psparse-529)
[   10.435380] ACPI Error: Aborting method \_SB.PCI0.LPCB.H_EC.VGBI.VBDL due to previous error (AE_NOT_EXIST) (20221020/psparse-529)
[   10.449523] intel-vbtn INT33D6:00: Error VBDL failed with ACPI status 6
Click to expand...
I searched for these questions. It seems that they only affect power management and do not affect normal system operation?
 
Gridsah said:
It seems I only need to care about errors:

Code: 
root@r220:~# dmesg --level=err
[   10.339032] ACPI Error: No handler for Region [ECF2] (0000000048f2285f) [EmbeddedControl] (20221020/evregion-130)
[   10.352744] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20221020/exfldio-261)
[   10.421554] ACPI Error: Aborting method \_SB.PCI0.LPCB.H_EC.ECWT due to previous error (AE_NOT_EXIST) (20221020/psparse-529)
[   10.435380] ACPI Error: Aborting method \_SB.PCI0.LPCB.H_EC.VGBI.VBDL due to previous error (AE_NOT_EXIST) (20221020/psparse-529)
[   10.449523] intel-vbtn INT33D6:00: Error VBDL failed with ACPI status 6
Click to expand...
Today, I installed RHEL7 which is in the support list of the DELL R220 server. But this problem still exists in journalctl -b of RHEL7.:confused:
 
After days of research, I can answer my question:

1. It is info, not error. I can ignore it.
2. It is Intel's fault. their CPU has some hardware bugs. I can not solve it.
3. It is a historical legacy issue related to BIOS and does not require attention.
4. Broadcom's fault, and It is been there for a long time. I have nothing to do.
5. It is warning. No EISA is connected to the system so nothing can be done.
6. This message is about some drivers being denied access to devices controlled by the ACPI. Someone tells me I can ignore it.
7. I installed a SATA2 disk to a SATA3 port. And I can ignore it.
8. It is info, not error. I can ignore it.
9-11. R220 has no Intel Virtual Button in BIOS, so this error just should be there. I have nothing to do.
12. It is warning and nothing can be done.
 
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
Back