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

Vincent Fortier 912558 at bugs.launchpad.net
Tue Mar 13 00:10:29 UTC 2012


** Attachment added: "Kernel call-trace when NOT using --no-log parameter"
   https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/912558/+attachment/2859647/+files/Kernel-call-trace.jpg

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

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/upstart/+bug/912558/+subscriptions




More information about the foundations-bugs mailing list