Bug#624469: Intermittent failure to start.

2011-05-13 Thread josh 
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-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#624469: Intermittent failure to start.

2011-05-13 Thread Marco d'Itri 
On May 13, j...@joshtriplett.org wrote:

 Does udevd normally have multiple processes?
Yes. It would be useful to determine if the problem is that:
- there is a race between the initial wildcard expansion by the shell
  and further forking by udev, or
- the killed processes do not die quickly enough

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Bug#624469: Intermittent failure to start.

2011-05-13 Thread Josh Triplett 
On Fri, May 13, 2011 at 09:44:44PM +0200, Marco d'Itri wrote:
 On May 13, j...@joshtriplett.org wrote:
 
  Does udevd normally have multiple processes?
 Yes. It would be useful to determine if the problem is that:
 - there is a race between the initial wildcard expansion by the shell
   and further forking by udev, or
 - the killed processes do not die quickly enough

I'll compare the PIDs in the trace to the PIDs in the subsequent ps
listing.

- Josh Triplett



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#624469: Intermittent failure to start.

2011-05-12 Thread Marco d'Itri 
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.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Bug#624469: Intermittent failure to start.

2011-05-11 Thread Marco d'Itri 
On May 11, Josh Triplett j...@joshtriplett.org 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?

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Bug#624469: Intermittent failure to start.

2011-05-08 Thread Marco d'Itri 
On May 08, Josh Triplett j...@joshtriplett.org wrote:

 Any chance this represents a conflict with udev from the initramfs?
This is the only explanation, but in this case you should see the old
process with ps.
Try again by immediately running something like strace -v -s 200 udevd
at the shell prompt so we can see exactly why it is failing to start.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Bug#624469: Intermittent failure to start.

2011-05-07 Thread Josh Triplett 
Package: udev
Version: 168-1
Followup-For: Bug #624469

One more note: this occurred after a fresh install of stable and upgrade
to unstable, with no unusual steps taken.

- Josh Triplett

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udev depends on:
ii  debconf [debconf-2.0]1.5.39  Debian configuration management sy
ii  libc62.13-2  Embedded GNU C Library: Shared lib
ii  libselinux1  2.0.98-1+b1 SELinux runtime shared libraries
ii  libudev0 168-1   libudev shared library
ii  libusb-0.1-4 2:0.1.12-17 userspace USB programming library
ii  lsb-base 3.2-27  Linux Standard Base 3.2 init scrip
ii  util-linux   2.17.2-9.1  Miscellaneous system utilities

Versions of packages udev recommends:
ii  pciutils  1:3.1.7-9  Linux PCI Utilities
ii  usbutils  1:001-1Linux USB utilities

udev suggests no packages.

-- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/reboot_needed:
  udev/sysfs_deprecated_incompatibility:



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org