Kernel panic - not syncing: Attempted to kill init!

Ranganath s

unread,

Jun 27, 2010, 2:54:26 AM6/27/10

to android-porting

Hi,

I got it my previous kernel panic problem solved. Now i am able to mount till rootfs but after that i am again running into "Kernel panic - not syncing: Attempted to kill init!"

The boot log is as follows:-

U-Boot 1.3.2-mini2440 (Oct 6 2009 - 12:51:09)

I2C: ready

DRAM: 64 MB

Flash: 2 MB

NAND: 128 MiB

Found Environment offset in OOB..

USB: S3C2410 USB Deviced

In: serial

Out: serial

Err: serial

MAC: 08:00:2f:00:00:06

Hit any key to stop autoboot: 0

trying to detect SD Card...

Manufacturer: 0x1b, OEM "SM"

Product name: "SD ", revision 1.0

Serial number: 3927984417

Manufacturing date: 2/2010

CRC: 0x4e, b0 = 1

READ_BL_LEN=15, C_SIZE_MULT=7, C_SIZE=3453

size = 2329935872

2060420 bytes read

## Booting kernel from Legacy Image at 31000000 ...

Image Name:

Created: 2010-03-26 5:54:15 UTC

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 2060356 Bytes = 2 MB

Load Address: 30008000

Entry Point: 30008000

Verifying Checksum ... OK

Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux..................................................................................................................................... done, booting the kernel.

Linux version 2.6.27 (root@tom) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #1 PREEMPT Mon Aug 24 17:01:35 CST 2009

CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177

Machine: FriendlyARM Mini2440 development board

Memory policy: ECC disabled, Data cache writeback

CPU S3C2440A (id 0x32440001)

MM: CPU does not support supersection mapping for 0x55000000000 at 0xf0d00000

S3C244X: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz

CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on

CPU0: D VIVT write-back cache

CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets

CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256

Kernel command line: console=ttySAC0,115200 root=/dev/mmcblk0p3 rootfstype=ext3 mini2440=1tb rootdelay=3 init=/linuxrc

irq: clearing pending status 02000000

irq: clearing subpending status 00000002

PID hash table entries: 256 (order: 8, 1024 bytes)

timer tcon=00500000, tcnt a4ca, tcfg 00000200,00000000, usec 00001e57

Console: colour dummy device 80x30

console [ttySAC0] enabled

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory: 64MB = 64MB total

Memory: 60188KB available (3896K code, 636K data, 116K init)

SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Calibrating delay loop... 201.93 BogoMIPS (lpj=504832)

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

net_namespace: 288 bytes

NET: Registered protocol family 16

S3C2440: Initialising architecture

S3C2440: IRQ Support

DMA channel 0 at c4800000, irq 33

DMA channel 1 at c4800040, irq 34

DMA channel 2 at c4800080, irq 35

DMA channel 3 at c48000c0, irq 36

S3C244X: Clock Support, DVS off

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

NET: Registered protocol family 1

NetWinder Floating Point Emulator V0.97 (double precision)

ashmem: initialized

NTFS driver 2.1.29 [Flags: R/W DEBUG].

yaffs Aug 24 2009 16:57:57 Installing.

msgmni has been set to 117

io scheduler noop registered (default)

Console: switching to colour frame buffer device 30x20

fb0: s3c2410fb frame buffer device

adc initialized

input: buttons as /class/input/input0

buttons initialized

leds initialized

s3c2440-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440

s3c2440-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440

s3c2440-uart.2: s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440

brd: module loaded

loop: module loaded

nbd: registered device at major 43

logger: created 64K log 'log_main'

logger: created 256K log 'log_events'

logger: created 64K log 'log_radio'

dm9000 Ethernet Driver, V1.31

Now use the default MAC address: 08:90:90:90:90:90

eth0: dm9000e at c4804000,c4806004 IRQ 51 MAC: c3908934 (friendly-arm)

usbcore: registered new interface driver zd1211rw

usbcore: registered new interface driver zd1201

Linux video capture interface: v2.00

ovcamchip: v2.27 for Linux 2.6 : OV camera chip I2C driver

usbcore: registered new interface driver ov511

ov511: v1.64 for Linux 2.5 : ov511 USB Camera Driver

Driver 'sd' needs updating - please use bus_type methods

s3c2440-nand s3c2440-nand: Tacls=3, 29ns Twrph0=7 69ns, Twrph1=3 29ns

NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)

NAND_ECC_NONE selected by board driver. This is not recommended !!

Scanning device for bad blocks

Creating 4 MTD partitions on "NAND 128MiB 3,3V 8-bit":

0x00000000-0x00060000 : "supervivi"

0x00060000-0x00260000 : "Kernel"

0x00260000-0x40260000 : "root"

