[Bug 922754] Re: booting without --no-log causes init and plymouth-upstart-bridge to spin at 100%

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.4-0ubuntu5

---------------
upstart (1.4-0ubuntu5) precise; urgency=low

  * Merge of important upstream log fixes to handle scenario attempts
    are made to exec(3) directly non-existent commands. (LP: #922754)
 -- James Hunt <james.hunt at ubuntu.com>   Fri, 03 Feb 2012 14:16:40 +0000

** Changed in: upstart (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  booting without --no-log causes init and plymouth-upstart-bridge to
  spin at 100%

Status in Upstart:
  Fix Committed
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  Release: Precise
  Architecture: amd64

  Likely broken since upstart_1.4-0ubuntu3

  When booting after recent updates I see init and plymouth-upstart-
  bridge spinning at 100% CPU time, defunct processes do not get reaped
  and a console on ttyS1 which is supposed to start, does not come up.

  Looking at strace of plymouth-upstart-bridge it seems to run a tight loop of 
  epoll_wait(3, {}, 64, 0)                = 0 (/proc/1383/fd/3 -> anon_inode:[eventpoll])

  and init does another tight loop of
  read(24, 0x7ffdc2d1caa0, 8192)          = -1 EAGAIN (Resource temporarily unavailable)
    (/proc/1/fd/24 -> /dev/ptmx)

  Booting with --no-log on the grub commandline brings the system up
  without showing any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/922754/+subscriptions