[Bug 218789] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2 in logs

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=218789

Heikki Krogerus (heikki.krogerus@linux.intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |heikki.krogerus@linux.intel
                   |                            |.com

--- Comment #4 from Heikki Krogerus (heikki.krogerus@linux.intel.com) ---
This looks like a symptom caused by an issue in the EC driver. The complete
error in your dmesg:

...
[   12.563832] ACPI Error: No handler for Region [ECSI] (000000007b8176ee)
[EmbeddedControl] (20230628/evregion-130)
[   12.564906] ACPI Error: Region EmbeddedControl (ID=3) has no handler
(20230628/exfldio-261)
[   12.566187] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error
(AE_NOT_EXIST) (20230628/psparse-529)
[   12.567909] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error
(AE_NOT_EXIST) (20230628/psparse-529)
[   12.569254] ACPI: \_SB_.UBTC: failed to evaluate _DSM
c298836f-a47c-e411-ad36-631042b5008f (0x6)
[   12.569259] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
...

The handler for the EC operation region is missing, which is very odd, because
the EC driver (drivers/acpi/ec.c) has clearly been loaded successfully based on
your the same dmesg output.

Can you also attach the acpidump output:

 % acpidump -o my_acpi.dump

The ACPI guys should take a look at this. I think this is to core issue here:
"ACPI Error: Region EmbeddedControl (ID=3) has no handler"

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.