Should I be concerned about these ACPI boot messages?

M

Mayhem30

Should I be concerned about these ACPI boot messages? The server appears to be running fine. I'm using FreeBSD 14.2-RELEASE

These appear near the start of boot :

Code: 
ACPI Error: No handler for Region [WST1] (0xfffff80106708800) [GenericSerialBus] (20221020/evregion-292)
ACPI Error: Region GenericSerialBus (ID=9) has no handler (20221020/exfldio-428)
ACPI Error: Aborting method \134_SB.PCI0.I2C0.PAS1 due to previous error (AE_NOT_EXIST) (20221020/psparse-689)
ACPI Error: Aborting method \134_GPE._L42 due to previous error (AE_NOT_EXIST) (20221020/psparse-689)
ACPI Error: AE_NOT_EXIST, while evaluating GPE method [_L42] (20221020/evgpe-708)

These appear near the end of boot :

Code: 
acpi_wmi0: <ACPI-WMI mapping> on acpi0
acpi_wmi0: cannot find EC device
acpi_wmi0: Embedded MOF found
ACPI: \134_GPE.AMW0.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi1: <ACPI-WMI mapping> on acpi0
acpi_wmi1: cannot find EC device
acpi_wmi2: <ACPI-WMI mapping> on acpi0
acpi_wmi2: cannot find EC device
acpi_wmi2: Embedded MOF found
ACPI: \134_SB.WFDE.WQCC: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi3: <ACPI-WMI mapping> on acpi0
acpi_wmi3: cannot find EC device
acpi_wmi3: Embedded MOF found
ACPI: \134_SB.WFTE.WQCC: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi4: <ACPI-WMI mapping> on acpi0
acpi_wmi4: cannot find EC device
acpi_wmi4: Embedded MOF found
ACPI: \134_SB.AMW0.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi5: <ACPI-WMI mapping> on acpi0
acpi_wmi5: cannot find EC device
acpi_wmi5: Embedded MOF found
ACPI: \134_SB.AMW4.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi6: <ACPI-WMI mapping> on acpi0
acpi_wmi6: cannot find EC device
acpi_wmi6: Embedded MOF found
ACPI: \134_SB.AMW2.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi7: <ACPI-WMI mapping> on acpi0
acpi_wmi7: cannot find EC device
acpi_wmi7: Embedded MOF found
ACPI: \134_SB.AMW5.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
 
No. Don't worry about them. I have an older machine which has similar errors. Likely your BIOS doesn't support some functions.

If your machine works fine, then don't worry about the messages.

BTW, is your machine older or bleeding edge by any chance?
 
It's pretty new ... not sure what the motherboard is, but It has :

Intel Xeon W-1290P CPU
128 GB Ram
2 x 256GB NVMe
 
That's not a brand new machine.

What I'm looking for is,

- Is it so old that FreeBSD calls ACPI functions not supported on old hardware?

- Is the hardware that new that FreeBSD is not calling some ACPI function.

This is probably a BIOS issue of sorts. Either way it's harmless. If your machine works it's just noise that pollutes your boot messages. You can ignore the messages.

When it comes to ACPI, when something breaks you won't see any messages. For instance, an older laptop (Acer 4752) worked fine under 15-CURRENT until an ACPI update was imported into FreeBSD. After that it failed to wake-on-lan when it was plugged into its power supply (into the wall). Unplugging it allowed wake-on-lan to work. I discovered our upstream ACPI developer had patched their sources (which I don't recall the details) resulting in my not being able to remotely power on this laptop. Reverting the upstream commit locally resolved the problem. I reported the problem and a fix to our upstream ACPI developer, who rejected my patch.

When ACPI breaks you will not see error messages and the messages you do see here are innocuous. Just ignore them.
 
You must log in or register to reply here.
Back
Top