FAQ: [#6679] mount nand ubifs as rootfs fails on bf548 ezkit(2011)

Document created by Aaronwu Employee on Sep 12, 2013
Version 1Show Document
  • View in full screen mode

[#6679] mount nand ubifs as rootfs fails on bf548 ezkit

Submitted By: Mingquan Pan

Open Date

2011-07-05 04:04:24     Close Date

2011-07-10 23:17:59

Priority:

Medium     Assignee:

steven miao

Status:

Closed     Fixed In Release:

N/A

Found In Release:

2011R1     Release:

Category:

N/A     Board:

N/A

Processor:

ALL     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Fixed

Uboot version or rev.:

    Toolchain version or rev.:

5013

App binary format:

N/A     

Summary: mount nand ubifs as rootfs fails on bf548 ezkit

Details:

 

mount nand ubifs as rootfs fails on bf548 ezkit from Jun 15.

 

bfin> bootm

## Booting kernel from Legacy Image at 02000000 ...

   Image Name:   bf548-0.2-2.6.39.1-ADI-2011R1-pr

   Created:      2011-06-22  16:47:50 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    1611263 Bytes = 1.5 MiB

   Load Address: 00001000

   Entry Point:  002c5e08

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 002c5e08

Linux version 2.6.39.1-ADI-2011R1-pre-svn9965 (test@uclinux61-bf548-std) (gcc version 4.3.5 (ADI-trunk/svn-5013) ) #7 Thu Jun 23 00:47:44 CST 2011

register early platform devices

bootconsole [early_shadow0] enabled

bootconsole [early_BFuart1] enabled

early printk enabled on early_BFuart1

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x001e67c0

  rodata    = 0x001e67c0-0x00288204

  bss       = 0x00289000-0x0029c87c

  data      = 0x0029c87c-0x002bc000

    stack   = 0x002ba000-0x002bc000

  init      = 0x002bc000-0x002e1000

  available = 0x002e1000-0x03e00000

  DMA Zone  = 0x03e00000-0x04000000

Hardware Trace active and enabled

Boot Mode: 1

Reset caused by Software reset

Blackfin support (C) 2004-2010 Analog Devices, Inc.

Compiled for ADSP-BF548 Rev 0.2

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

Processor Speed: 525 MHz core clock and 131 MHz System Clock

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

  External memory: cacheable in instruction cache

  L2 SRAM        : uncacheable in instruction cache

Data Cache Enabled for CPU0

  External memory: cacheable (write-through) in data cache

  L2 SRAM        : uncacheable in data cache

Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 15748

Kernel command line: ubi.mtd=7 root=ubi0:ubifs1 rw rootfstype=ubifs earlyprintk=serial,uart1,57600 console=ttyBF1,57600 ip=10.100.4.50:10.100.4.174:10.100.4.174:255.255.255.0:bf548-ezkit:eth0:off

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

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

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

Memory available: 59932k/65536k RAM, (148k init code, 1941k kernel code, 855k data, 2048k dma, 612k reserved)

NR_IRQS:295

Configuring Blackfin Priority Driven Interrupts

console [ttyBF1] enabled, bootconsole disabled

console [ttyBF1] enabled, bootconsole disabled

Calibrating delay loop... 1044.48 BogoMIPS (lpj=2088960)

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

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

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

Blackfin L1 Instruction SRAM: 48 KB (41 KB free)

Blackfin L2 SRAM: 128 KB (128 KB free)

NET: Registered protocol family 16

Blackfin DMA Controller

ezkit_init(): registering device resources

bio: create slab <bio-0> at 0

SCSI subsystem initialized

spi spi0.2: Warning: SPI CPHA not set: Slave Select not under software control!

See Documentation/blackfin/bfin-spi-notes.txt

bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs@ffc00500, dma channel@4

bfin-spi bfin-spi.1: Blackfin on-chip SPI Controller Driver, Version 1.0, regs@ffc02300, dma channel@5

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc00700

i2c-bfin-twi i2c-bfin-twi.1: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc02200

Advanced Linux Sound Architecture Driver Version 1.0.24.

musb-hdrc: version 6.0, musb-dma, host, debug=0

musb-hdrc musb-hdrc: MUSB HDRC host driver

musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 1

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

musb-hdrc musb-hdrc: USB Host mode controller at ffc03c00 using DMA, IRQ 82

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

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

debug-mmrs: setting up Blackfin MMR debugfs

msgmni has been set to 117

io scheduler noop registered (default)

bf54x-lq043: FrameBuffer initializing...

dma_alloc_init: dma_page @ 0x02197000 - 512 pages at 0x03e00000

bfin-uart: Blackfin serial driver

bfin-uart.1: ttyBF1 at MMIO 0xffc02000 (irq = 48) is a BFIN-UART

bfin-otp: initialized

brd: module loaded

register bfin atapi driver

scsi0 : pata-bf54x

ata1: PATA max UDMA/66 irq 68

physmap platform flash device: 02000000 at 20000000

physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x00881e

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Using buffer write method

Using auto-unlock on power-up/resume

cfi_cmdset_0001: Erase suspend on write enabled

RedBoot partition parsing not available

Using physmap partition information

Creating 5 MTD partitions on "physmap-flash.0":

0x000000000000-0x000000080000 : "bootloader(nor)"

0x000000080000-0x000000480000 : "linux kernel(nor)"

0x000000480000-0x000000fe0000 : "file system(nor)"

0x000000fe0000-0x000000ff8000 : "config(nor)"

0x000000ff8000-0x000001000000 : "u-boot env(nor)"

m25p80 spi0.1: m25p16 (2048 Kbytes)

Creating 2 MTD partitions on "m25p80":

0x000000000000-0x000000080000 : "bootloader(spi)"

0x000000080000-0x000000200000 : "linux kernel(spi)"

BF5xx on-chip NAND FLash Controller Driver, Version 1.2 (c) 2007 Analog Devices, Inc.

bf5xx-nand bf5xx-nand.0: data_width=8, wr_dly=3, rd_dly=3

NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit)

Creating 3 MTD partitions on "NAND 256MiB 3,3V 8-bit":

0x000000000000-0x000000080000 : "bootloader(nand)"

0x000000080000-0x000000480000 : "linux kernel(nand)"

0x000000480000-0x000010000000 : "file system(nand)"

UBI: attaching mtd7 to ubi0

UBI: physical eraseblock size:   131072 bytes (128 KiB)

UBI: logical eraseblock size:    129024 bytes

UBI: smallest flash I/O unit:    2048

UBI: sub-page size:              512

UBI: VID header offset:          512 (aligned 512)

UBI: data offset:                2048

UBI: max. sequence number:       0

UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 0, need 2

UBI: attached mtd7 to ubi0

UBI: MTD device name:            "bootloader(nand)"

UBI: MTD device size:            0 MiB

UBI: number of good PEBs:        4

UBI: number of bad PEBs:         0

UBI: number of corrupted PEBs:   0

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     0

UBI: available PEBs:             0

UBI: total number of reserved PEBs: 4

UBI: number of PEBs reserved for bad PEB handling: 0

UBI: max/mean erase counter: 12/12

UBI: image sequence number:  0

UBI: background thread "ubi_bgt0d" started, PID 289

smsc911x: Driver version 2008-10-21.

smsc911x-mdio: probed

eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)

