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

[Dave Walker]

Whilst looking for others that have encountered this, I came across an
unreferenced pastebin http://pastebin.com/sPwXJS0x , seems to be the
same issue.

...
init: log.c: 291: Assertion failed in log_io_error_handler: err-> number == EIO
init: Caught abort, core dumped
init: io.c: 1312: Unhandled error from nih_io_destroy: bad file descriptor
init: Caught abort, core dumped
kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Tainted: P     C O 3.2.0-7-generic #13-Ubuntu
Call Trace:
[<ffffffff81639ce7>] panic+0x91/0x1a7
[<ffffffff81069205>] forget_original_parent+0x245/0x250
[<ffffffff81069227>] exit_notify+0x17/0x160
[<ffffffff81069b03>] do_exit+0x1f3/0x420
[<ffffffff81141713>] ? do_munmap+0x1f3/0x2f0
[<ffffffff81069ed4>] do_group_exit+0x44/0xa0
[<ffffffff81069f47>] sys_exit_group+0x17/0x20
[<ffffffff8165a5c2>] system_call_fastpath+0x16/0x1b
...


** Changed in: upstart (Ubuntu)
   Importance: Undecided => Critical

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

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