- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: i have similar error Proliant DL20 Gen10, plea...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2021 08:55 PM - last edited on 08-19-2021 12:59 AM by support_s
08-11-2021 08:55 PM - last edited on 08-19-2021 12:59 AM by support_s
i have similar error Proliant DL20 Gen10, please help
ACPI Error: No Handler for Region [POWR] (000000007d0f211e) [IPMI] (20200110/evregion-132)
Region IPMI (ID=7) has no handler (20200110/exfldio-265)
Aborting method \_sB.PMI0._PMM (due to previous error (AE_NOT_EXIST) (20200110/psparse-531)
AE_NOT_EXIST, Evaluating _PMM (20200110/power_meter-338)
dmidecode | grep -i product
Product Name: ProLiant DL20 Gen10
Module Product ID: Unknown
Memory Subsystem Controller Product ID: Unknown
Module Product ID: Unknown
Memory Subsystem Controller Product ID: Unknown
Module Product ID: Unknown
Memory Subsystem Controller Product ID: Unknown
Module Product ID: Unknown
Memory Subsystem Controller Product ID: Unknown
String 2: Product ID: P17079-B21
Product Name: ProLiant DL20 Gen10
[root@factra ~]# uname -a
Linux factra 4.18.0-240.22.1.el8_3.x86_64 #1 SMP Fri Apr 9 10:23:57 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
[root@factra ~]# lsmod | grep ipmi
ipmi_ssif 36864 0
ipmi_si 65536 0
ipmi_devintf 20480 0
ipmi_msghandler 110592 3 ipmi_devintf,ipmi_si,ipmi_ssif
[root@factra ~]# modinfo ipmi_si
filename: /lib/modules/4.18.0-240.22.1.el8_3.x86_64/kernel/drivers/char/ipmi/ipmi_si.ko.xz
description: Interface to the IPMI driver for the KCS, SMIC, and BT system interfaces.
author: Corey Minyard <minyard@mvista.com>
license: GPL
alias: platform:dmi-ipmi-si
rhelversion: 8.3
srcversion: AED09729E71836B61BE58ED
alias: pci:v*d*sv*sd*bc0Csc07i02*
alias: pci:v*d*sv*sd*bc0Csc07i01*
alias: pci:v*d*sv*sd*bc0Csc07i00*
alias: pci:v0000103Cd0000121Asv*sd*bc*sc*i*
alias: acpi*:IPI0001:*
depends: ipmi_msghandler
intree: Y
name: ipmi_si
vermagic: 4.18.0-240.22.1.el8_3.x86_64 SMP mod_unload modversions
sig_id: PKCS#7
signer: AlmaLinux kernel signing key
sig_key: 1C:E2:E0:C1:77:55:39:A9:57:D0:1F:F5:18:6F:D4:45:82:E8:34:F6
sig_hashalgo: sha256
signature: 0D:18:CB:4F:05:84:6E:68:8E:50:81:F1:CC:5B:A9:FB:71:E0:C5:61:
78:03:7E:D1:AF:BF:C3:43:D6:9E:FE:BC:9E:68:D1:03:E1:91:5F:38:
0A:D0:AF:D5:A7:41:42:FD:D7:A4:EC:5D:C9:9E:48:4E:5A:E5:38:CE:
B5:29:9C:E0:3F:DE:4D:C6:92:65:F8:C0:E1:76:90:98:43:E8:AA:3D:
50:17:B5:AF:6D:67:BE:20:50:41:C7:38:B1:FB:BA:4A:51:5B:C6:18:
9F:13:2B:0C:9A:B0:72:53:D7:AE:05:81:F2:A3:FA:95:EB:15:A6:E5:
C5:5E:F1:E5:9B:9B:8B:89:DC:21:C5:9A:FE:3F:A4:26:0A:32:89:9F:
1C:F0:2B:89:1B:8D:6E:5D:34:2F:98:1F:9F:DA:D0:F1:23:0E:F4:B3:
E1:D6:CA:07:AC:13:E8:59:02:CA:AD:4B:AD:E9:0C:15:94:42:A7:EE:
74:73:43:55:01:DD:AF:D7:74:FF:F8:9C:F8:1B:14:2E:B0:52:D9:AA:
9B:CE:6B:79:E5:D8:2B:0D:7F:86:59:53:97:33:7F:13:9B:12:1E:C5:
BE:5F:B6:93:F0:EF:0B:CC:87:EA:0D:70:E0:44:DA:0B:DF:53:4F:ED:
B1:2F:5F:32:2E:93:44:75:FC:F5:A5:A3:55:9C:79:98:C2:C2:79:37:
81:09:FE:37:F7:26:B4:C5:9D:50:AF:DE:EE:62:59:45:65:9D:84:84:
E5:3D:5F:02:B0:D5:9F:97:C0:9E:43:F8:EE:0D:B7:1A:A7:53:66:AE:
97:9D:D8:3B:97:F3:64:1E:74:1B:51:8E:88:0A:82:FB:A4:43:A9:D6:
17:36:0C:93:BE:BE:B0:8C:BD:9D:42:55:9A:2B:A2:93:34:A5:29:AC:
86:CD:51:12:0A:87:14:38:11:0E:93:9F:A2:B5:C4:FA:A6:83:21:06:
90:86:4B:A1:CA:71:F1:88:96:79:06:A8:90:89:1F:71:5B:88:49:35:
7F:11:07:DB
parm: trypci:Setting this to zero will disable the default scan of the interfaces identified via pci (bool)
parm: tryplatform:Setting this to zero will disable the default scan of the interfaces identified via platform interfaces besides ACPI, OpenFirmware, and DMI (bool)
parm: tryacpi:Setting this to zero will disable the default scan of the interfaces identified via ACPI (bool)
parm: trydmi:Setting this to zero will disable the default scan of the interfaces identified via DMI (bool)
parm: type:Defines the type of each interface, each interface separated by commas. The types are 'kcs', 'smic', and 'bt'. For example si_type=kcs,bt will set the first interface to kcs and the second to bt (string)
parm: addrs:Sets the memory address of each interface, the addresses separated by commas. Only use if an interface is in memory. Otherwise, set it to zero or leave it blank. (array of ulong)
parm: ports:Sets the port address of each interface, the addresses separated by commas. Only use if an interface is a port. Otherwise, set it to zero or leave it blank. (array of uint)
parm: irqs:Sets the interrupt of each interface, the addresses separated by commas. Only use if an interface has an interrupt. Otherwise, set it to zero or leave it blank. (array of int)
parm: regspacings:The number of bytes between the start address and each successive register used by the interface. For instance, if the start address is 0xca2 and the spacing is 2, then the second address is at 0xca4. Defaults to 1. (array of int)
parm: regsizes:The size of the specific IPMI register in bytes. This should generally be 1, 2, 4, or 8 for an 8-bit, 16-bit, 32-bit, or 64-bit register. Use this if you the 8-bit IPMI register has to be read from a larger register. (array of int)
parm: regshifts:The amount to shift the data read from the. IPMI register, in bits. For instance, if the data is read from a 32-bit word and the IPMI data is in bit 8-15, then the shift would be 8 (array of int)
parm: slave_addrs:Set the default IPMB slave address for the controller. Normally this is 0x20, but can be overridden by this parm. This is an array indexed by interface number. (array of int)
parm: hotmod:Add and remove interfaces. See Documentation/IPMI.txt in the kernel sources for the gory details.
parm: bt_debug:debug bitmask, 1=enable, 2=messages, 4=states (int)
parm: smic_debug:debug bitmask, 1=enable, 2=messages, 4=states (int)
parm: kcs_debug:debug bitmask, 1=enable, 2=messages, 4=states (int)
parm: force_kipmid:Force the kipmi daemon to be enabled (1) or disabled(0). Normally the IPMI driver auto-detects this, but the value may be overridden by this parm. (array of int)
parm: unload_when_empty:Unload the module if no interfaces are specified or found, default is 1. Setting to 0 is useful for hot add of devices using hotmod. (bool)
parm: kipmid_max_busy_us:Max time (in microseconds) to busy-wait for IPMI data before sleeping. 0 (default) means to wait forever. Set to 100-500 if kipmid is using up a lot of CPU time. (array of uint)
[root@factra ~]# dmidecode -t bios
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.1.1 present.
Handle 0x0002, DMI type 0, 26 bytes
BIOS Information
Vendor: HPE
Version: U43
Release Date: 03/09/2020
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 32 MB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/360 kB floppy services are supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB 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)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 2.14
Firmware Revision: 2.12
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2021 08:01 AM
08-12-2021 08:01 AM
Re: i have similar error Proliant DL20 Gen10, please help
needs to be replace for fix this issue.
How old is that server ?
Sometimes PSU have voltage issues when they get cold or warm as they are worn out. Re-seating may help or reset the error but it is better to get HP to look at it as not wise to fool around with power components (especially if it can be fire, safety and health hazard).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2021 06:41 PM
08-16-2021 06:41 PM
Re: i have similar error Proliant DL20 Gen10, please help
Hi,
Good day!
These messages doesnt seems to be harmful.
What we see is the messages are related to power monitoring and it could be a BIOS issue which should be addressed by BIOS update.
These error messages can be avoided by blacklisting the "acpi_power_meter" module causing the IPMI region to be used. The acpi_power_meter module seems to be causing this issues, The messages are a sign that some power management features may not be usable and these messages can be considered informational and not a harmful error and can be ignored.
# echo "blacklist acpi_power_meter" >> /etc/modprobe.d/hwmon.conf
You may try updating BIOS and check.
Thank you
RamKS
I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]