[#4764] Kernel prints warning when booting from jffs2 rootfs in nor flash on bf548-ezkit

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

[#4764] Kernel prints warning when booting from jffs2 rootfs in nor flash on bf548-ezkit

Submitted By: Sonic Zhang

Open Date

2008-12-29 23:00:39     Close Date

2010-02-22 10:28:55

Priority:

Very Low     Assignee:

Michael Hennerich

Status:

Closed     Fixed In Release:

N/A

Found In Release:

2010R1     Release:

SVN trunk

Category:

N/A     Board:

EZKIT Lite

Processor:

BF548     Silicon Revision:

0.1

Is this bug repeatable?:

Yes     Resolution:

Assigned (Not Start)

Uboot version or rev.:

    Toolchain version or rev.:

all

App binary format:

N/A     

Summary: Kernel prints warning when booting from jffs2 rootfs in nor flash on bf548-ezkit

Details:

 

Build jffs2 image by mkfs.jffs2. Flash into nor flash on bf548-ezkit in uboot. Kernel prints warning when booting from jffs2 rootfs.

 

----------------------------------------------------------

bootm 0x20040000

## Booting image at 20040000 ...

   Image Name:   Linux-2.6.28-rc2-ADI-2009R1-pre-

   Created:      2008-12-30   3:36:57 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    1351418 Bytes =  1.3 MB

   Load Address: 00001000

   Entry Point:  00262be0

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 262be0

Linux version 2.6.28-rc2-ADI-2009R1-pre-svn5909 (root@eight) (gcc version 4.1.2 (ADI svn)) #58 Tue De8

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x0019c410

  rodata    = 0x0019c410-0x0022458c

  bss       = 0x00224590-0x00237e34

  data      = 0x00237e34-0x00250000

    stack   = 0x0024e000-0x00250000

  init      = 0x00250000-0x00277000

  available = 0x00277000-0x03dff000

  DMA Zone  = 0x03e00000-0x04000000

Hardware Trace Active and Enabled

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

Compiled for ADSP-BF548 Rev 0.0

Blackfin Linux support by   blackfin.uclinux.org/

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

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

Data Cache Enabled for CPU0 (write-through)

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

Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2 console=tty0 console=ttyBF0,57600

Configuring Blackfin Priority Driven Interrupts

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

Console: colour dummy device 80x25

console [tty0] enabled

console [ttyBF0] enabled

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

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

Memory available: 60376k/65536k RAM, (156k init code, 1645k kernel code, 719k data, 2048k dma, 588k r)

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

Security Framework initialized

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

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

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

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

Blackfin L2 SRAM: 128 KB (128 KB free)

PDA for CPU0 reserved at 00225a10

net_namespace: 288 bytes

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

ezkit_init(): registering device resources

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

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

musb_hdrc: USB Host mode controller at ffc03c00 using DMA, IRQ 82

musb_hdrc musb_hdrc.0: MUSB HDRC host driver

musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

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

hub 1-0:1.0: 1 port detected

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

NET: Registered protocol family 1

JFFS2 version 2.2. (NAND)  2001-2006 Red Hat, Inc.

msgmni has been set to 117

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bfin-otp: initialized

Serial: Blackfin serial driver

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

brd: module loaded

smsc911x: Driver version 2007-07-13.

eth0: SMSC911x MAC Address: 00:81:ab:be:5d:f1

Driver 'sd' needs updating - please use bus_type methods

Driver 'sr' needs updating - please use bus_type methods

register bfin atapi driver

scsi0 : pata-bf54x

ata1: PATA max UDMA/66 irq 68

ata1.00: ATA-4: HITACHI_DK229A-10, 00X7A0C0, max UDMA/33

ata1.00: 19640880 sectors, multi 0: LBA

ata1.00: configured for UDMA/33

blk_queue_max_hw_segments: set to minimum 1

scsi 0:0:0:0: Direct-Access     ATA      HITACHI_DK229A-1 00X7 PQ: 0 ANSI: 5

sd 0:0:0:0: [sda] 19640880 512-byte hardware sectors: (10.0 GB/9.36 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

sd 0:0:0:0: [sda] 19640880 512-byte hardware sectors: (10.0 GB/9.36 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

physmap platform flash device: 02000000 at 20000000

physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank

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 3 MTD partitions on "physmap-flash.0":

0x00000000-0x00040000 : "bootloader(nor)"

0x00040000-0x00440000 : "linux kernel(nor)"

0x00440000-0x02000000 : "file system(nor)"

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

bf5xx-nand bf5xx-nand.0: page_size=256, 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 2 MTD partitions on "NAND 256MiB 3,3V 8-bit":

0x00000000-0x00400000 : "linux kernel(nand)"

0x00400000-0x10000000 : "file system(nand)"

input: bf54x-keys as /class/input/input0

bf54x-keys: Blackfin BF54x Keypad registered IRQ 76

i2c /dev entries driver

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

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver

TCP cubic registered

NET: Registered protocol family 17

Empty flash at 0x0000fffc ends at 0x00010000

CLEANMARKER node found at 0x00010000, not first node in block (0x00000000)

Empty flash at 0x0002fffc ends at 0x00030000

CLEANMARKER node found at 0x00030000, not first node in block (0x00020000)

Empty flash at 0x0004fffc ends at 0x00050000

CLEANMARKER node found at 0x00050000, not first node in block (0x00040000)

Empty flash at 0x0006fffc ends at 0x00070000

CLEANMARKER node found at 0x00070000, not first node in block (0x00060000)

Empty flash at 0x0008fffc ends at 0x00090000

CLEANMARKER node found at 0x00090000, not first node in block (0x00080000)

Empty flash at 0x000afffc ends at 0x000b0000

CLEANMARKER node found at 0x000b0000, not first node in block (0x000a0000)

CLEANMARKER node found at 0x000d0000, not first node in block (0x000c0000)

Empty flash at 0x000efffc ends at 0x000f0000

CLEANMARKER node found at 0x000f0000, not first node in block (0x000e0000)

Empty flash at 0x0010fffc ends at 0x00110000

CLEANMARKER node found at 0x00110000, not first node in block (0x00100000)

Empty flash at 0x0012fffc ends at 0x00130000

CLEANMARKER node found at 0x00130000, not first node in block (0x00120000)

Empty flash at 0x0014fffc ends at 0x00150000

CLEANMARKER node found at 0x00150000, not first node in block (0x00140000)

Empty flash at 0x0016fffc ends at 0x00170000

CLEANMARKER node found at 0x00170000, not first node in block (0x00160000)

Empty flash at 0x0018fffc ends at 0x00190000

CLEANMARKER node found at 0x00190000, not first node in block (0x00180000)

CLEANMARKER node found at 0x001b0000, not first node in block (0x001a0000)

Empty flash at 0x001cfffc ends at 0x001d0000

CLEANMARKER node found at 0x001d0000, not first node in block (0x001c0000)

Empty flash at 0x001efffc ends at 0x001f0000

CLEANMARKER node found at 0x001f0000, not first node in block (0x001e0000)

Empty flash at 0x0020fffc ends at 0x00210000

CLEANMARKER node found at 0x00210000, not first node in block (0x00200000)

Empty flash at 0x0022fffc ends at 0x00230000

CLEANMARKER node found at 0x00230000, not first node in block (0x00220000)

Empty flash at 0x0024fffc ends at 0x00250000

CLEANMARKER node found at 0x00250000, not first node in block (0x00240000)

Empty flash at 0x0026fffc ends at 0x00270000

CLEANMARKER node found at 0x00270000, not first node in block (0x00260000)

Empty flash at 0x0028fffc ends at 0x00290000

CLEANMARKER node found at 0x00290000, not first node in block (0x00280000)

Empty flash at 0x002afffc ends at 0x002b0000

CLEANMARKER node found at 0x002b0000, not first node in block (0x002a0000)

Empty flash at 0x002cfffc ends at 0x002d0000

CLEANMARKER node found at 0x002d0000, not first node in block (0x002c0000)

CLEANMARKER node found at 0x002f0000, not first node in block (0x002e0000)

Empty flash at 0x0030fffc ends at 0x00310000

CLEANMARKER node found at 0x00310000, not first node in block (0x00300000)

Empty flash at 0x0032fffc ends at 0x00330000

CLEANMARKER node found at 0x00330000, not first node in block (0x00320000)

Empty flash at 0x0034fffc ends at 0x00350000

CLEANMARKER node found at 0x00350000, not first node in block (0x00340000)

Empty flash at 0x0036fffc ends at 0x00370000

CLEANMARKER node found at 0x00370000, not first node in block (0x00360000)

Empty flash at 0x0038ffc8 ends at 0x00390000

CLEANMARKER node found at 0x00390000, not first node in block (0x00380000)

Empty flash at 0x003afffc ends at 0x003b0000

CLEANMARKER node found at 0x003b0000, not first node in block (0x003a0000)

Empty flash at 0x003cfffc ends at 0x003d0000

CLEANMARKER node found at 0x003d0000, not first node in block (0x003c0000)

Empty flash at 0x003efffc ends at 0x003f0000

CLEANMARKER node found at 0x003f0000, not first node in block (0x003e0000)

VFS: Mounted root (jffs2 filesystem).

Freeing unused kernel memory: 156k freed

                           _____________________________________

        a8888b.           / Welcome to the uClinux distribution \

       d888888b.         /       _     _                         \

       8P"YP"Y88        /       | |   |_|            __  __ (TM)  |

       8|o||o|88  _____/        | |    _ ____  _   _ \ \/ /       |

       8'    .88       \        | |   | |  _ \| | | | \  /        |

       8`._.' Y8.       \       | |__ | | | | | |_| | /  \        |

      d/      `8b.       \      \____||_|_| |_|\____|/_/\_\       |

     dP   .    Y8b.       \   For embedded processors including   |

    d8:'  "  `::88b        \    the Analog Devices Blackfin      /

   d8"         'Y88b        \___________________________________/

  :8P    '      :888

   8a.   :     _a88P         For further information, check out:

._/"Yaa_:   .| 88P|            -   blackfin.uclinux.org/

\    YP"    `| 8P  `.          -   docs.blackfin.uclinux.org/

/     \.___.d|    .'           -   www.uclinux.org/

`--..__)8888P`._.'  jgs/a:f    -   www.analog.com/blackfin

 

Have a lot of fun...

 

 

BusyBox v1.13.1 (2008-12-29 16:21:15 CST) built-in shell (msh)

Enter 'help' for a list of built-in commands.

 

root:/> ls

bin   dev   etc   home  lib   mnt   proc  root  sbin  sys   tmp   usr   var                          

 

Follow-ups

 

--- Sonic Zhang                                              2008-12-29 23:07:45

If creates the jffs2 rootfs in linux by mount and copy instead of mkfs.jffs2,

the warning disappears.

 

A possible difference is that the mkfs.jffs2 doesn't generated CLEANMARKER node

in correct position. The other possible difference is that the jffs2 image

created by mkfs.jffs2 is smaller than the size of rootfs MTD partition.

 

--- Sonic Zhang                                              2008-12-30 01:11:09

This bug is confirmed to have nothing to do with size mismatch. The only

possible cause is the mismatch of mkfs.jffs2 and jffs2 driver in kernel

2.6.28-rc2.

 

--- Mike Frysinger                                           2008-12-30 01:29:18

i dont really think so ... the cleanmarker position is dependent on the flash in

use and we havent been tracking it at all for any board

 

--- Sonic Zhang                                              2008-12-30 01:57:50

Does that means the mkfs.jffs2 should understand the cleanmarker position for

different flash?

 

--- Mike Frysinger                                           2008-12-30 02:44:15

afaik, it means we need to add cleanmarker flags in each uclinux-dist board

config Makefile.  Michael would know more, but i think he's on vacation atm ...

 

--- Sonic Zhang                                              2009-01-09 04:30:53

It seems this bug doesn't break the jffs2 filesystem on nor flash. JFFS2

regression test can still running to its end. Down its priority.

 

--- Michael Hennerich                                        2009-07-27 06:36:10

First of all - the warnings are harmless -

 

Some Flash Memory Technologies Devices require a specially structured JFFS2

filesystem image. Therefore additional flags for mkfs.jffs2 must be given during

the uClinux-dist build process.

We therefore added the MKFS_JFFS2_FLAGS variable -

 

From top of my head I don't know the erase block size of the 28F128 try:

 

make MKFS_JFFS2_FLAGS='-e 0x40000'

 

IIRC there is procfs entry that tells you exactly what the erase block size

need to be...

 

  docs.blackfin.uclinux.org/doku.php?id=linux-kernel:jffs&s[]=mkfs&s[]=jffs2&s[]=flags

 

--- Mike Frysinger                                           2009-07-27 13:14:15

/proc/mtd has that info

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes