[Bug 936667] Re: Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys")

Michael Lustfield 936667 at bugs.launchpad.net
Wed Feb 29 17:16:56 UTC 2012


Seems to be working for me. I ended up putting the --no-log in grub conf.
Took it out to test and it works.

On Wed, Feb 29, 2012 at 9:36 AM, KrzysiekT
<936667 at bugs.launchpad.net>wrote:

> With upstart I can boot on 3.2.0-17.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/936667
>
> Title:
>  Upstart early job logging causes boot failure for systems with no
>  initramfs (error is "No available ptys")
>
> Status in “upstart” package in Ubuntu:
>  Confirmed
>
> Bug description:
>  When booting 12.04 after a recent update, I see "init(4): no available
>  ptys" being displayed faster than a machine gun. When I add --no-log
>  as a kernel option and I'm able to boot just fine.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667/+subscriptions
>

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

Title:
  Upstart early job logging causes boot failure for systems with no
  initramfs (error is "No available ptys")

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  When booting 12.04 after a recent update, I see "init(4): no available
  ptys" being displayed faster than a machine gun. When I add --no-log
  as a kernel option and I'm able to boot just fine.

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




More information about the foundations-bugs mailing list