Reproducer attached. I can use this to reliably reproduce the busy loop on my laptop and in a VM. So hopefully this provides the clues we need!
In the process of refining this test case, I also repeatedly ran into a panic (!= EIO assertion failure in log.c), but I haven't been able to figure out again how to reproduce the error. Maybe there's another related bug lingering, or maybe it's a different manifestation of the same bug. ** Attachment added: "upstart-busyloop.conf" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/922754/+attachment/2700904/+files/upstart-busyloop.conf ** Changed in: upstart (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922754 Title: booting without --no-log causes init and plymouth-upstart-bridge to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/922754/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
