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

James Hunt 912558 at bugs.launchpad.net
Fri Jan 6 20:37:06 UTC 2012


@Kaulbach: Thank you for taking the time to transcribe the panic.

A full fix for this problem has already been written but requires new
test cases to be written too (it also requires the full test suite to be
run extensively).

Rest assured, we intend to put out an updated Upstart package as soon as
possible with logging re-enabled.

-- 
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
Status in “upstart” source package in Precise:
  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




More information about the foundations-bugs mailing list