Red Bear OS
ad40fffd80
The kernel masks an IRQ line when it delivers the interrupt to userspace (trigger() -> pic_mask()/ioapic_mask()) and only re-enables it when the driver writes the count back (kwrite -> acknowledge() -> pic_unmask()/ ioapic_unmask()). That write-back is therefore mandatory, not optional. ahcid only performed it inside the `is > 0` branch. IRQ lines are shared (on q35 the AHCI controller sits on IRQ 10 with other devices), so an interrupt raised by a different device reaches the handler with the HBA interrupt status register reading 0. In that case ahcid returned without writing back, leaving the line masked permanently: every subsequent AHCI completion was lost and all disk I/O blocked forever. Move the write-back out of the branch so the line is re-armed whether or not the interrupt turned out to be ours, and keep scheme.tick() gated on `is > 0` since there is no completion to service otherwise. Device-level status is still cleared before unmasking, so this cannot cause a storm.
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.