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

James Hunt 912558 at bugs.launchpad.net
Fri Jan 6 10:50:48 UTC 2012


It seems that a particular job or combo of jobs is causing this issue,
but unclear why (since all jobs are treated equally by the logger).

I'm currently working with Dave to try and isolate the job(s) causing
the failure. I'll also create a PPA with some extra debug to identify
what err->number is set to. It's looking like EBADF from the
stackstrace.

-- 
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




More information about the foundations-bugs mailing list