| Previous | Next |
| STATUS_ABIOS_LID_ALREADY_OWNED | STATUS_ABIOS_INVALID_COMMAND |
STATUS_ABIOS_NOT_LID_OWNER
A valid LID can still be rejected because the caller does not own it
STATUS_ABIOS_NOT_LID_OWNER should be read as a caller-versus-resource state mismatch. ABIOS requests identify a device through a Logical ID in the common request block, and IBM documentation describes LIDs as indices into initialized device information. The Windows status family separately names nonexistent, already-owned, and not-owned LID conditions. Consequently, seeing a valid device or a valid numeric LID is not enough to prove that the current driver context may issue the requested operation.
The most valuable evidence is the ownership lifecycle before the failure. Trace driver initialization, acquisition, reset, unload, and re-entry. A stale context can retain a LID number after another component has become the owner; a failed partial initialization can also reach a service routine without completing the step that establishes ownership. The exact Windows implementation of ABIOS ownership is not publicly specified, so the status should not be mapped to a modern handle or mutex model without evidence.
When comparing with STATUS_ABIOS_LID_ALREADY_OWNED, note the direction of the conflict. An already-owned result is useful at claim time; a not-owner result is useful at operation time because it says the caller lacks the ownership state expected for the addressed LID. Capture the requesting module, request-block LID/function fields, current ABIOS table, and prior acquire/release events. Reinitializing the hardware blindly may hide the software ownership bug without explaining it.
What to inspect
- Trace the LID acquisition/release lifecycle for the requesting module.
- Record the request-block LID and function together with the caller identity.
- Compare the current owner with the caller before resetting or reassigning the device.
References
- IBM: Advanced BIOS (ABIOS) manual
- IBM: ABIOS for PS/2 computers and compatibles
- IBM: PS/2 Hardware Interface Technical Reference
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.