This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

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

hi every body i'm working on DM6446 EVM when i try to boot it i get this :

yaffs: dev is 3145729 name is "hda1"

yaffs: Attempting MTD mount on 3.1, "hda1"

yaffs: dev is 3145729 name is "hda1"

yaffs: Attempting MTD mount on 3.1, "hda1"

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

how can i solve this problem plzz 

thank you 

  • Could you attach the bootup log and u-boot boot parameters here.

    I presume that you are trying to boot DM6446 EVM through hard disk.
    If that's the case, you can't use YAFFS2 filesystem since it is dedicated for flash devices like NAND,NOR etc.,

    Are you trying to boot EVM board with YAFFS2 mode ?

    If not, share your u-boot boot parameters.
  • thank you for reply,
    it was working for several days but now i get this error

    U-Boot 1.1.3 (Jun 16 2009 - 11:14:39)

    U-Boot code: 81080000 -> 810975E0 BSS: -> 8109FFD0
    RAM Configuration:
    Bank #0: 80000000 256 MB
    MY AMD Flash: 16 MB
    In: serial
    Out: serial
    Err: serial
    ARM Clock :- 297MHz
    DDR Clock :- 162MHz
    *****************************************************
    *TECHSHINE*
    *****************************************************
    Hit any key to stop autoboot: 0
    ## Booting image at 02060000 ...
    Image Name: Linux-2.6.10_mvl401-davinci_evm
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 1297860 Bytes = 1.2 MB
    Load Address: 80008000
    Entry Point: 80008000
    Verifying Checksum ... OK
    OK

    Starting kernel ...

    Uncompressing Lin...............................................................
    ....................... done, booting t Linux version 2.6.10_mvl401-davinci_evm
    (root@localhost.localdomain) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.30.050113
    1 2005-07-23)) #42 Fri Sep 19 20:02:52 CST 2008
    CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    Machine: DaVinci EVM
    Memory policy: ECC disabled, Data cache writeback
    Built 1 zonelists
    Kernel command line: mem=120M console=ttyS0,57600n8 video=dm64xxfb:interface=com
    posite:mode=ntsc:output=ntsc root=/dev/hda1 rw eth=00:0E:FF:FF:FF:85 ip=192.168.
    1.2::192.168.1.3 nfsroot=192.168.1.3:/home/filesys,nolock
    TI DaVinci EMAC: Kernel Boot params Eth address: 00:0E:FF:FF:FF:85
    PID hash table entries: 512 (order: 9, 8192 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: 120MB = 120MB total
    Memory: 118912KB available (2226K code, 473K data, 132K init)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: Testing write buffer coherency: ok
    spawn_desched_task(00000000)
    desched cpu_callback 3/00000000
    ksoftirqd started up.
    desched cpu_callback 2/00000000
    desched thread 0 started up.
    NET: Registered protocol family 16
    Registering platform device 'nor_davinci.0'. Parent at platform
    Registering platform device 'nand_davinci.0'. Parent at platform
    DaVinci I2C DEBUG: 19:57:22 Sep 19 2008
    Registering platform device 'i2c'. Parent at platform
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    yaffs Aug 6 2008 09:46:39 Installing.
    Registering platform device 'davincifb.0'. Parent at platform
    Console: switching to colour frame buffer device 90x30
    Registering platform device 'davinci_resizer.2'. Parent at platform
    Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
    Registering platform device 'serial8250'. Parent at platform
    ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
    io scheduler noop registered
    io scheduler anticipatory registered
    RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
    Registering platform device 'ti_davinci_emac'. Parent at platform
    DaVinci EMAC: Unable to read MAC from EEPROM, no i2c support in kernel.
    TI DaVinci EMAC: MAC address is 00:0E:FF:FF:FF:85
    TI DaVinci EMAC Linux version updated 4.0
    TI DaVinci EMAC: Installed 1 instances.
    netconsole: not configured, aborting
    i2c /dev entries driver
    Linux video capture interface: v1.00
    Registering platform device 'vpfe.1'. Parent at platform
    DaVinci v4l2 capture driver V1.0 loaded
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
    hda: SAMSUNG HM061GC, ATA DISK drive
    elevator: using anticipatory as default io scheduler
    ide0 at 0xe10661f0-0xe10661f7,0xe10663f6 on irq 22
    hda: max request size: 1024KiB
    hda: 117231408 sectors (60022 MB) w/8192KiB Cache, CHS=16383/255/63
    hda: hda1
    ide0: BM-DMA at 0xe1066000-0xe1066007, BIOS settings: hda:pio, hdb:pio
    mice: PS/2 mouse device common for all mice
    Registering platform device 'davinci-audio.0'. Parent at platform
    NET: Registered protocol family 2
    IP: routing cache hash table of 512 buckets, 4Kbytes
    TCP: Hash tables configured (established 8192 bind 16384)
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    IP-Config: Guessing netmask 255.255.255.0
    IP-Config: Complete:
    device=eth0, addr=192.168.1.2, mask=255.255.255.0, gw=192.168.1.3,
    host=192.168.1.2, domain=, nis-domain=(none),
    bootserver=255.255.255.255, rootserver=192.168.1.3, rootpath=
    yaffs: dev is 3145729 name is "hda1"
    yaffs: Attempting MTD mount on 3.1, "hda1"
    yaffs: dev is 3145729 name is "hda1"
    yaffs: Attempting MTD mount on 3.1, "hda1"
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
  • Hi Sisia,


    Kernel command line: mem=120M console=ttyS0,57600n8 video=dm64xxfb:interface=com
    posite:mode=ntsc:output=ntsc root=/dev/hda1 rw eth=00:0E:FF:FF:FF:85 ip=192.168.
    1.2::192.168.1.3 nfsroot=192.168.1.3:/home/filesys,nolock
    TI DaVinci EMAC: Kernel Boot params Eth address: 00:0E:FF:FF:FF:85


    The u-boot parameter seems to be wrong that you are trying to boot the through NFS but using "/dev/hda" drive.
    Try the following either bootargs.

    1) setenv bootargs 'mem=120M console=ttyS0,57600n8 video=dm64xxfb:interface=composite:mode=ntsc:output=ntsc root=/dev/nfs rw eth=00:0E:FF:FF:FF:85 ip=192.168.1.2::192.168.1.3 nfsroot=192.168.1.3:/home/filesys,nolock'

    2) setenv bootargs 'mem=120M console=ttyS0,57600n8 video=dm64xxfb:interface=composite:mode=ntsc:output=ntsc root=/dev/hda1 rw eth=00:0E:FF:FF:FF:85 ip=192.168.1.2::192.168.1.3'

  • hi Titusrathinaraj, 

    i've tried these command and when i try to boot i get this message : Unkonwn command 'mem=120M' -try help 

    for help: 

    autoscr - run script from memory

    base    - print or set address offset

    bdinfo  - print Board Info structure

    boot    - boot default, i.e., run 'bootcmd'

    bootd   - boot default, i.e., run 'bootcmd'

    bootm   - boot application image from memory

    bootp   - boot image via network using BootP/TFTP protocol

    cmp     - memory compare

    coninfo - print console devices and information

    cp      - memory copy

    crc32   - checksum calculation

    dhcp    - invoke DHCP client to obtain IP/boot params

    echo    - echo args to console

    erase   - erase FLASH memory

    flinfo  - print FLASH memory information

    go      - start application at address 'addr'

    help    - print online help

    iminfo  - print header information for application image

    imls    - list all images found in flash

    itest   - return true/false on integer compare

    loadb   - load binary file over serial line (kermit mode)

    loads   - load S-Record file over serial line

    loop    - infinite loop on address range

    md      - memory display

    mm      - memory modify (auto-incrementing)

    mtest   - simple RAM test

    mw      - memory write (fill)

    nfs     - boot image via network using NFS protocol

    nm      - memory modify (constant address)

    ping    - send ICMP ECHO_REQUEST to network host

    printenv- print environment variables

    protect - enable or disable FLASH write protection

    rarpboot- boot image via network using RARP/TFTP protocol

    reset   - Perform RESET of the CPU

    run     - run commands in an environment variable

    saveenv - save environment variables to persistent storage

    setenv  - set environment variables

    sleep   - delay execution for some time

    tftpboot- boot image via network using TFTP protocol

    version - print monitor version

    hope you help me for solving this problem

    best regards 

  • Hi,

    Apologize, some type here.
    Try now.

    1) setenv bootargs 'mem=120M console=ttyS0,57600n8 video=dm64xxfb:interface=composite:mode=ntsc:output=ntsc root=/dev/nfs rw eth=00:0E:FF:FF:FF:85 ip=192.168.1.2::192.168.1.3 nfsroot=192.168.1.3:/home/filesys,nolock'

    2) setenv bootargs 'mem=120M console=ttyS0,57600n8 video=dm64xxfb:interface=composite:mode=ntsc:output=ntsc root=/dev/hda1 rw eth=00:0E:FF:FF:FF:85 ip=192.168.1.2::192.168.1.3'
  • hi TituS, i still have that probem when i put the first command i get this error :

    VFS: Unable to mount root fs via NFS, trying floppy.

    VFS: Cannot open root device "nfs" or unknown-block(2,0)

    Please append a correct "root=" boot option

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

    and for the second command i get the same error that i have for the first time! i'm new in linux i saw this link  

    e2e.ti.com/.../110353

    but i'm still confused about how to solve this problem

    best regards  

  • Could you try the following boot parameter.

    setenv bootargs 'mem=120M console=ttyS0,57600n8 video=dm64xxfb:interface=composite:mode=ntsc:output=ntsc root=/dev/nfs rw
    eth=00:0E:FF:FF:FF:85 ip=dhcp nfsroot=192.168.1.3:/home/filesys,nolock'

    Do you want to boot the board through static IP (fixed Ip address) ?

    Have you tried to boot through DHCP like above I mentioned boot parameter ?