lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <366f00c80906180218p539f9df9md30f629787fabeb2@mail.gmail.com>
Date:	Thu, 18 Jun 2009 14:48:10 +0530
From:	Sudeep K N <sudeepholla.maillist@...il.com>
To:	linux-arm-kernel@...ts.arm.linux.org.uk
Cc:	drzeus-mmc@...eus.cx, linux-kernel@...r.kernel.org
Subject: Rootfs in eMMC: Kernel panic ...Attempted to kill init!

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