net eth0: MAC Address: 00:e0:22:fe:bf:4e

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

input: bf54x-keys as /devices/platform/bf54x-keys/input/input0

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

i2c /dev entries driver

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

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

ALSA device list:

  No soundcards found.

TCP cubic registered

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting system clock to 2004-05-31 07:03:33 UTC (1085987013)

mmc0: host does not support reading read-only switch. assuming write-enable.

mmc0: new SD card at address e624

ata1.00: ATA-6: TOSHIBA MK4032GAX, AD101A, max UDMA/100

ata1.00: 78140160 sectors, multi 16: LBA48

ata1.00: configured for UDMA/66

blk_queue_max_segments: set to minimum 1

scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MK4032GA AD10 PQ: 0 ANSI: 5

sd 0:0:0:0: [sda] 78140160 512-byte logical blocks: (40.0 GB/37.2 GiB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

sda: sda1 sda2

sd 0:0:0:0: [sda] Attached SCSI disk

net eth0: SMSC911x/921x identified at 0x24000000, IRQ: 175

IP-Config: Complete:

     device=eth0, addr=10.100.4.50, mask=255.255.255.0, gw=10.100.4.174,

     host=bf548-ezkit, domain=, nis-domain=(none),

     bootserver=10.100.4.174, rootserver=10.100.4.174, rootpath=

VFS: Cannot open root device "ubi0:ubifs1" or unknown-block(0,0)

Please append a correct "root=" boot option; here are the available partitions:

1f00             512 mtdblock0  (driver?)

1f01            4096 mtdblock1  (driver?)

1f02           11648 mtdblock2  (driver?)

1f03              96 mtdblock3  (driver?)

1f04              32 mtdblock4  (driver?)

1f05             512 mtdblock5  (driver?)

1f06            1536 mtdblock6  (driver?)

1f07             512 mtdblock7  (driver?)

1f08            4096 mtdblock8  (driver?)

1f09          257536 mtdblock9  (driver?)

0800        39070080 sda  driver: sd

  0801         8193118 sda1 00000000-0000-0000-0000-000000000000sda1

  0802        20482875 sda2 00000000-0000-0000-0000-000000000000sda2

Kernel panic - not syncing: VFSkernel panic detected... trying to recover from ittest@uclinux61-bf548-std:~/work/cruise/test_scripts/uclinux-dist/logs> ;9R;9R;9R;9R;9R;9R;2R;9R;9R;9R;1R;9R;9R;9R;9R;9R;9R;9R;9R;9R;9R;9R;9R;1R;1R;9R;1R;1R;9R;9R;9R;9R;9R;9R;9R;9R

 

 

last passed version:

root:/> ^[[6nversion^M

kernel:    Linux release 2.6.39.1-ADI-2011R1-pre-svn9931, build #7 Thu Jun 16 02:17:10 CST 2011^M

toolchain: bfin-uclinux-gcc release gcc version 4.3.5 (ADI-trunk/svn-5013) ^M

user-dist: release svn-10203, build #24 Thu Jun 16 02:15:54 CST 2011^M

root:/> ^[[6nsuccessful boot attemptdmesg|grep -i ubiusb 1-1: new high speed USB device number 2 using musb-hdrc^M

fscsi1 : usb-storage 1-1:1.0^M

s^M

Kernel command line: ubi.mtd=7 root=ubi0:ubifs1 rw rootfstype=ubifs earlyprintk=serial,uart1,57600 console=ttyBF1,57600 ip=10.100.4.50:10.100.4.174:10.100.4.174:255.255.255.0:bf548-ezkit:eth0:off^M

UBIFS: mounted UBI device 0, volume 1, name "ubifs1"^M

UBIFS: file system size:   19611648 bytes (19152 KiB, 18 MiB, 152 LEBs)^M

UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)^M

UBIFS: media format:       w4/r0 (latest is w4/r0)^M

UBIFS: default compressor: lzo^M

UBIFS: reserved for root:  0 bytes (0 KiB)^M

VFS: Mounted root (ubifs filesystem) on device 0:12.^M

 

Follow-ups

 

--- steven miao                                              2011-07-07 04:57:21

is there any section mismatch warning when build kernel?

 

--- Mingquan Pan                                             2011-07-07 05:03:41

I post the build log and kernel config file. You can have a look.

 

--- steven miao                                              2011-07-08 02:04:06

it seems ubi image download to mtd9 partition, but bootargs still set to mtd7

 

ubiattach /dev/ubi_ctrl -m 9^M

 

Kernel command line: ubi.mtd=7 root=ubi0:ubifs1 rw rootfstype=ubifs

earlyprintk=serial,uart1,57600 console=ttyBF1,57600

ip=10.100.4.50:10.100.4.174:10.100.4.174:255.255.255.0:bf548-ezkit:eth0:off^M

 

--- Mingquan Pan                                             2011-07-10 23:15:59

Yes, after setting the right partition number, it boots up ok now. Close.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

build_nand_kernel_log    application/octet-stream    472774    Mingquan Pan

config.linux.nand    application/octet-stream    49342    Mingquan Pan

Outcomes