[#4204] Trunk kernel crashed on BF533-EZKIT after re-program clocks of kernel booting

Submitted By: Vivi Li

Open Date

2008-06-27 06:18:47 Close Date

2008-07-03 22:23:21

Priority:

Medium Assignee:

Michael Hennerich

Status:

Closed Fixed In Release:

N/A

Found In Release:

N/A Release:

Category:

N/A Board:

N/A

Processor:

N/A Silicon Revision:

Is this bug repeatable?:

Yes Resolution:

Fixed

Uboot version or rev.:

Toolchain version or rev.:

08r1-8

App binary format:

N/A

Summary: Trunk kernel crashed on BF533-EZKIT after re-program clocks of kernel booting

Details:

Re-program clocks when kernel boots, it crashed on BF533-EZKIT.

VCO_MULT is set to 16, CCLK_DIV is 1, SCLK_DIV is 5.

Attached is the kernel config file.

Linux version 2.6.24.7-ADI-2008R2-pre-svn4896 (test@uclinux46-bf533ezkit) (gcc version 4.1.2 (ADI svn)) #69 Thu Jun 26 21:55:55 CST 2008

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

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

fixedcode = 0x00000400-0x00000490

text = 0x00001000-0x000f9290

rodata = 0x000f93c0-0x00142178

bss = 0x00142180-0x0014f324

data = 0x0014f324-0x00162000

stack = 0x00160000-0x00162000

init = 0x00162000-0x003ec000

available = 0x003ec000-0x037ff000

DMA Zone = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Reset caused by Software reset

Compiled for ADSP-BF533 Rev 0.3

Warning: Compiled for Rev 3, but running on Rev 4

Blackfin Linux support by blackfin.uclinux.org/

Processor Speed: 432 MHz core clock and 86 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: 14224

Kernel command line: root=/dev/mtdblock0 rw ip=10.100.4.50:10.100.4.174:10.100.4.174:255.255.255.0::eth0:off

Configuring Blackfin Priority Driven Interrupts

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

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: 52744k/65536k RAM, (2600k init code, 992k kernel code, 420k data, 1024k dma, 7756k reserved)

Blackfin Scratchpad data SRAM: 4 KB

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

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

Blackfin Instruction SRAM: 64 KB (56 KB free)

Security Framework initialized

Mount-cache hash table entries: 512

net_namespace: 64 bytes

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

ezkit_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

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

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

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

eth0: SMC91C11xFD (rev 1) at 20310300 IRQ 42 [nowait]

eth0: Ethernet addr: 00:e0:22:fe:b1:2e

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@5

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

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

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting system clock to 2004-05-31 05:50:54 UTC (1085982654)

eth0: link down

IP-Config: Complete:

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

host=10.100.4.50, domain=, nis-domain=(none),

bootserver=10.100.4.174, rootserver=10.100.4.174, rootpath=

Freeing unused kernel memory: 2600k freed

dma_alloc_init: dma_page @ 0x003e9000 - 256 pages at 0x03f00000

NULL pointer access

Kernel OOPS in progress

Deferred Exception context

No Valid process in current context

return address: [0x0009334a]; contents of:

0x00093320: 0000 0000 e522 001a 3044 ae52 0062 0c00

0x00093330: 3038 101f 0c06 1028 0000 0000 a128 48d0

0x00093340: 1066 4af8 b128 916a 0031 [e410] 002d 4c08

0x00093350: e610 002d 60f8 0801 1812 e14a 0015 e10a

SEQUENCER STATUS: Not tainted

SEQSTAT: 00062027 IPEND: 8030 SYSCFG: 0006

HWERRCAUSE: 0x18

EXCAUSE : 0x27

physical IVG15 asserted : <0xffa00e80> { _evt_system_call + 0x0 }

logical irq 6 mapped : <0xffa00448> { _timer_interrupt + 0x0 }

logical irq 21 mapped : <0x000953c0> { _bfin_serial_dma_rx_int + 0x0 }

logical irq 22 mapped : <0x00095328> { _bfin_serial_dma_tx_int + 0x0 }

logical irq 42 mapped : <0x0009dc58> { _smc_interrupt + 0x0 }

RETE: <0x00000000> /* Maybe null pointer? */

Double Fault

Kernel OOPS in progress

Deferred Exception context

No Valid process in current context

return address: [0x00003cbc]; contents of:

0x00003c90: e10f f4b4 4374 3046 ce82 0d98 b233 0000

0x00003ca0: 3267 4f6e e521 0021 e12a 0084 3261 4414

0x00003cb0: 087c 18a4 0c04 1828 0000 0000 [e523] 0027

0x00003cc0: 0c43 1bf1 0000 0000 e51a 004c 0c42 180e

SEQUENCER STATUS: Not tainted

SEQSTAT: 00062027 IPEND: 0480 SYSCFG: 0006

HWERRCAUSE: 0x18

EXCAUSE : 0x27

physical IVG7 asserted : <0xffa00e2c> { _evt_evt7 + 0x0 }

physical IVG10 asserted : <0xffa00e50> { _evt_evt10 + 0x0 }

logical irq 6 mapped : <0xffa00448> { _timer_interrupt + 0x0 }

logical irq 21 mapped : <0x000953c0> { _bfin_serial_dma_rx_int + 0x0 }

logical irq 22 mapped : <0x00095328> { _bfin_serial_dma_tx_int + 0x0 }

logical irq 42 mapped : <0x0009dc58> { _smc_interrupt + 0x0 }

RETE: <0x00000000> /* Maybe null pointer? */

Follow-ups

--- Michael Hennerich 2008-06-27 08:00:09

assign to me

-Michael

--- Michael Hennerich 2008-06-30 15:25:39

Vivi,

The problem is not changing the frequencies – it’s more caused by changing

the SDRAM size and address width.

If your u-boot configures 32MB you can’t change this afterwards.

So make sure following config is set:

CONFIG_MEM_SIZE=32

CONFIG_MEM_ADD_WIDTH=9

If your u-boot configures 64MB you have to use this config:

CONFIG_MEM_SIZE=64

CONFIG_MEM_ADD_WIDTH=10

I will remove this kernel option.

-Michael

--- Michael Hennerich 2008-07-01 14:12:37

This should not happen again - fixed on svn trunk.

-Michael

--- Vivi Li 2008-07-03 22:23:21

CONFIG_MEM_SIZE is also not properly set according to different boards. I've add

it in build script, and it's OK now.

Close the bug. Thanks!

Files

Changes

Commits

Dependencies

Duplicates

Associations

Partner Forums

Partner Libraries

[#4204] Trunk kernel crashed on BF533-EZKIT after re-program clocks of kernel booting