On Apr 28, Tony Houghton <h...@realh.co.uk> wrote: > udevd[435]: bind failed: Address already in use > error binding udev control socket > udevd[435]: error binding udev control socket > failed! I do not know why this happens. You will need to find out why udevd is failing to start (probably because there is already an udevd process running, but why?).
Debugging early boot ~~~~~~~~~~~~~~~~~~~~ If the system hangs at boot time or fails to boot properly, it may be useful to examine in real time what is happening while "udevadm settle" is running. A simple way to do this is: * boot the system passing "init=/bin/bash" on the kernel command line * start a getty on tty2 (or the serial console) with a command like "/sbin/getty 38400 tty2 &" * continue the boot process with "exec /sbin/init single" The open console can be used to check which processes are running and what they are waiting for. > I'm not 100% sure, but I think this is caused by conflicting timestamps. Not this. > However, I noticed that timestamps of early parts of the boot sequence > in the logs were an hour ahead, so /etc/default/rcS doesn't seem to be > taking effect until some point after udev tries to start. But once the This is even documented in README.Debian. -- ciao, Marco
signature.asc
Description: Digital signature
