I have a rented root server, where I have a yocto build running, which utilizes sysvinit.
After logging in, the /var/log/boot file is empty and the process is taking up to 95% of cpu usage. Also the process doesn't react on SIGINT. After some debugging, I saw, that the process is trying to open the /dev/ttyS0 device, but this fails everytime with an EIO. There's no counter for a maximal retry of EIO errors, so the process is stuck trying to open the not available serial console... I guess the serial console shouldn't return EIO in the first place (at least not the whole time), but on the other hand, in my humbled opinion, the process should be able to handle this situation. Best regards, Sven
