Upstart 1.4 causes boot lockup with custom kernel
Bug #911946 reported by
Michael Marley
This bug report is a duplicate of:
Bug #912558: log.c Assert failed - err=>number == EIO.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I just upgraded to Upstart 1.4 on my Precise x64 system with a custom kernel (which lacks initramfs and a few other fs-related things that come in the stock kernel.) After the upgrade, my system fails to boot. The kernel starts, but Upstart never seems to start. The system just sits there flashing the cursor on a blank screen until I reset the computer. The stock kernel still works fine. Reverting back to 1.3 causes the problem to go away. I have attached my kernel configuration. I can also attach other info about my system, but I don't think the logs will be useful because it doesn't boot far enough to where it can actually write logs to the disk.
Revision history for this message
| Michael Marley (mamarley) wrote | #1 |
To post a comment you must log in.
