What does errno 101 (ETIME) mean?

 
Could be also:
ConstantTypeOS
ERROR_EXCL_SEM_ALREADY_OWNEDWin32 errorWindows
HTTP_STATUS_SWITCH_PROTOCOLSHTTP CodeAny
ENETUNREACHerrnoLinux
EADDRNOTAVAILerrnoWindows
MEMORY1_INITIALIZATION_FAILEDBugCheck CodeWindows
Previous Next
ENETUNREACH EADDRNOTAVAIL

ETIME

This page examines Darwin STREAMS ioctl timeout. A STREAMS control transaction did not complete within its protocol timeout.

The returning interface matters

Darwin BSD system-call handling: Darwin streams ioctl timeout belongs to Darwin errno and should be decoded with the exact SDK or XNU header used by the target. Darwin extensions and legacy STREAMS names related to this error can differ in availability or numbering on other UNIX-like systems. The wording attached to ETIME is a clue to the original interface, not proof that a similarly named modern subsystem returned it.

Darwin assigns platform-specific meanings and numbers to several non-POSIX errno symbols. Do not decode the integer with a Linux table or assume the same symbol is produced by the same API on another OS.

Incident record

EvidenceQuestion it answers
Ioctl, timeout, module stack, pending message, producer/driver state, and wakeup events.Ties this error to one live API object instead of a translated message.
Darwin errno value and the SDK/XNU header version used to decode it.Shows whether this error arose in the caller ABI, wrapper, or provider.
First syscall/ioctl return plus process, thread, and object generation.Preserves the first boundary before errno can be overwritten.
Known-good object of the same class on the same macOS build.Provides a same-platform known-good comparison.

Capture errno immediately after the failing call that produced this error before formatting, tracing, allocation, or cleanup code runs. Retain the function return value as well because many C interfaces signal failure there and use errno only as secondary detail.

Controlled comparisons

  1. Issue a minimal control request with the same endpoint while monitoring completion. A changed errno after this test is a new boundary, not another spelling of this error.
  2. Capture errno immediately and compare the paired return value. Repeat the original operation after the control so the result remains relevant to this error.
  3. Repeat with one controlled object while keeping identity and sandbox unchanged. Keep the binary, header ABI, and provider fixed.

Two observations are especially discriminating here: Ioctl, timeout, module stack, pending message, producer/driver state, and wakeup events. Use this control for comparison: issue a minimal control request with the same endpoint while monitoring completion. Those two observations separate a stale identifier or unsupported request from a provider-wide failure without broad changes to the host.

Nearby interpretations

Tempting assumptionSafer interpretation
The English phrase is assumed to be portablethis error belongs to Darwin BSD system-call handling; verify the target headers and returning API before applying another platform's errno table
A retry succeeded and erased the original evidenceThe retry can replace this error with a different state; preserve the first call, numeric value, and object generation beforehand

If a wrapper converts this error to an exception or Boolean, instrument below that wrapper. The decisive record is the syscall, ioctl, CRT function, or compatibility entry point that first exposed the value.

Resolution criteria

Targeted correction. Repair the nonresponding module/peer and implement bounded retry with cancellation.

Regression proof. Controls complete or time out predictably without leaving stuck messages or reused state. Verify one supported boundary case and one deliberate negative case so handling of this error remains explicit.

Technical references

References for Darwin BSD system-call handling ETIME on the deployed platform version.


Looking for a different code? Search another status or error code.