booting without --no-log causes init and plymouth-upstart-bridge to spin at 100%
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Fix Released
|
High
|
James Hunt | ||
upstart (Ubuntu) |
Fix Released
|
High
|
James Hunt |
Bug Description
Release: Precise
Architecture: amd64
Likely broken since upstart_
When booting after recent updates I see init and plymouth-
Looking at strace of plymouth-
epoll_wait(3, {}, 64, 0) = 0 (/proc/1383/fd/3 -> anon_inode:
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.
Related branches
Changed in upstart (Ubuntu): | |
importance: | Undecided → High |
Changed in upstart (Ubuntu): | |
status: | Triaged → In Progress |
Changed in upstart: | |
status: | New → Fix Committed |
importance: | Undecided → High |
assignee: | nobody → James Hunt (jamesodhunt) |
Changed in upstart: | |
status: | Fix Committed → Fix Released |
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.