Scott James Remnant
scott at netsplit.com
Sun Oct 25 16:09:34 GMT 2009
On Thu, 2009-10-22 at 14:07 +0300, Janne Karhunen wrote:
> On Wed, Oct 21, 2009 at 5:59 PM, Scott James Remnant <scott at netsplit.com> wrote:
> >> Kernel panic - not syncing: Attempted to kill init!
> > Huh, that's kinda unusual - have you checked whether init is crashing?
> > Maybe init=/bin/bash, set ulimit -c to unlimited, then see if you get
> > other messages?
> It may be upstart after all goofing up the console somehow. Crash
> is due to following;
> stat64("/dev/fd", 0x7efc3978) = -1 ENOENT (No such file or directory)
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
> Kernel panic - not syncing: Attempted to kill init!
It certainly shouldn't crash when that happens!
I don't suppose you have a core dump, if so, could you get a backtrace
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20091025/a9400386/attachment.pgp
More information about the upstart-devel