Comment 37 for bug 1269731

I stand corrected! Now that you mention it, upstart would have been upgraded at some point during the upgrade, and that could very well have been after the upgrade of libc which caused the kernel panic.

The upgrade was from the previous version, i.e. something like 13.10, with updates installed.

Either way, after reading your post, I ran "telinit u" to verify, and this time it runs without any incident.

So it looks like it has been fixed as stated above. Apologies for the false alarm, and thank you for the explanation!