kernel: ACPI Error: Region IPMI (ID=7) has no handler (20190816/exfldio-261)

[sandeepkar99]

Error message:
ACPI message keep on showing in every min

================= 
kernel: ACPI Error: Region IPMI (ID=7) has no handler (20190816/exfldio-261)
kernel: ACPI Error: Aborting method \_SB.PMI0._PMM due to previous error (AE_NOT_EXIST) (20190816/psparse-529)
kernel: ACPI Error: AE_NOT_EXIST, Evaluating _PMM (20190816/power_meter-325)
kernel: ACPI Error: No handler for Region [POWR] (00000000985bfed4) [IPMI] (20190816/evregion-127)
================

$dmidecode | grep -i product
Product Name: ProLiant DL360 Gen10

Kernel version
================
[root@<hostname> ~]$ uname -a
Linux <hostname> 5.4.50-1.el7.x86_64 #2 SMP Thu Jul 2 21:54:12 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
=======================================================================================================
[root@ul5g24 ~]$ lsmod | grep ipmi
ipmi_si 65536 0
ipmi_devintf 20480 0
ipmi_msghandler 106496 2 ipmi_devintf,ipmi_si

$ modinfo ipmi_si
filename: /lib/modules/5.4.50-1.el7.x86_64/kernel/drivers/char/ipmi/ipmi_si.ko
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
srcversion: A8DAC081BD11E3D1AD91825
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
retpoline: Y
intree: Y
name: ipmi_si
vermagic: 5.4.50-1.el7.x86_64 SMP mod_unload modversions
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)

$ dmidecode -t bios
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.2 present.
# SMBIOS implementations newer than version 3.0 are not
# fully supported by this version of dmidecode.

Handle 0x0003, DMI type 0, 26 bytes
BIOS Information
Vendor: HPE
Version: U32
Release Date: 04/18/2019
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16384 kB
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.4
Firmware Revision: 1.40

How to fix the issue?
I know one solution is to remove the modules.
How we can fix it without removing the modules?

[parnassus · Accepted solution]

Hello, you posted on the wrong forum (HPE Community -> Networking -> Switching and Rounting -> Comware based)...you should re-post it entirely (or kindly ask the Forum administrators to move it) into the correct Community Forum which should be, giving the fact you cited an HPE ProLiant DL360 Gen10 server, this one instead (HPE Community -> Server and Operating Systems -> ProLiant -> ProLiant Servers (ML,DL,SL)). Pay attention WHERE you post...Networking is not Servers and vice-versa...otherwise you risk your post to pass totally unaswered.

[sandeepkar99]

Hi,

I have reposted the query in the correct forum. Thank you for the help.