2008-09-18 14:35:28 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Daniel Hartman (UNITED STATES)

Message: 62397

Hi all,

I'm a new to the Blackfin platform. I've got an ADSP-BF537 STAMP, and I've been following the Blackfin on-line documentation for compiling and downloading an image to the target:

http://docs.blackfin.uclinux.org/doku.php?id=basic_compilation

http://docs.blackfin.uclinux.org/doku.php?id=downloading_to_the_target

Using the default configuration settings, I get a kernel panic message when I use the "linux" image under the "linux-2.6.x" directory. However, if I use "vmlinux", everything boots fine. I've notice that "linux" is substantially smaller than "vmlinux", 2038590 vs. 9055038.

Although I am happy that it is finally booting, I'm concerned that I am doing something wrong since it doesn't agree with the documentation (to be read: I'm in the "weeds" with the simple stuff). I'm using the most recent release: uClinux-dist-2008R1.5-RC3.tar.bz2.

I have two questions: (1) What is the difference between "linux" and "vmlinux" and (2) why might I be getting a kernel panic while following the these simple documentation steps? I've attached the output for the kernel panic below.

Many thanks for your help.

Dan

autoboot in 5 seconds: press space to stop

bf537> tftp 0x1000000 linux

Using BF537 ETHERNET device

TFTP from server 192.168.45.192; our IP address is 192.168.45.143

Filename 'linux'.

Load address: 0x1000000

Loading: #################################################################

#################################################################

#########

done

Bytes transferred = 2038590 (1f1b3e hex)

bf537> bootelf 0x1000000

Loading .text @ 0x00001000 (1019792 bytes)

Loading .rodata @ 0x000fa000 (231416 bytes)

Loading __ksymtab @ 0x001327f8 (14336 bytes)

Loading __ksymtab_gpl @ 0x00135ff8 (4016 bytes)

Loading __ksymtab_strings @ 0x00136fa8 (43912 bytes)

Loading __param @ 0x00141b30 (300 bytes)

Loading .data @ 0x00142000 (65536 bytes)

Loading .init.text @ 0x00152000 (94212 bytes)

Loading .init.data @ 0x00169004 (3320 bytes)

Loading .init.setup @ 0x00169cfc (592 bytes)

Loading .initcall.init @ 0x00169f4c (432 bytes)

Loading .con_initcall.init @ 0x0016a0fc (4 bytes)

Loading .init.ramfs @ 0x0016a100 (134 bytes)

Loading .text_l1 @ 0xffa00000 (8232 bytes)

sh_addr: FFA00000, p_paddr: 0016A186

Loading from: 0116B000 to 0016A186, size: 8232

Loading .data_l1 @ 0xff800000 (192 bytes)

sh_addr: FF800000, p_paddr: 0016C1AE

Loading from: 0116E000 to 0016C1AE, size: 192

Clearing .bss @ 0x0016d000 (65616 bytes)

## Starting application at 0x00152000 ...

Linux version 2.6.22.19-ADI-2008R1.5-svn (hartman@HP-PAVILION) (gcc version 4.1.2 (ADI svn)) #4 Thu Sep 18 10:16:17 MDT 2008

Hardware Trace Active and Enabled

Warning: limiting memory to 56MB due to hardware anomaly 05000263

Compiled for ADSP-BF537 Rev 0.2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 100 MHz System Clock

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

text = 0x00001000-0x000f9f90

rodata = 0x000fa000-0x00141c5c

data = 0x00142000-0x00152000

stack = 0x00142000-0x00144000

init = 0x00152000-0x0016d000

bss = 0x0016d000-0x0017d050

available = 0x0017d050-0x037ff000

DMA Zone = 0x03f00000-0x04000000

NOMPU: setting up cplb tables for global access

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists. Total pages: 14224

Kernel command line: root=/dev/mtdblock0 rw

Configuring Blackfin Priority Driven Interrupts

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

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

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

Memory available: 55236k/65536k RAM, (108k init code, 995k kernel code, 417k data, 1024k dma, 7756k reserved)

Blackfin Scratchpad data SRAM: 4 KB

Blackfin Data A SRAM: 16 KB (15 KB free)

Blackfin Data B SRAM: 16 KB (16 KB free)

Blackfin Instruction SRAM: 48 KB (39 KB free)

Security Framework v1.0.0 initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

Generic PHY: Registered new driver

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

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

ISA-BlackFin-CAN CAN Driver 3.4.6_AD_BLACKFIN (c) Sep 18 2008

BlackFin port by H.J. Oertel (oe@port.de)

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

SMSC LAN83C185: Registered new driver

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=19)@sclk=100MHz)

bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@7

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 1970-01-01 01:57:00 (7020)

List of all partitions:

No filesystem could mount root, tried:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

QuoteReplyEditDelete

2008-09-18 15:11:38 Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Mike Frysinger (UNITED STATES)

Message: 62401

the documentation explains things:

http://docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:images

QuoteReplyEditDelete

2008-09-19 23:05:10 Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Daniel Hartman (UNITED STATES)

Message: 62457

Perfect. Thank you Mike. Dan

Partner Forums

Partner Libraries

2008-09-18 14:35:28 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)