[Bug 818177] Re: boot failures because 'udevadm exit' does not kill udevd worker threads

Steve Langasek steve.langasek at canonical.com
Fri Oct 7 05:47:31 UTC 2011


Serge,

Picking that log apart, I see one worker thread (pid 94) not exiting
cleanly, whereas all the others do.  No clear indication of why this
worker would have failed to exit since its own log output shows it
completely processing an event (seq 1072) and doesn't show it picking up
another one; but we're definitely left with references to the worker,
which is why we see the 'worker exit' message without the 'worker
cleaned up' message (and why the worker list is never empty).

Could you do a test that would correlate this udev output with a 'ps
-ef' at the end of scripts/init-bottom/udev?  It doesn't look to me like
the output from the two tests we have here match in the slightest - one
reports all worker threads exited, the other shows dozens of processes
still running...

Could you (and others) also try the udev from ppa:vorlon/ppa, and see if
this makes a difference in bootability?  This adds the pkill after
udevadm control --exit.  If it works, we know udevd is losing track of
its worker threads...

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/818177

Title:
  boot failures because 'udevadm exit' does not kill udevd worker
  threads

Status in Release Notes for Ubuntu:
  Triaged
Status in “linux” package in Ubuntu:
  Invalid
Status in “udev” package in Ubuntu:
  Triaged
Status in “linux” source package in Oneiric:
  Invalid
Status in “udev” source package in Oneiric:
  Triaged
Status in “linux” source package in p-series:
  Invalid
Status in “udev” source package in p-series:
  Triaged

Bug description:
  After running a do-release-upgrade -d on a natty server, I'm unable to
  boot the machine properly.

  It looks like it doesn't see the local disks anymore.

  I think this looks quite a lot like the debbug linked from here:
  https://bugs.launchpad.net/ubuntu/oneiric/+source/linux/+bug/746751

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-7-server 3.0.0-7.8
  ProcVersionSignature: Ubuntu 3.0.0-7.8-server 3.0.0
  Uname: Linux 3.0.0-7-server x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 2011-07-29 13:34 seq
   crw-rw---- 1 root audio 116, 33 2011-07-29 13:34 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Date: Fri Jul 29 13:40:10 2011
  HibernationDevice: RESUME=UUID=844d17fa-ff69-4250-844b-33b930236c56
  IwConfig:
   lo        no wireless extensions.
   
   eth0      no wireless extensions.
   
   eth1      no wireless extensions.
  MachineType: HP ProLiant DL380 G5
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   PATH=(custom, user)
   LANG=en_US
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-7-server root=/dev/mapper/User Name-root ro INIT_VERBOSE=yes
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-7-server N/A
   linux-backports-modules-3.0.0-7-server  N/A
   linux-firmware                          1.56
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-07-29 (0 days ago)
  dmi.bios.date: 06/28/2007
  dmi.bios.vendor: HP
  dmi.bios.version: P56
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: dmi:bvnHP:bvrP56:bd06/28/2007:svnHP:pnProLiantDL380G5:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions




More information about the foundations-bugs mailing list