I see the same error while trying to boot from nfs. I saw it in syslog of the nfs client (after getting a sulogin console). Is this normal? I see that udev-fallback-graphics also failed, is this related? Why, is it a fatal error that graphics cannot be started? That does not make much sense to me. After this, the system tends to freeze, silently.
Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics main process (1295) terminated with status 1 Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics goal changed from start to stop Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics state changed from running to stopping Jun 1 10:46:11 cylon-fermi-unset init: Handling stopping event Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics state changed from stopping to killed Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics state changed from killed to post-stop Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics state changed from post-stop to waiting Jun 1 10:46:11 cylon-fermi-unset init: Handling startup/failed event Jun 1 10:46:11 cylon-fermi-unset init: Handling stopped/failed event Jun 1 10:46:11 cylon-fermi-unset init: Handling stopped event Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash goal changed from stop to start Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from waiting to starting Jun 1 10:46:11 cylon-fermi-unset init: Handling starting event Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from starting to pre-start Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from pre-start to spawned Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash main process (1303) Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from spawned to post-start Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from post-start to running Jun 1 10:46:11 cylon-fermi-unset init: Handling started event Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb goal changed from stop to start Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from waiting to starting Jun 1 10:46:11 cylon-fermi-unset init: Handling starting event Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from starting to pre-start Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from pre-start to spawned Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb main process (1304) Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from spawned to post-start Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from post-start to running Jun 1 10:46:11 cylon-fermi-unset init: Handling started event Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb main process (1304) exited normally Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb goal changed from start to stop Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from running to stopping Jun 1 10:46:11 cylon-fermi-unset init: Handling stopping event Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from stopping to killed Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from killed to post-stop Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from post-stop to waiting Jun 1 10:46:11 cylon-fermi-unset init: Handling stopped event Jun 1 10:46:11 cylon-fermi-unset init: plymouth main process (871) killed by ABRT signal Jun 1 10:46:11 cylon-fermi-unset init: plymouth goal changed from start to stop Jun 1 10:46:11 cylon-fermi-unset init: plymouth state changed from running to stopping Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash main process (1303) terminated with status 2 Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash goal changed from start to stop Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from running to stopping Jun 1 10:46:11 cylon-fermi-unset init: Handling stopping event Jun 1 10:46:11 cylon-fermi-unset init: plymouth state changed from stopping to killed Jun 1 10:46:11 cylon-fermi-unset init: plymouth state changed from killed to post-stop Jun 1 10:46:11 cylon-fermi-unset init: plymouth state changed from post-stop to waiting Jun 1 10:46:11 cylon-fermi-unset init: Handling stopping event Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from stopping to killed Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from killed to post-stop Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from post-stop to waiting Jun 1 10:46:11 cylon-fermi-unset init: Handling stopped event Jun 1 10:46:11 cylon-fermi-unset init: Handling stopped event -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/782291 Title: reboot in a container gets somehow stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/782291/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
