On Thu, May 12, 2011 at 11:46:23AM +0200, Marco d'Itri wrote:
> On May 11, Marco d'Itri <m...@linux.it> wrote:
>
> > > bind(3, {sa_family=AF_FILE, path=@"/org/kernel/udev/udevd"}, 25) = -1
> > > EADDRINUSE
> > > (Address already in use)
> > OK, so it looks like that there *is* an udevd process left around by
> > the initramfs.
> > Can you confirm this with ps at the first prompt?
> If this is true, then please add set -x to init-bottom/udev to
> understand why all processes are not being killed.
I confirmed via ps that udevd --daemon remains running, in 'Ds' state.
I booted with break=top, and edited init-bottom/udev to add "set -x",
then exited the shell to continue the initramfs. The trace showed the
loop over /proc/ directories running, finding process with exe -> /sbin/udevd
as PID 284 and
calling "kill" on it, then finding another process with exe -> /sbin/udevd as
PID 68 and calling "kill" on that too. It then reaches the end of the loop,
and runs:
udev_root=/dev
[ -e /etc/udev/udev.conf ]
. /etc/udev/udev.conf
udev_log=err
mount -n -o move /dev /root/dev
nuke /dev
ln -s /root/dev /dev
Does udevd normally have multiple processes?
- Josh Triplett
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
