Kernel panic: Attempted to kill init!

Katey Yu katey.Yu at ositech.com
Thu Jul 20 14:18:07 UTC 2006


Hello,

I configured the busybox to include init program and copied examples/inittab into directory /etc. The file system is working.

Thanks,

Katey

-----Original Message-----
From: Brenda J. Butler [mailto:bjb at magma.ca] 
Sent: Wednesday, July 19, 2006 12:19 PM
To: Katey Yu
Subject: Re: Kernel panic: Attempted to kill init!

Katey,

It looks like the kernel has booted, and has mounted the cramfs rootfs
successfully.  The next step should be to run the init program,
and there is no evidence that it is running.  It looks like a
busybox program is trying to run and failing.

It also seems that busybox is not configured to include the "init"
applet.

So, try rebuilding busybox including the "init" program, and then
rebuild your cramfs rootfs with the new busybox, and try again.

cheerio,
bjb


On Wed, Jul 19, 2006 at 11:37:18AM -0400, Katey Yu wrote:
> 
> 
> Hello,
> 
> Could somebody tell me what's wrong?
> 
> Katey yu
> 
> 
> Now booting the kernel
> Linux version 2.4.24-arc2 (root at localhost.localdomain) (gcc version 2.95.3 20010315 (release)) #19 Mon Jul 17 13:16:22 EDT 2006
> Processor: ARM/CNXT Arm940sid(wb) revision 2
> Architecture: CNXT CX821XX
> On node 0 totalpages: 1920
> zone(0): 0 pages.
> zone(1): 1920 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/mtdblock2 init=/linuxrc
> Calibrating delay loop... 83.76 BogoMIPS
> MemoryOsitech: 7MB = 7MB total
> MemoryOsitech: 6180KB available (1099K code, 255K data, 48K init)
> Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
> Inode cache hash table entries: 512 (order: 0, 4096 bytes)
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Conexant General Purpose timers initialized
> Conexant hardware timer 2 enabled
> Conexant Flash Driver version: 001
> Initializing Flash Segment 1
> Initializing Flash Segment 2
> Initializing Flash Segment 3
> Initializing Flash Segment 4
> Initializing Flash Segment 5
> Initializing Flash Segment 6
> Initializing Flash Segment 7
> Initializing Flash Segment 8
> Initializing Flash Segment 9
> Initializing Flash Segment 10
> Initializing Flash Segment 11
> Initializing Flash Segment 12
> Initializing Flash Segment 13
> Initializing Flash Segment 14
> Initializing Flash Segment 15
> Initializing Flash Segment 16
> Starting kswapd
> cnxtserialirq 24
> cnxtserialGPIOINT_UART1 25
> ttyS0 at 0x002c0000 (irq = 24) is a 16c550 UART
> info = 0094b720
> ACTION_TEC_DEBUG : rs_ACTION_TEC_init
> ttyS2 at 0x002c8000 (irq = 5) is a 16c550 UART
> info = 0094c9bc
> emac_probe: Rushmore device detected
> PHY #2 = 15f441
> emac_probe: eth0 found.
> Tx DMA Ring f824b0 
> Rx DMA Ring fa0b20 
> EMAC Network Driver Cnxt 2004/05/03 irq=19 00:30:cd:00:02:9c:
> emac_probe: Rushmore device detected
> PHY #2 = 15f441
> emac_probe: eth1 found.
> Tx DMA Ring fc00c0 
> Rx DMA Ring fde730 
> EMAC Network Driver Cnxt 2004/05/03 irq=20 00:30:cd:00:02:d1:
> emac_probe: Rushmore device detected
> emac_probe: Rushmore device detected
> emac_probe: Rushmore device detected
> emac_probe: Rushmore device detected
> emac_probe: Rushmore device detected
> emac_probe: Rushmore device detected
> emac_probe: Rushmore device detected
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Intel flash driver
> Search for id:(89 8891) interleave(1) type(2)
> Found: Intel 28F160B3B
>  Intel flash memory: Found 1 x16 devices at 0x0 in 16-bit mode
> Using word write method
> Creating 5 MTD partitions on " Intel flash memory":
> 0x00000000-0x00010000 : "bootloader"
> 0x00010000-0x000a0000 : "kernel"
> 0x000a0000-0x001f0000 : "filesystem"
> 0x001f0000-0x00200000 : "config"
> 0x00000000-0x00200000 : "complete flash"
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 512 bind 512)
> ip_conntrack version 2.1 (60 buckets, 480 max) - 320 bytes per conntrack
> ip_tables: (C) 2000-2002 Netfilter core team
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> VFS: Mounted root (cramfs filesystem) readonly.
> BusyBox v1.00-pre5 (2006.07.18-14:24+0000) multi-call binary
> 
> Usage: busybox [function] [arguments]...
>    or: [function] [arguments]...
> 
> 	BusyBox is a multi-call binary that combines many common Unix
> 	utilities into a single executable.  Most people will create a
> 	link to busybox for each function they wish to use, and BusyBox
> 	will act like whatever it was invoked as.
> 
> Currently defined functions:
> 	[, basename, busybox, cat, chgrp, chmod, chown, chroot, clear,
> 	cp, cut, date, dd, df, dirname, du, echo, env, false, free, gunzip,
> 	gzip, head, hostname, id, ifconfig, kill, killall, ln, login,
> 	ls, mkdir, mknod, mount, msh, mv, passwd, ping, ps, pwd, reboot,
> 	reset, rm, rmdir, route, sh, sleep, sort, sync, tail, tar, test,
> 	tftp, touch, true, tty, umount, uname, uniq, vi, whoami, yes,
> 	zcat
> 
> Kernel panic: Attempted to kill init!
> ÇÇ
> 
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
> 
---end quoted text---





More information about the busybox mailing list