From: myuboot@fastmail.fm
To: linux-kernel@vger.kernel.org, "linux-mips" <linux-mips@linux-mips.org>
Subject: Kernel panic - not syncing: Attempted to kill init!
Date: Tue, 10 Nov 2009 18:22:55 -0600 [thread overview]
Message-ID: <1257898975.30125.1344591929@webmail.messagingengine.com> (raw)
In-Reply-To: <4AD906D8.3020404@caviumnetworks.com>
Hi,
I got the following error trying to bring up the /sbin/init with Kernel
2.6.31 using cramfs filesystem on a MIPS 32 board:
[ 1.160000] VFS: Mounted root (cramfs filesystem) readonly on device
31:2.
[ 1.171000] Freeing unused kernel memory: 116k freed
[ 1.223000] Kernel panic - not syncing: Attempted to kill init!
[ 1.229000] Rebooting in 3 seconds..
Using BDI I know the kernel panic happens as soon as
run_init_process("/sbin/init") in init_post() is called. The filesystem
itself seems to be ok, because I can use 'ls' command under u-boot to
see /sbin/init is a symbolic link to busybox. Also the kernel seems to
like the filesystem and can mount the filesystem. I have for checked
for similar questions for this error, so I tried replacing /sbin/init
with a hello world program, but the result is exactly the same. It seems
neither hello-world or /sbin/init got executed.
At this point, I don't know how to debug this issue. Any suggestion on
how to debug this issue will be greatly appreciated.
Andrew
next prev parent reply other threads:[~2009-11-11 0:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 23:23 2.6.31 kernel for mips compile failure - war.h:12:17: error: war.h: No such file or directory myuboot
2009-10-16 23:41 ` myuboot
2009-10-16 23:50 ` David Daney
2009-10-19 23:49 ` myuboot
2009-10-19 23:56 ` serial port 8250 messed up after coverting from little endian to big endian on kernel 2.6.31 myuboot
2009-10-20 6:17 ` Florian Fainelli
2009-10-20 15:52 ` myuboot
2009-10-27 20:40 ` myuboot
2009-10-28 8:35 ` Shmulik Ladkani
2009-10-28 11:04 ` Sergei Shtylyov
2009-10-28 19:36 ` myuboot
2009-10-29 8:26 ` Shmulik Ladkani
2009-11-02 23:54 ` myuboot
2009-12-04 1:52 ` PIR OFFSET for AR7 myuboot
2009-12-04 16:03 ` Thomas Bogendoerfer
2009-12-04 17:30 ` myuboot
2009-11-11 0:22 ` myuboot [this message]
2009-11-11 7:45 ` Kernel panic - not syncing: Attempted to kill init! Gaye Abdoulaye Walsimou
2009-11-11 15:48 ` myuboot
2009-11-17 0:21 ` problem bring up initramfs and busybox myuboot
2009-11-17 9:33 ` Ralf Baechle
2009-11-17 17:39 ` myuboot
2009-11-17 17:48 ` Florian Fainelli
2009-11-17 21:09 ` myuboot
2010-01-19 19:51 ` loadable kernel module link failure - endianness incompatible with that of the selected emulation myuboot
2010-01-19 23:47 ` David Daney
2010-01-20 16:10 ` myuboot
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=1257898975.30125.1344591929@webmail.messagingengine.com \
--to=myuboot@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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