We have ARM926EJ-S board and trying to boot Linux on the same. We are using 2.6.19 with cramfs. But we are failing with kernel panic error. Please see attached log of the same. Please let us know what could be the issue. run u-boot_versatilepb U-Boot 1.2.0-gb3261521-dirty (Feb 25 2007 - 02:59:39) DRAM: 0 kB Flash: 64 MB In: serial Out: serial Err: serial Hit any key to stop autoboot: 2 1 0 ## Booting image at 00007fc0 ... Image Name: Linux-2.6.19-1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1186944 Bytes = 1.1 MB Load Address: 00008000 Entry Point: 00008000 OK Starting kernel ... Uncompressing Linux............................................................................... done, booting the kernel. Linux version 2.6.19-1 (root@bd-0155.patni.com) (gcc version 4.1.1 (CodeSourcery ARM Sourcery G++ 2006q3-26)) #2 Thu Mar 8 15:03:10 IST 2007 CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177 Machine: ARM-Versatile PB Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/mtdblock0 mtdparts=armflash.0:19232k@0x2C0000(cramfs) console=ttyAMA0 mem=128M PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 127360KB available (2012K code, 438K data, 88K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 4096 bind 2048) TCP reno registered JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc. io scheduler noop registered (default) CLCD: Versatile hardware, VGA display Clock CLCDCLK: setting VCO reg params: S=1 R=99 V=98 Console: switching to colour frame buffer device 80x30 Serial: AMBA PL011 UART driver dev:f1: ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a AMBA/PL011 dev:f2: ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a AMBA/PL011 dev:f3: ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a AMBA/PL011 fpga:09: ttyAMA3 at MMIO 0x10009000 (irq = 38) is a AMBA/PL011 smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org> eth0: SMC91C11xFD (rev 1) at c8866000 IRQ 25 [nowait] eth0: Ethernet addr: 00:02:f7:00:19:63 armflash.0: Found 2 x16 devices at 0x0 in 32-bit bank Intel/Sharp Extended Query Table at 0x0031 Using buffer write method cfi_cmdset_0001: Erase suspend on write enabled 1 cmdlinepart partitions found on MTD device armflash.0 Creating 1 MTD partitions on "armflash.0": 0x002c0000-0x01588000 : "cramfs" mtd: partition "cramfs" doesn't end on an erase block -- force read-only mice: PS/2 mouse device common for all mice Advanced Linux Sound Architecture Driver Version 1.0.13 (Tue Nov 28 14:07:24 2006 UTC). aaci-pl041 fpga:04: ARM AC'97 Interface at 0x0000000010004000, irq 24, fifo 512 atkbd.c: keyboard reset failed on fpga:06 ALSA device list: #0: ARM AC'97 Interface at 0x0000000010004000, irq 24 TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 1 input: ImPS/2 Generic Wheel Mouse as /class/input/input0 No filesystem could mount root, tried: cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,0) Reproducible: Always Expected Results: Normal boot up
This is NOT a Gentoo Bugzilla product bug; read the descriptions.
i also got this kernel error!! Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) could anyone please tell what kernel option could be causing this error?
bugzilla is not a support forum if you're having troubling booting your board, go ask on the forums
