Hi, On Feb 20, 2008 8:39 AM, tomy <tomy@xxxxxxxxxxxx> wrote: > Hello, > I am working on booting Linux on an embedded platform > (AT91SAM9260). In this I am using a JFFS2 flash file system . I have > created a Jffs2 file system using mkfs.jffs2. I have written this file > system on a particular sector in the NAND flash. I have made three > partitions in Linux , and the third partition is starting from where i > wrote the JFFS2 file system. I have given the kernel parameter as > *mem=64M console=ttyS0,115200 noinitrd root=/dev/mtdblock3 rw > rootfstype=jffs2. *During Linux kernel boot up, it is creating 3 > partitions ,but at the end it is giving a kernel panic. The boot process > is given below > > Starting kernel ... > Uncompressing > Linux............................................................. > .................. done, booting the kernel. > Linux version 2.6.20.11 (root@KALKI-SYS-145) (gcc version 4.1.0 20060304 > (TimeSy > s 4.1.0-3)) #59 Tue Feb 19 19:32:19 IST 2008 > CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 > Machine: Atmel AT91SAM9260-EK > Memory policy: ECC disabled, Data cache writeback > Clocks: CPU 198 MHz, master 99 MHz, main 18.432 MHz > CPU0: D VIVT write-back cache > CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets > CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets > Built 1 zonelists. Total pages: 16256 > Kernel command line: mem=64M console=ttyS0,115200 noinitrd > root=/dev/mtdblock2 r > w rootfstype=jffs2 > AT91: 96 gpio irqs in 3 banks > PID hash table entries: 256 (order: 8, 1024 bytes) > Console: colour dummy device 80x30 > 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: 62372KB available (2200K code, 188K data, 100K init) > Mount-cache hash table entries: 512 > CPU: Testing write buffer coherency: ok > NET: Registered protocol family 16 > Generic PHY: Registered new driver > 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: 1, 8192 bytes) > TCP bind hash table entries: 1024 (order: 0, 4096 bytes) > TCP: Hash tables configured (established 2048 bind 1024) > TCP reno registered > NetWinder Floating Point Emulator V0.97 (double precision) > audit: initializing netlink socket (disabled) > audit(0.520:1): initialized > JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc. > fuse init (API version 7.8) > io scheduler noop registered > io scheduler anticipatory registered (default) > atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL > atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL > atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL > atmel_usart.3: ttyS3 at MMIO 0xfffb8000 (irq = 8) is a ATMEL_SERIAL > atmel_usart.4: ttyS4 at MMIO 0xfffd0000 (irq = 23) is a ATMEL_SERIAL > atmel_usart.5: ttyS5 at MMIO 0xfffd4000 (irq = 24) is a ATMEL_SERIAL > atmel_usart.6: ttyS6 at MMIO 0xfffd8000 (irq = 25) is a ATMEL_SERIAL > RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize > Davicom DM9161E: Registered new driver > Davicom DM9131: Registered new driver > LXT970: Registered new driver > LXT971: Registered new driver > macb macb: detected PHY at address 0 (ID 0181:b8a0) > eth0: Atmel MACB at 0xfffc4000 irq 21 (00:00:00:00:00:00) > NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ > INFTL: inftlcore.c $Revision: 1.19 $, inftlmount.c $Revision: 1.18 $ > SSFDC read-only Flash Translation layer > impA7:probing 0x00800000 at 0x00000000 > impA7:probing 0x00800000 at 0x10000000 > Generic platform RAM MTD, (c) 2004 Simtec Electronics > slram: not enough parameters. > block2mtd: version $Revision: 1.30 $ > NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB > 3,3V 8-bi > t) > Creating 3 MTD partitions on "NAND 256MiB 3,3V 8-bit": > 0x00000000-0x00400000 : "Kernel" > 0x00400000-0x00800000 : "Ram File System" > 0x01000000-0x03000000 : "Flash File System" > usbmon: debugfs is not available > at91_ohci at91_ohci: AT91 OHCI > at91_ohci at91_ohci: new USB bus registered, assigned bus number 1 > at91_ohci at91_ohci: irq 20, io mem 0x00500000 > 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. > udc: at91_udc version 3 May 2006 > i2c /dev entries driver > AT91 MMC: 4 wire bus mode not supported by this driver - using 1 wire > TCP cubic registered > NET: Registered protocol family 1 > NET: Registered protocol family 17 > VFS: Mounted root (jffs2 filesystem).name-/dev/root fs-jffs2 flags32768 > Freeing init memory: 100K > Warning: unable to open an initial console. > Kernel panic - not syncing: No init found. Try passing init= option to > kernel. This explains what is wrong: the kernel cannot find a suitable init process. In the function init() in main.c of the kernel, there are a number of calls to run_init_process(), which try to find a suitable init. If there is none found, you get the error message. This code tries the following locations: * an init process you mentioned on the command line via init= * /sbin/init * /etc/init * /bin/init * /bin/sh Please show us the contents of your file system. The easiest thing for you now is to make sure you have a /bin/sh in your filesystem. You should also make sure you have /dev/console in your filesystem, to avoid the other error you got: > Warning: unable to open an initial console. All this is explained in the book: "Embedded Linux Primer" by Christopher Hallinan (Prentice Hall), which I found very interesting. Good luck, Thomas -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
