| Previous | Next |
| kIOReturnNoSpace | kIOReturnCannotWire |
kIOReturnPortExists
Not automatically a network-port conflict
kIOReturnPortExists means that a port already exists. The common IOKit header does not define the type of port or the ownership scope for this status, so it should not automatically be interpreted as a TCP or UDP bind failure. Its meaning depends on the IOKit API, service, or driver path that reported it.
The usual diagnostic question is whether the caller repeated a registration, listener, notification, or port-creation step without first disposing of the earlier object. A duplicate can also follow a lifecycle race in which the client assumes a prior teardown completed when the service still retains the existing port state.
How to investigate
- Log the exact creation or registration API, the requested identifier, service instance, and object lifetime.
- Check whether a previous successful call must be paired with an explicit remove, close, or release operation.
- Serialize create and teardown paths so a second registration cannot race with cleanup.
- Inspect the family-specific documentation before choosing any recovery action; the common status does not define one.
References
- Apple XNU source: IOReturn.h
- Apple: IOKit architectural overview
- Apple: Introduction to IOKit Fundamentals
Looking for a different code? Search another status or error code.