mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudeep K N <sudeepholla.maillist@gmail.com>
To: linux-arm-kernel@lists.arm.linux.org.uk
Cc: drzeus-mmc@drzeus.cx, linux-kernel@vger.kernel.org
Subject: Rootfs in eMMC: Kernel panic ...Attempted to kill init!
Date: Thu, 18 Jun 2009 14:48:10 +0530	[thread overview]
Message-ID: <366f00c80906180218p539f9df9md30f629787fabeb2@mail.gmail.com> (raw)

Hi,

I am trying to boot linux on SMP system with root file system(ext2) on eMMC.
The eMMC is partitioned in 3 parts and I am trying to use 2nd
partition of 128M to keep
the rootfs.
The command line used is:
Kernel command line: cachepolicy=writealloc noinitrd
root=/dev/mmcblk0p2 rootfstype=ext2 rootdelay=1 init=/bin/sh rw
console=ttyAMA2,115200n8 mem=128M

After mounting the rootfs in eMMC, it panics.
Panic log as below.  When I traced, I observed it fails while its
execution "run_init_process"
I have tried with different init process,i.e. init=/linuxrc,
init=/bin/busybox, init=/sbin/init
Even I tried initramfs and the switch_root/pivot_root to rootfs on
eMMC partition.
In all the cases, I got the same panic.
Can anybody help me in understanding the exact reason for this panic?


Panic Log:
DRIVER MMC: probe
Waiting 1sec before mounting root device...
mmc0: new MMC card at address 0001
mmcblk0: mmc0:0001 M8G4DD 8028160KiB
 mmcblk0: p1 p2 p3
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 108K
Kernel panic - not syncing: Attempted to kill init!
CPU0: stopping
[<c0028950>] (dump_stack+0x0/0x14) from [<c0023384>] (do_IPI+0xd4/0x140)
[<c00232b0>] (do_IPI+0x0/0x140) from [<c0023a88>] (__irq_svc+0x48/0xdc)
Exception stack(0xc01fdf40 to 0xc01fdf88)
df40: 00000000 c01fc000 c01fdf88 00000000 c0025754 c01fc000 00322000 00000004
df60: c001d000 410fc090 c001dfc0 c01fdf94 c01fdf98 c01fdf88 c0025794 c0025798
df80: 60000013 ffffffff
 r9:c01fc000 r8:00000001 r7:00000002 r6:00000401 r5:f0410100
r4:ffffffff
[<c0025754>] (default_idle+0x0/0x4c) from [<c0025634>] (cpu_idle+0x64/0x94)
[<c00255d0>] (cpu_idle+0x0/0x94) from [<c018666c>] (rest_init+0x6c/0x80)
 r5:c02188dc r4:c0225358
[<c0186600>] (rest_init+0x0/0x80) from [<c0008bf4>] (start_kernel+0x2f0/0x358)
[<c0008904>] (start_kernel+0x0/0x358) from [<0000807c>] (0x807c)


--
Regards,
Sudeep

             reply	other threads:[~2009-06-18  9:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  9:18 Sudeep K N [this message]
2009-06-19 13:44 ` Russell King - ARM Linux
2009-06-22 14:13   ` Sudeep K N
2009-06-22 14:26     ` Catalin Marinas
2009-06-22 14:32       ` Catalin Marinas
2009-06-22 15:43     ` Russell King - ARM Linux
2009-06-22 15:50       ` Catalin Marinas
2009-06-22 15:56         ` Russell King - ARM Linux
2009-06-22 16:13           ` Catalin Marinas
2009-06-22 16:46             ` Russell King - ARM Linux
2009-06-22 21:37               ` Catalin Marinas
2009-06-23  9:23               ` Linus Walleij
2009-06-23 14:34               ` Catalin Marinas
2009-07-13 15:44                 ` Dirk Behme
2009-07-13 15:48                   ` Russell King - ARM Linux
2009-07-16 10:39                   ` Catalin Marinas
2009-06-23  5:58             ` Sudeep K N

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=366f00c80906180218p539f9df9md30f629787fabeb2@mail.gmail.com \
    --to=sudeepholla.maillist@gmail.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®