| Previous | Next |
| STATUS_ACPI_MUTEX_NOT_OWNED | STATUS_ACPI_RS_ACCESS |
STATUS_ACPI_MUTEX_NOT_OWNER
STATUS_ACPI_MUTEX_NOT_OWNER is an ownership mismatch. The mutex has ownership semantics, but the current AML execution context is not the owner permitted to perform the attempted operation. This is distinct from a mutex that is simply unheld.
Diagnosis therefore needs the owner identity or execution context, not only a boolean “locked” state. Nested control-method calls and asynchronous platform events can make a shared mutex appear in more than one path, so record the calling method, ownership history and any transition that introduced the second path.
The AML execution context did not own the mutex
- Record the mutex, current owner context, requesting context and AML call chains for both where available.
- Check that the acquisition and release occur within the ownership scope required by the AML execution model.
- Compare with
STATUS_ACPI_MUTEX_NOT_OWNED; that result means no active owner exists at release time.
References
Looking for a different code? Search another status or error code.