Comment 2 for bug 1303139

Revision history for this message
David Oftedal (rounin) wrote :

Steve Langasek (vorlon) pointed out in bug #1269731 that the issue may in fact have been fixed, as I could have been running the old version of upstart when the error occurs.

Running the "telinit u" command after the upgrade seems to confirm this, at it does not cause a kernel panic.

Therefore, I think this was a false alarm.