From: narkewoody@gmail.com (Woody Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel panic - not syncing: Attempted to kill init!
Date: Mon, 26 Nov 2012 15:40:42 +0800 [thread overview]
Message-ID: <20121126074042.GA4034@zuhnb712.ap.bm.net> (raw)
In-Reply-To: <CAPFyZi6VYWaMmb4WVZdDyv5yrz5MTvM8k6GkY_F=MsJNBU69JA@mail.gmail.com>
Hi, Jello
It's a little strange that your reply not appear on the list (at least
at this moment).
Firstly thank you so much for the suggestion. But you know, this old
file system is working for a old 2.6 kernel, which was not built by me.
Hence I can see, this file system is okay for at least that version of
kernel.
For the situation, I want to try something from two directions:
1. Is there possible something missed from the kernel side? Any
suggestion?
2. Because it resulted in a kernel panic message, I have no good way to
trace it. Can I run something else (init=) from the root file system to
gather more information about the file system? So, how can I play with
the "init=" parameter to help for the case?
Thanks in advance.
-woody
On Thu, Nov 22, 2012 at 05:50:05PM +0800, Jello huang wrote:
> pls check u root file system.if the root file system is no filesystem or not
> * correct .the kernel shall*
> *throw the kernel panic*
>
>
> On 22 November 2012 17:19, Woody Wu <narkewoody@gmail.com> wrote:
>
> > Hi,
> >
> > "Kernel panic - not syncing: Attempted to kill init!
> > exitcode=0x0000000b"
> >
> > I got above message when I am porting 3.4.19 to a s3c2410 board. I
> > traced the execution path is: kernel_init() -> init_post() ->
> > run_init_process("/sbin/init") -> kernel_execve().
> >
> > And, in the last function kernel_execve, the call of do_execve sucessed.
> > Then I see a piece of assembly code follows which I cannot understand.
> >
> > That means, the root file system, which is mtdblock3 in my case, is
> > mounted and /sbin/init was started to execute, then I got the panic
> > message.
> >
> > Is that possible that this is caused by the root file system instead of
> > the kernel? The root file system is a very old one that can run with an
> > old kernel 2.6.14.
> >
> >
> > Do you have any clue? Thanks in advance!
> >
> > --
> > woody
> > I can't go back to yesterday - because I was a different person then.
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> >
>
>
>
> --
> Thanks
> Jello Huang
--
woody
I can't go back to yesterday - because I was a different person then.
next prev parent reply other threads:[~2012-11-26 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 9:19 Kernel panic - not syncing: Attempted to kill init! Woody Wu
2012-11-22 9:50 ` Jello huang
2012-11-26 7:40 ` Woody Wu [this message]
2012-11-26 7:51 ` Baruch Siach
2012-11-26 7:53 ` Woody Wu
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=20121126074042.GA4034@zuhnb712.ap.bm.net \
--to=narkewoody@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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