Udevd goes haywire, stops booting process completely

Bug #65711 reported by Erik Andrén
2
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
High
Scott James Remnant (Canonical)

Bug Description

Using Edgy current.

The boot process hangs 1/2 of the times on my Dell C640 when on battery power with the following error message:
kill: Could not kill pid `1825` : No such process

These messages show up for a brief while a bit earlier in the boot process:
udevd init: udevd socket bind failed, address already in use
udevd init: error initializing udevd socket, address already in use

It doesn't really hang but the machine doesn't react to keyboards strokes.
I haven't been able to reproduce the error while editing out the quiet and splash boot options in grub.

Could this be some kind race condition?

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

This is caused by some dodgy shell in the initramfs, replacing with pkill in feisty

Changed in udev:
assignee: nobody → keybuk
importance: Undecided → High
status: Unconfirmed → Fix Committed
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

 udev (103-0ubuntu1) feisty; urgency=low
 .
   * New upstream release:
     - %e enumeration removed.
     - MODALIAS key and substitution removed.
     - Most keys renamed (see RELEASE-NOTES).
     - Direct writing to sysfs attributes now supported.
 .
   * Update patches:
     - 40-udevtrigger-filters.patch: dropped, the spirit of this patch is
       merged upstream and we don't need most of it anymore.
     - 45-udevtrigger-sort.patch: dropped, merged upstream.
     - 60-vol_id-swap.patch: dropped, merged upstream.
     - 70-ifrename.patch: largely merged upstream, keep support for "eth*"
       incrementing in 70-rename-netif-increment.patch.
 .
   * Simplify the initramfs handling somewhat. We now just trigger
     everything, and don't wait for things to settle; instead relying on the
     loop in mountroot() which will do exactly the right thing,
   * Use pkill instead of shell /proc iteration to kill udevd. Ubuntu #65711.
 .
   * Drop most WAIT_FOR_SYSFS rules, increase kernel requirement to 2.6.19.
   * Rework rules file to newer attributes and naming. Drop some symlinks
     where they are not part of devices.txt and no other distribution
     supplies them.
 .
   * Rename libvolumeid0 and libvolumeid-dev to libvolume-id0 and
     libvolume-id-dev to match Debian.
   * Restore the "writing udev rules" documentation now that it's not wildly
     inaccurate.

Changed in udev:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.