linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sreen Tallam" <tallam.sreen@gmail.com>
To: "Sebastian Siewior" <linuxppc-embedded@ml.breakpoint.cc>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel Panic - not syncing: Attempted to kill init!
Date: Thu, 10 Apr 2008 09:53:30 -0700	[thread overview]
Message-ID: <5b1d25eb0804100953u38f514dblaccbb3477c532b23@mail.gmail.com> (raw)
In-Reply-To: <20080410085030.GA27907@Chamillionaire.breakpoint.cc>

Hi Sebastian,

Thank you for looking into this issue.
But I am not using udev. And my /dev is empty, there is no devices in there.

Any more hints on this. I would appreciate your follow up.

Thanks,
Sreen

On Thu, Apr 10, 2008 at 1:50 AM, Sebastian Siewior
<linuxppc-embedded@ml.breakpoint.cc> wrote:
> * Sreen Tallam | 2008-04-09 19:07:01 [-0700]:
>
>
>  >VFS: Mounted root (jffs2 filesystem) readonly.
>  >Freeing unused kernel memory: 156k init
>  >Warning: unable to open an initial console.
>  >init/main.c -- 819
>  >init/main.c -- 821
>  >init/main.c -- 844
>  >init/main.c -- 704 -- /sbin/tallam_init<0>Kernel panic - not syncing:
>  >Attempted to kill init!
>  >Call Trace:
>  >[C3FE7E60] [C0006D98]  (unreliable)
>  >[C3FE7EA0] [C001F150]
>  >[C3FE7EF0] [C0023630]
>  >[C3FE7F30] [C0023734]
>  >[C3FE7F40] [C000DBC0]
>  > <0>Rebooting in 180 seconds..
>  >
>
>  This looks like you are missing /dev/console and probably /dev/null. You
>  need atleast those two nodes in your rootfs if you are using udev. You
>  will need a static /dev if you don't use udev/mdev.
>
>  >Thanks,
>  >Sreen
>  Sebastian
>

      reply	other threads:[~2008-04-10 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10  2:07 Kernel Panic - not syncing: Attempted to kill init! Sreen Tallam
2008-04-10  8:50 ` Sebastian Siewior
2008-04-10 16:53   ` Sreen Tallam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5b1d25eb0804100953u38f514dblaccbb3477c532b23@mail.gmail.com \
    --to=tallam.sreen@gmail.com \
    --cc=linuxppc-embedded@ml.breakpoint.cc \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).