Fails to boot after IO scheduler noop registered
 

Hi,

I am new to linux.The board which i am using is a embedded device based on MCF5474 processor. It has 128MB SDRAM memory. The board fails to boot after the print "IO scheduler noop register" and format error is reported. Below are prints collected from the debug port. Please help in understanding this error and provide some light in the troubleshooting.Thanks.
--------------------
tag: 6 5 0 33554432
mem chunk 0, 33554432 1
tag: 6 7 1936028704 1668030573
starting up linux rev 0.2: startmem 0xc0190000, size 27MB
config: CONFIG_BLK_DEV_INITRD
Built 1 zonelists
Kernel command line: set cl mac0=00:00:AA:1F:DF:9F noinitrd rootfstype=jffs2 root=/dev/mtdblock/0 rw
PID hash table entries: 128 (order: 7, 2048 bytes)
No real time clock, nothing to read, returning 1970.
Dentry cache hash table entries: 4096 (order: 1, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 0, 8192 bytes)
Memory: 27832k/29696k available (1312k kernel code, 376k data, 80k init)
Mount-cache hash table entries: 1024 (order: 0, 8192 bytes)
NET: Registered protocol family 16
Initialize Multi-channel DMA API Alpha v0.3 (2004-04-26)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: devfs_debug: 0x0
devfs: boot_options: 0x1
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
mcfrs_init driver init
ColdFire internal UART serial driver version 1.00
ttyS0 at 0xe0008600 (irq = 99) is a builtin ColdFire UART
ttyS1 at 0xe0008700 (irq = 98) is a builtin ColdFire UART
io scheduler noop registered
*** FORMAT ERROR *** FORMAT=4
Current process id is 1
BAD KERNEL TRAP: 00000000
Modules linked in:
PC: [<c0002438>]
SR: 2014 SP: c0191f58 a2: c1cc1bc0
d0: 00000000 d1: ffff8d62 d2: 00000005 d3: 0000003c
d4: 00000000 d5: 00000004 a0: 00005319 a1: c1cff7a0
Process swapper (pid: 1, stackpage=c1cc3bc0)
Stack from c0191f58:
ffff8d62 00000005 0000003c 00000000 00000004 00005319 c1cff7a0 c1cc1bc0
00000000 ffffffff 00000000 00005319 00000000 40382014 c0002438 0c0a2004
c011f7e2 00000001 00000005 00000000 00008197 00000000 00000000 c000aa88
c0188d90 c1cc1bc0 00000030 c018dffc c018337a c013559a 0000003c 00000000
00000000 00000000 00000000 00000001 c00020e2 00000000 c000aa88 c000aa88
c00027dc 00000000
--------------------------------------------------

From what I can see, the initrd image has loaded and the init script has been run - so the problem actually comes after the kernel has completed the boot phase. You'll have to look at your init script and see for yourself what happens after setting up ttyS* and whether the next part or the ttyS* setup causes the problem. See if you can find out what that "format error" thing is all about.

Hi,

Could you please tell where to find the init script in the kernal source code. I am from Hardware background and have less knowledge about linux. One of the software engineers whom I consulted on this says the kernel which is the running in the board does not have initrd.
Help me in understanding about initird and init script.

Thanks.

regards,
Mithra