[Bug 922754] Re: booting without --no-log causes init and plymouth-upstart-bridge to spin at 100%
James Hunt
922754 at bugs.launchpad.net
Fri Feb 3 16:05:02 UTC 2012
** Changed in: upstart (Ubuntu)
Status: Triaged => In Progress
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => Fix Committed
** Changed in: upstart
Importance: Undecided => High
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
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:
In Progress
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
More information about the foundations-bugs
mailing list