mtd: partition "root" extends beyond the end of device "NAND 128MiB 3,3V 8-bit" -- size truncated to 0x7da0000

0x00000000-0x40000000 : "nand"

mtd: partition "nand" extends beyond the end of device "NAND 128MiB 3,3V 8-bit" -- size truncated to 0x8000000

s3c2410-ohci s3c2410-ohci: S3C24XX OHCI

s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1

s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 2 ports detected

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

s3c2440-usbgadget s3c2440-usbgadget: S3C2440: increasing FIFO to 128 bytes

mice: PS/2 mouse device common for all mice

usbcore: registered new interface driver appletouch

input: s3c2410 TouchScreen as /class/input/input1

s3c2410 TouchScreen successfully loaded

s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling

s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0

i2c /dev entries driver

s3c2440-i2c s3c2440-i2c: slave address 0x10

s3c2440-i2c s3c2440-i2c: bus frequency set to 98 KHz

s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter

mapped channel 0 to 0

s3c2440-sdi s3c2440-sdi: powered down.

s3c2440-sdi s3c2440-sdi: initialisation done.

s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: 0kHz).

s3c2440-sdi s3c2440-sdi: running at 198kHz (requested: 197kHz).

usbcore: registered new interface driver hiddev

s3c2440-sdi s3c2440-sdi: running at 198kHz (requested: 197kHz).

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver

UDA1341 audio driver initialized

failed to get memory region resouce

s3c2410-iis: probe of s3c2410-iis.0 failed with error -2

TCP cubic registered

NET: Registered protocol family 17

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

s3c2440-sdi s3c2440-sdi: running at 198kHz (requested: 197kHz).

s3c2440-sdi s3c2440-sdi: running at 16875kHz (requested: 25000kHz).

mmc0: new SD card at address b368

mmcblk0: mmc0:b368 SD 1981440KiB

mmcblk0: p1 p2 p3

s3c2410-rtc s3c2410-rtc: hctosys: invalid date/time

Waiting 3sec before mounting root device...

kjournald starting. Commit interval 5 seconds

EXT3 FS on mmcblk0p3, internal journal

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem).

Freeing init memory: 116K

Warning: unable to open an initial console.

ts_control_open!

ts_control_release!

Kernel panic - not syncing: Attempted to kill init!

Regards

Ranganath.S

Ashwin Bihari

unread,

Jun 27, 2010, 8:34:57 AM6/27/10

to ranga...@gmail.com, android-porting

You want "init=/init" in your bootargs..and you can use "rootwait"
instead of "rootdelay=3"..

Regards
-- Ashwin

> --
> unsubscribe: android-porti...@googlegroups.com
> website: http://groups.google.com/group/android-porting
>

Subramani Venkatesh

unread,

Jun 27, 2010, 11:11:23 AM6/27/10

to ranga...@gmail.com, android-porting

Hi Ranganath,
There are some changes required when yuou try SD/MMC card as file system

1. copy entire out/target/product/<board>/root to your sd card
2. copy entire out/target/product/<board>/system your sd card
<sdcard>/system directory created by root
3. Modify your init.rc file to avoid mounting again system by yaffs2 type.

Regads,
Subbu

On Sun, Jun 27, 2010 at 2:54 AM, Ranganath s <ranga...@gmail.com> wrote:

Brad Davis

unread,

Jun 28, 2010, 4:27:29 PM6/28/10

to android-porting

On Jun 27, 12:54 am, Ranganath s <rangana...@gmail.com> wrote:
>
> I2C: ready
> DRAM: 64 MB
> Flash: 2 MB
> NAND: 128 MiB

I have 2.1 running on an Atmel AT91SAM9263-EK board. Running is the
operative word here. 64MB Dram is not enough to run the standard
Android image. I removed Bluetooth, Camera, Mms, Phone, and
TelephonyProvider from the image before installing and removed the
services bootsound, bootanim, dbus, bluetoothd, hfag, hsag, opush, and
pbap from the init.rc.

The problem is that the system runs out of real memory when trying to
run applications that are required to be running (the consumer system
reboots if things like the phone code crash, just what you would
expect on a consumer phone). Init detects these startup failures and
dies. You can actually watch it happening on a slow processor with a
debug shell. After the shell starts (while Dalvik is starting the
Java programs) start vmstat and logcat in the background. The free
real memory goes to 0 as the different programs start up. Then the
kernel panics.

My current stripped system has run for days at a time without crashing
before I reboot it.

You will need at least 128mb ram
Brad

Retti

unread,

Jul 12, 2010, 4:49:30 AM7/12/10

to android-porting

> 3. Modify your init.rc file to avoid mounting again system by yaffs2 type.

Can you tell me how to do this!?
I have copied these files to SD, but there's always the Warning: