•  

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block

Tags
Details
  • 5 Replies
  • 2 Subscribers
  • Postedover 2 years ago
Options
Home » Leopardboard » Leopardboard 355 » Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block

This question is not answered
Justin
Posted by
on 17 May 2011 7:49 AM

Hi there.

I'm having trouble getting started with my LeopardBoard DM355.
I get the following error once I have flashed the leopardboard:

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

I have attached what thought to be relevant.
Has anyone encountered this before? Any ideas of where I what went wrong?

*********************************************************************
            DM355 LEOPARD:
*********************************************************************
DM35x
 initialization passed!
Customized by RidgeRun
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000002.
   DONE
Jumping to entry point at 0x81080000.


U-Boot customized by RidgeRun
U-Boot 2009.11 (May 13 2011 - 19:59:55)

Cores: ARM 216 MHz
DDR:   171 MHz
I2C:   ready
DRAM:  128 MB
NAND:  256 MiB
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: Bad block at 0x000000020000
nand_read_bbt: Bad block at 0x000000040000
nand_read_bbt: Bad block at 0x000000060000
nand_read_bbt: Bad block at 0x000000080000
nand_read_bbt: Bad block at 0x0000000a0000
nand_read_bbt: Bad block at 0x0000000c0000
Net:   dm9000
Hit any key to stop autoboot:  0

Loading from nand0, offset 0xc0000
Skipping bad block 0x000c0000
   Image Name:   "RR Linux Kernel"
   Created:      2011-05-16  12:55:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3376616 Bytes =  3.2 MB
   Load Address: 80008000
   Entry Point:  80008000
Skipping bad block 0x000c0000
Automatic boot of image at addr 0x80700000 ...
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   "RR Linux Kernel"
   Created:      2011-05-16  12:55:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3376616 Bytes =  3.2 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.000000] Linux version 2.6.29-ridgerun-davinci1 (justin@ubuntu) (gcc version 4.2.4) #1 PREEMPT Fri May 13 19:31:29 SAST 2011
[    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: DaVinci DM355 leopard
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] DaVinci DM0355 variant 0x0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 29464
[    0.000000] Kernel command line: console=ttyS0,115200n8 video=davincifb:osd1=0x0x8 root=/dev/mtdblock3 rw mem=116M rootfstype=jffs2 mtdparts=davinci_nand.0:640k(UBOOT),128k(UBOOT_ENV),3840k(KERNEL),21888k(FS)
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[42949372.960000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[42949372.960000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[42949372.980000] Memory: 116MB = 116MB total
[42949372.980000] Memory: 114076KB available (3056K code, 208K data, 116K init)
[42949372.980000] Calibrating delay loop... 107.72 BogoMIPS (lpj=538624)
[42949373.210000] Mount-cache hash table entries: 512
[42949373.210000] CPU: Testing write buffer coherency: ok
[42949373.210000] net_namespace: 520 bytes
[42949373.220000] NET: Registered protocol family 16
[42949373.220000] MUX: initialized INT_EDMA_CC
[42949373.220000] MUX: initialized VIN_CINL_EN
[42949373.250000] DaVinci: 104 gpio irqs
[42949373.330000] bio: create slab <bio-0> at 0
[42949373.340000] vpss vpss: dm355_vpss vpss probed
[42949373.340000] vpss vpss: dm355_vpss vpss probe success
[42949373.340000] ch0 default output "COMPOSITE", mode "NTSC"
[42949373.340000] VPBE Encoder Initialized
[42949373.350000] SCSI subsystem initialized
[42949373.350000] usbcore: registered new interface driver usbfs
[42949373.350000] usbcore: registered new interface driver hub
[42949373.360000] usbcore: registered new device driver usb
[42949373.370000] Avnetlcd encoder initialized
[42949373.380000] musb_hdrc: version 6.0, pio, host, debug=0
[42949373.400000] musb_hdrc: USB Host mode controller at fec64000 using PIO, IRQ 12
[42949373.400000] musb_hdrc musb_hdrc: MUSB HDRC host driver
[42949373.400000] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[42949373.400000] usb usb1: configuration #1 chosen from 1 choice
[42949373.400000] hub 1-0:1.0: USB hub found
[42949373.400000] hub 1-0:1.0: 1 port detected
[42949373.410000] NET: Registered protocol family 2
[42949373.410000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[42949373.410000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[42949373.410000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[42949373.410000] TCP: Hash tables configured (established 4096 bind 4096)
[42949373.410000] TCP reno registered
[42949373.410000] NET: Registered protocol family 1
[42949373.420000] JFFS2 version 2.2. (NAND) (SUMMARY)  �© 2001-2006 Red Hat, Inc.
[42949373.430000] msgmni has been set to 223
[42949373.430000] io scheduler noop registered (default)
[42949373.440000] davincifb davincifb.0: dm_osd0_fb: 720x480x16@0,0 with framebuffer size 1350KB
[42949373.450000] davincifb davincifb.0: dm_vid0_fb: 0x0x16@0,0 with framebuffer size 675KB
[42949373.460000] davincifb davincifb.0: dm_osd1_fb: 0x0x8@0,0 with framebuffer size 1350KB
[42949373.470000] davincifb davincifb.0: dm_vid1_fb: 0x0x16@0,0 with framebuffer size 675KB
[42949373.480000] Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
[42949373.480000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[42949373.480000] console [ttyS0] enabled
[42949373.810000] brd: module loaded
[42949373.840000] loop: module loaded
[42949373.840000] dm9000 Ethernet Driver, V1.31
[42949373.970000] Unable to read MAC address: Generating random value ...
[42949373.970000] The random generated MAC address: 56:53:ba:ae:bf:c6 will be assigned to your device
[42949373.980000] eth0 (dm9000): not using net_device_ops yet
[42949373.990000] eth0: dm9000e at c785c000,c7860016 IRQ 73 MAC: 56:53:ba:ae:bf:c6 (chip)
[42949374.000000] Linux video capture interface: v2.00
[42949374.010000] vpfe-capture vpfe-capture: video device registered
[42949374.010000] vpfe-capture vpfe-capture: v4l2 int master registered
[42949374.020000] vpfe_capture: init successful
[42949374.030000] Trying to register davinci display video device.
[42949374.030000] layer=c65f7200,layer->video_dev=c65f7364
[42949374.040000] Trying to register davinci display video device.
[42949374.050000] layer=c65f7000,layer->video_dev=c65f7164
[42949374.050000] davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
[42949374.060000] vpfe-capture vpfe-capture: register slave mt9v113
[42949374.070000] mt9v113 1-003c: chip id mismatch read 0x0, expecting 0x2280
[42949374.070000] mt9v113 1-003c: Unable to detect decoder
[42949374.080000] mt9v113 1-003c: Registered to v4l2 master vpfe-capture!!
[42949374.090000] Driver 'sd' needs updating - please use bus_type methods
[42949374.100000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[42949374.110000] 2 NAND chips detected
[42949374.110000] Scanning device for bad blocks
[42949374.120000] Bad eraseblock 3 at 0x000000060000
[42949374.120000] Bad eraseblock 4 at 0x000000080000
[42949374.130000] Bad eraseblock 5 at 0x0000000a0000
[42949374.130000] Bad eraseblock 6 at 0x0000000c0000
[42949374.220000] Bad eraseblock 2051 at 0x000010060000
[42949374.220000] Bad eraseblock 2052 at 0x000010080000
[42949374.230000] Bad eraseblock 2053 at 0x0000100a0000
[42949374.230000] Bad eraseblock 2054 at 0x0000100c0000
[42949374.320000] 4 cmdlinepart partitions found on MTD device davinci_nand.0
[42949374.330000] Creating 4 MTD partitions on "davinci_nand.0":
[42949374.340000] 0x000000000000-0x0000000a0000 : "UBOOT"
[42949374.350000] 0x0000000a0000-0x0000000c0000 : "UBOOT_ENV"
[42949374.360000] 0x0000000c0000-0x000000480000 : "KERNEL"
[42949374.360000] 0x000000480000-0x0000019e0000 : "FS"
[42949374.370000] davinci_nand davinci_nand.0: controller rev. 2.3
[42949374.380000] Initializing USB Mass Storage driver...
[42949374.390000] usbcore: registered new interface driver usb-storage
[42949374.390000] USB Mass Storage support registered.
[42949374.400000] i2c /dev entries driver
[42949374.410000] watchdog watchdog: heartbeat 60 sec
[42949374.420000] davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
[42949374.430000] davinci_mmc davinci_mmc.1: Using DMA, 4-bit mode
[42949374.450000] Advanced Linux Sound Architecture Driver Version 1.0.18a.
[42949374.460000] No device for DAI tlv320aic3x
[42949374.470000] No device for DAI davinci-i2s
[42949374.470000] AIC3X Audio Codec 0.2
[42949374.480000] asoc: tlv320aic3x <-> davinci-i2s mapping ok
[42949374.510000] ALSA device list:
[42949374.510000]   #0: Leopard Board (tlv320aic3x)
[42949374.520000] TCP cubic registered
[42949374.520000] NET: Registered protocol family 17
[42949374.530000] RPC: Registered udp transport module.
[42949374.530000] RPC: Registered tcp transport module.
[42949374.540000] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[42949387.490000] Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
[42949387.500000] empty_blocks 0, bad_blocks 0, c->nr_blocks 171
[42949387.500000] VFS: Cannot open root device "mtdblock3" or unknown-block(31,3)
[42949387.510000] Please append a correct "root=" boot option; here are the available partitions:
[42949387.520000] 1f00             640 mtdblock0 (driver?)
[42949387.520000] 1f01             128 mtdblock1 (driver?)
[42949387.530000] 1f02            3840 mtdblock2 (driver?)
[42949387.530000] 1f03           21888 mtdblock3 (driver?)
[42949387.540000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)

***************************************************************************






***************************************************************
            IFCONFIG
***************************************************************
justin@ubuntu:~$ ifconfig


eth0      Link encap:Ethernet  HWaddr 48:5b:39:b7:84:02 
          inet addr:192.168.1.50  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::4a5b:39ff:feb7:974f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:3693 (3.6 KB)
          Interrupt:29 Base address:0x2000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:132 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10660 (10.6 KB)  TX bytes:10660 (10.6 KB)
***************************************************************







***************************************************************
            PRINTENV
***************************************************************

DM355 LEOPARD # printenv
bootdelay=3
baudrate=115200
ethaddr="00:0e:99:00:05:2e"
bootfile="uImage"
ethact=dm9000
mtdparts=mtdparts=davinci_nand.0:640k(UBOOT),128k(UBOOT_ENV),3840k(KERNEL),21888k(FS)
mtdids=nand0=davinci_nand.0
filesize=338628
kernelloadaddr=0x82000000
kernelsaveaddr=0xC0000
kerneloffset=0xC0000
ksize=0x340000
kernelmd5sum=23c2767fb1fc9a9fbd2d732674843890
ipaddr=192.168.1.100
partition=nand0,0
mtddevnum=0
mtddevname=UBOOT
fssize=0x15537D4
fssaveaddr=0x480000
fsoffset=0x480000
bootargs=console=ttyS0,115200n8 video=davincifb:osd1=0x0x8 root=/dev/mtdblock3 rw mem=116M rootfstype=jffs2 mtdparts=davinci_nand.0:640k(UBOOT),128k(UBOOT_ENV),3840k(KERNEL),21888k(FS)
serverip=192.168.1.50
bootcmd=nboot KERNEL
autostart=yes
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2009.11 (May 13 2011 - 19:59:55)

Environment size: 799/131068 bytes
*******************************************************






***************************************************************
         MAKE CONFIG
***************************************************************

Make Config -> Architecture configurations:

     (192.168.1.50) Linux network IP address (eth0)                   
     (255.255.255.0) Linux network mask address for interface (eth0)  
     (48:5b:39:b7:84:02)Linux network ethernet address (eth0)


Make Config -> Installer Configuration:

 
      (0x82000000) RAM address to load components                                                  
       Communication method with the target board (Serial port)  --->                          
       (/dev/ttyS0) Serial port for target communication                                           
        Protocol for transfering images to the target (TFTP)  --->                              
      Flashing method for the bootloader (U-boot Commands)  --->                               
         *** Network options for installation ***                                                 
      (eth0) Interface on your host machine connected to your target hardware                      
      U-boot IP address (Static IP address)  --->                                               
      (192.168.1.100) Static IP                                                                   
     (255.255.255.0) Static mask                                                                  
      *** NAND Flash memory map (Partitions sizes are given in blocks number) ***               
     (5) Uboot partition size                                                                      
     (1) Uboot environment partition size                                                          
     (30) Minimum kernel partition size                                                             
     (160) Mininum file system partition size                                                        
      *** MTD Integration options ***                                                            
    [*] Configure Kernel MTD partitions with U-boot information                                     
   (davinci_nand.0) MTD device name                                                               
      MTD extra partitions  
      
********************************************************



********************************************************
        WHEN I CONNCT TO WIFI
********************************************************
justin@ubuntu:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 48:5b:39:b7:84:02
          inet6 addr: fe80::4a5b:39ff:feb7:974f/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:11856 (11.8 KB)
          Interrupt:29 Base address:0x2000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:14212 (14.2 KB)  TX bytes:14212 (14.2 KB)

wlan0     Link encap:Ethernet  HWaddr 00:0c:f6:85:d9:01 
          inet addr:192.168.1.103  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:f6ff:fe85:d901/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7250 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2969 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3766299 (3.7 MB)  TX bytes:657390 (657.3 KB)

dm355 nand DM355 RidgeRun SDK uboot dm355 ridgerun bootloader leopardboard 355
All Replies
  • Justin
    Posted by
    on 23 May 2011 11:26 AM

    Hi there.

    I'm not sure if this site is active anymore but anyway.

    I have come to realize that so many of the NAND blocks are bad that I cannot flash

    the file system onto my leopardboard 355.

    I would like to boot my board directly from the SD card. Is it possible to load the bootloader

    and kernel images directly from the SD card?? Is this possible using DM355SDK840402?

    I have ordered a new Leopadrboard 365, can the DM365SDK844703 do this?
  • Todd Fischer
    Posted by
    on 23 May 2011 11:35 AM

    Hi Justin,

    This site is still active.  I am disappointed more people don't contribute answers when they themselves have asked the same questions before.  I monitor all the posts and answer questions I haven't seen addressed before.

    For RidgeRun, the focus switched to DM365 when we were unable to resolve audio encode issues on DM355.  I don't answer DM355 questions as I haven't used that platform in more than a year.

    RidgeRun is about to publish an updated evaluation SDK for LeopardBoard 365.  It will support boot from SD card, so you don't need to touch the NAND chip.  We will also provide pre-built images you can load on SD cards so folks that don't want to rebuild the bootloader, kernel, or target file system can use the pre-built images.  I would expect the updated SDK to be available in around two weeks.

    Todd
  • Justin
    Posted by
    on 24 May 2011 2:36 AM

    Hi Todd.

    Wat is the product name or version number of the SDK to be updated? 844703?  Which site can I monitor to see when the SDK update is ready?

    Thank you for the reply.
  • Todd Fischer
    Posted by
    on 24 May 2011 9:49 AM

    We are updating the evaluation SDK for the LeopardBoard 365.  RidgeRun will send an email to everyone who indicated they wanted to be notified when an update is available at the time they requested an evaluation SDK.  We will also post on this forum when the updated evaluation SDK is available.
  • Justin
    Posted by
    on 13 Jun 2011 5:54 AM

    Hi Todd

    How is the updated SDK coming on?
About Designsomething.org  |  Terms of Use

Creative Commons License This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License