[#4369] kernel boot up stuck at smc91x.c on bf533 stamp board

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

[#4369] kernel boot up stuck at smc91x.c on bf533 stamp board

Submitted By: Mingquan Pan

Open Date

2008-08-19 06:47:11     Close Date

2008-09-02 23:11:35


Medium     Assignee:

Mike Frysinger


Closed     Fixed In Release:


Found In Release:

N/A     Release:


N/A     Board:



BF533     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:


Uboot version or rev.:

    Toolchain version or rev.:


App binary format:


Summary: kernel boot up stuck at smc91x.c on bf533 stamp board



kernel boot up stuck at smc91x.c on bf533 stamp board on trunk now, and no other messages followed.


bfin> boote

Loading .text @ 0x00001000 (1059616 bytes)

Loading .rodata @ 0x00103b20 (265020 bytes)

Loading .init.rodata @ 0x0014465c (80 bytes)

Loading __ksymtab @ 0x001446ac (15256 bytes)

Loading __ksymtab_gpl @ 0x00148244 (4664 bytes)

Loading __ksymtab_strings @ 0x0014947c (44079 bytes)

Loading __init_rodata @ 0x001540ac (172 bytes)

Loading __param @ 0x00154158 (380 bytes)

Clearing .bss @ 0x001542e0 (56428 bytes)

Loading .data @ 0x00161f4c (65716 bytes)

Loading .init.text @ 0x00172000 (86588 bytes)

Loading .init.data @ 0x0018723c (13524 bytes)

Loading .init.setup @ 0x0018a710 (636 bytes)

Loading .initcall.init @ 0x0018a98c (472 bytes)

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

Loading .init.ramfs @ 0x0018ab68 (2938743 bytes)

Loading .text_l1 @ 0xffa00000 (6948 bytes)

sh_addr: FFA00000, p_paddr: 004582DF

Loading from: 0244C000 to 004582DF, size: 6948

Loading .data_l1 @ 0xff800000 (192 bytes)

sh_addr: FF800000, p_paddr: 00459E03

Loading from: 0244E000 to 00459E03, size: 192

## Starting application at 0x0017d008 ...

Linux version (test@uclinux56-bf533-stamp-elf) (gcc version 4.1.2 (ADI svn)) #2 Tue Aug 19 18:49:49 MDT 2008

console [early_BFuart0] enabled

early printk enabled on early_BFuart0

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

Board Memory: 128MB

Kernel Managed Memory: 128MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x00103b20

  rodata    = 0x00103b20-0x001542d4

  bss       = 0x001542e0-0x00161f4c

  data      = 0x00161f4c-0x00172000

    stack   = 0x00170000-0x00172000

  init      = 0x00172000-0x0045a000

  available = 0x0045a000-0x037ff000

  DMA Zone  = 0x07f00000-0x08000000

Hardware Trace Active and Enabled

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

Compiled for ADSP-BF533 Rev 0.3

Blackfin Linux support by   blackfin.uclinux.org/

Processor Speed: 398 MHz core clock and 79 MHz System Clock

NOMPU: setting up cplb tables for global access

Instruction Cache Enabled

Data Cache Enabled (write-through)

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

Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart0,57600

Configuring Blackfin Priority Driven Interrupts

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

console handover: boot [early_BFuart0] -> real [ttyBF0]

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

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

Memory available: 52304k/131072k RAM, (2976k init code, 1034k kernel code, 442k data, 1024k dma, 73292k reserved)

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: 64 KB (57 KB free)

net_namespace: 192 bytes

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

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

msgmni has been set to 102

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

Serial: Blackfin serial driver

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

brd: module loaded

smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>


kernel config file is attached.




--- Mingquan Pan                                             2008-08-20 04:24:33

By reverting some of the checkins, it is found that this bug is due to the linux

5181 checkin.


--- Mingquan Pan                                             2008-08-20 05:06:07

This checkin also results in booting up failure on bf537 board, which would

print ramdom charactors on serial console,like:


Loading .text @ 0x00001000 (1061216 bytes)

Loading .rodata @ 0x00104160 (273168 bytes)

Loading .init.rodata @ 0x00146c70 (80 bytes)

Loading __ksymtab @ 0x00146cc0 (15520 bytes)

Loading __ksymtab_gpl @ 0x0014a960 (4664 bytes)

Loading __ksymtab_strings @ 0x0014bb98 (44678 bytes)

Loading __init_rodata @ 0x00156a20 (172 bytes)

Loading __param @ 0x00156acc (340 bytes)

Clearing .bss @ 0x00156c20 (58204 bytes)

Loading .data @ 0x00164f7c (69764 bytes)

Loading .init.text @ 0x00176000 (99480 bytes)

Loading .init.data @ 0x0018e498 (13536 bytes)

Loading .init.setup @ 0x00191978 (644 bytes)

Loading .initcall.init @ 0x00191bfc (480 bytes)

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

Loading .init.ramfs @ 0x00191de0 (4269171 bytes)

Loading .text_l1 @ 0xffa00000 (6932 bytes)

sh_addr: FFA00000, p_paddr: 005A4253

Loading from: 02597000 to 005A4253, size: 6932

Loading .data_l1 @ 0xff800000 (192 bytes)

sh_addr: FF800000, p_paddr: 005A5D67

Loading from: 02599000 to 005A5D67, size: 192

## Starting application at 0x001841e0 ...







spawn id exp6 not


--- Mingquan Pan                                             2008-08-21 02:33:26

Forget about the second following comment about bf537 board, which happens on

the board that is using old u-boot. If using 08r1.5 release u-boot, it can boot



As to the problem of bf533 board, it still exists with the board using 08r1.5



--- Mingquan Pan                                             2008-09-02 23:11:31

This issue is happened when using 08r1.5 u-boot to boot up the board. If using

trunk head 2009R1 u-boot,then it can be booted.


So close it.












File Name     File Type     File Size     Posted By

config.bf533    application/octet-stream    29366    Mingquan Pan