I spoke too soon. The init='/sbin/init --verbose' trick worked, until I accepted an update that was a new version of the mountall package. Now I have the old behavior even with --verbose . Sigh. I don't _know_ that mountall caused the problem. I was working on other stuff and only discovered the problem later.
Remember the old, old advice. If it is working, don't touch _anything_ ! Not that I tried both 2.6.32-22-generic and 2.6.32-21-generic, but that did not fix the problem. Attached is a syslog that includes the working runs and then the broken ones. I tried to comment it. I think there is now evidence of the problem. Look for when init: tty4 goal changed from stop to start .... May 16 14:36:04 autoaud-broad1 kernel: [ 0.030000] CPU 3/0x3 -> Node 0 May 16 14:36:04 autoaud-broad1 kernel: [ 0.030000] CPU: Physical Processor ID: 0 May 16 14:36:04 autoaud-broad1 kernel: [ 0.030000] CPU: Processor Core ID: 3 >>>> tty4 is starting when the CPUs are not yet fully initialize????? May 16 14:36:04 autoaud-broad1 init: tty4 goal changed from stop to start May 16 14:36:04 autoaud-broad1 kernel: [ 0.650088] CPU3: AMD Phenom(tm) II X4 955 Processor stepping 02 ** Attachment added: "syslog" http://launchpadlibrarian.net/48570840/syslog -- upstart (/sbin/init) fails to start many /etc/init and /etc/rc2.d files https://bugs.launchpad.net/bugs/581291 You received this bug notification because you are a member of Registry Administrators, which is the registrant for NULL Project. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : registry@lists.launchpad.net Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
