Red Bear OS
260003331e
Three bugs in the xHCI endpoint-restart path used by all error recovery (stall hard reset, transaction-error soft retry, resource retry, split/babble hard reset): 1. Latent deadlock: restart_endpoint held the port_states write guard across set_tr_deque_ptr(), which internally re-acquires a read guard on the same key (std RwLock read-while-write on one thread). Unobserved because error injection is not yet exercised at runtime (P8-C). Fixed by scoping phase-1 ring priming so the guard drops before the async command. 2. Doorbell ordering violated xHCI spec 4.6.8/4.6.10: after Reset Endpoint the TR Dequeue Pointer is undefined, so Set TR Dequeue Pointer must complete BEFORE the doorbell transitions the endpoint Stopped->Running. The old order (doorbell first) ran the endpoint with an undefined dequeue pointer — undefined xHC behavior on real hardware. Linux rings the doorbell from the Set TR Dequeue command completion path (xhci_handle_cmd_set_deq, ring.c:1416-1554); xhcid now issues Set TR Dequeue, awaits completion, then rings. 3. Priming NoOp never executed: ring.register() was captured after ring.next() advanced the enqueue index, so the dequeue pointed past the NoOp (dead TRB). Now captured before next(), priming the hardware dequeue AT the NoOp so the xHC executes it on restart — same semantics as Linux xhci_move_dequeue_past_td pointing at the first valid TRB. Verified: cargo check clean (138 warnings, unchanged), 43/43 tests pass.
Base
Repository containing various system daemons, that are considered fundamental for the OS.
You can see what each component does in the following list:
- audiod : Daemon used to process the sound drivers audio
- bootstrap : First code that the kernel executes, responsible for spawning the init daemon
- daemon : Redox daemon library
- drivers
- init : Daemon used to start most system components and programs
- initfs : Filesystem with the necessary system components to run RedoxFS
- ipcd : Daemon used for inter-process communication
- logd : Daemon used to log system components and daemons
- netstack : Daemon used for networking
- ptyd : Daemon used for pseudo-terminal
- ramfs : RAM filesystem
- randd : Daemon used for random number generation
- zerod : Daemon used to discard all writes and fill read buffers with zero
How To Contribute
To learn how to contribute you need to read the following document:
If you want to contribute to drivers read its README
Development
To learn how to do development with these system components inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
It is recommended to build this system component via the Redox build system, you can learn how to do it on the Building Redox page.
To build and test outside the build system, install redoxer then use check.sh script to build or test:
./check.sh- Check build for x86_64./check.sh --arch=ARCH- Check build for specific ARCH (aarch64,i586,riscv64gc)./check.sh --all- Check build for all ARCH./check.sh --test- Check the base system boots up on x86_64
You can also use make install to inspect the content on ./sysroot, or make test-gui to test booting with orbital interactively.