[Bug 936293] Re: upstart 1.4-0ubuntu7 causes systems with custom kernel not to boot

[James Hunt]

OK, sounds like you're in unchartered territory then. Try adding
"init=/bin/sh" to the grub command line and booting, then:

1) See what "ulimit -n" shows.

  If it is < 1024, that might be your problem so try setting 'nofile' manually to atleast 1024 and then manually exec-ing upstart:
  
  ulimit -n 1024
  exec /sbin/init --debug </dev/console >/dev/console 2>&1

2) If (1) doesn't appear to be the problem check your root disk is
mounted as expected. Is it mounted read-write? Does the following help:

  mount -oremount,rw   /
  exec /sbin/init --debug </dev/console >/dev/console 2>&1

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

Title:
  upstart 1.4-0ubuntu7 causes systems with custom kernel not to boot

Status in “upstart” package in Ubuntu:
  New

Bug description:
  Upstart 1.4-0ubuntu7 has caused two of my systems with custom kernels
  to fail to boot again.  This appears to have to do with boot logging,
  which caused the same problem in a previous release and was re-enabled
  for 1.4-0ubuntu7.  When attempting to boot the custom kernel, the
  system just sits there flashing the cursor instead of doing anything
  useful.  Reverting to 1.4-0ubuntu6 works around the problem.

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