[Bug 912558] Re: log.c Assert failed - err=>number == EIO

[VinDSL]

I meant to type 5-Jan-2012 (not 2011) above...  sigh!

Anyway, I thought I should also mention, immediately preceding the
kernel panic/core dump, a little flashing white line appears in
Plymouth... and the end of the animated dots.  Never saw that before.

After I implemented the --no-log workaround, the (previously) flashing
white line was replaced with a message about CUPS, after which it
continues the normal boot sequence, rather than crashing.  Never saw
that before, either.

This odd behavior may, or may not, be indicative.  Moreover, I don't
have a printer installed on this machine (local or network). LoL!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/912558

Title:
  log.c Assert failed - err=>number == EIO

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Whilst booting, init has an issue and causes a core dump -> kernel
  panic.

  Appending --no-log to the kernel cmd line allows a successful boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/912558/+subscriptions