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

[Steve Langasek]

Stefan, is this on real hardware or in a VM?  Can you attach the
/proc/cmdline used?

Is plymouth itself still running at this point?  even with upstart
banging on the cpu like this, it shouldn't take too long for the boot
sequence to finish and plymouth to stop, at which point the bridge
should also go away... but it doesn't sound like that's what happened to
you.

** Changed in: upstart (Ubuntu)
       Status: New => Incomplete

-- 
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” package in Ubuntu:
  Incomplete

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/ubuntu/+source/upstart/+bug/922754/+subscriptions