[#4779] SVN 5932 BF548 kernel crashes when reboot

Submitted By: Sonic Zhang

Open Date

2009-01-07 22:36:10 Close Date

2009-01-07 22:37:24

Priority:

High Assignee:

Nobody

Status:

Closed Fixed In Release:

N/A

Found In Release:

N/A Release:

Category:

N/A Board:

EZKIT Lite

Processor:

BF548 Silicon Revision:

Is this bug repeatable?:

Yes Resolution:

Rejected

Uboot version or rev.:

Toolchain version or rev.:

App binary format:

N/A

Summary: SVN 5932 BF548 kernel crashes when reboot

Details:

BusyBox v1.13.1 (2009-01-08 11:23:20 CST) built-in shell (msh)

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

root:/>

root:/> reboot

sd 0:0:0:0: [sda] Synchronizing SCSI cache

Restarting system.

U-Boot 1.1.6-svn1322 (ADI-2008R2-pre) (Aug 14 2008 - 10:44:39)

CPU: ADSP bf548-0.0 (Detected Rev: 0.0)

Board: ADI BF548 EZ-Kit board

Support: blackfin.uclinux.org/

Clock: VCO: 525 MHz, Core: 525 MHz, System: 131 MHz

RAM: 64 MB

Flash:

Ack! Something bad happened to the Blackfin!

SEQUENCER STATUS:

SEQSTAT: 00002000 IPEND: 3fa00e2 SYSCFG: 0032

HWERRCAUSE: 0x0

EXCAUSE : 0x0

physical IVG6 asserted : <0x03fa0564> { _evt_default + 0x0 }

physical IVG7 asserted : <0x03fa0564> { _evt_default + 0x0 }

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

RETN: <0x0083fc88> /* unknown address */

RETX: <0x00000406> /* unknown address */

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

PC : <0x03fa00e2> { _start + 0xe2 }

PROCESSOR STATE:

R0 : 00000010 R1 : 00000008 R2 : 00000010 R3 : 00000000

R4 : 20000000 R5 : 07d2b750 R6 : 1f4add40 R7 : 000000ff

P0 : 000000ad P1 : 00000000 P2 : 03effe5b P3 : 03efff80

P4 : 03ffd408 P5 : 03efff80 FP : 03ffd408 SP : 03effd8c

LB0: 03fb9e8c LT0: 03fb9e80 LC0: 00000000

LB1: 03fb3662 LT1: 03fb3660 LC1: 00000000

B0 : 000005a0 L0 : 00000000 M0 : 00000000 I0 : 03effe4c

B1 : 00000000 L1 : 00000000 M1 : 00000000 I1 : 03e59f20

B2 : 00000000 L2 : 00000000 M2 : 00000000 I2 : 00000001

B3 : 00000000 L3 : 00000000 M3 : 00000000 I3 : 00001680

A0.w: 020d0000 A0.x: 00000000 A1.w: 000036da A1.x: 00000000

USP : ffb00ffc ASTAT: 00001004

Hardware Trace:

0 Target : <0x03fa0a34> { _bfin_panic + 0x0 }

Source : <0x03fa0bac> { _trap_c + 0x13c }

1 Target : <0x03fa0ba0> { _trap_c + 0x130 }

Source : <0x03fa0a8c> { _trap_c + 0x1c }

2 Target : <0x03fa0a70> { _trap_c + 0x0 }

Source : <0x03fa050a> { _trap + 0x56 }

3 Target : <0x03fa04b4> { _trap + 0x0 }

Source : <0x00000404> /* unknown address */

4 Target : <0x00000000> /* Maybe null pointer? */

Source : <0x03fa48ee> { _flash_write_cmd + 0x7a }

5 Target : <0x03fa48e8> { _flash_write_cmd + 0x74 }

Source : <0x03fa48b6> { _flash_write_cmd + 0x42 }

6 Target : <0x03fa48ac> { _flash_write_cmd + 0x38 }

Source : <0x03fa48a4> { _flash_write_cmd + 0x30 }

7 Target : <0x03fa489a> { _flash_write_cmd + 0x26 }

Source : <0x03fa4872> { _flash_make_cmd + 0x3a }

8 Target : <0x03fa485a> { _flash_make_cmd + 0x22 }

Source : <0x03fa4854> { _flash_make_cmd + 0x1c }

9 Target : <0x03fa484a> { _flash_make_cmd + 0x12 }

Source : <0x03fa486c> { _flash_make_cmd + 0x34 }

10 Target : <0x03fa485a> { _flash_make_cmd + 0x22 }

Source : <0x03fa4854> { _flash_make_cmd + 0x1c }

11 Target : <0x03fa484a> { _flash_make_cmd + 0x12 }

Source : <0x03fa486c> { _flash_make_cmd + 0x34 }

12 Target : <0x03fa485a> { _flash_make_cmd + 0x22 }

Source : <0x03fa4854> { _flash_make_cmd + 0x1c }

13 Target : <0x03fa484a> { _flash_make_cmd + 0x12 }

Source : <0x03fa486c> { _flash_make_cmd + 0x34 }

14 Target : <0x03fa485a> { _flash_make_cmd + 0x22 }

Source : <0x03fa4854> { _flash_make_cmd + 0x1c }

15 Target : <0x03fa484a> { _flash_make_cmd + 0x12 }

Source : <0x03fa486c> { _flash_make_cmd + 0x34 }

Please reset the board

### ERROR ### Please RESET the board ###

Follow-ups

--- Sonic Zhang 2009-01-07 22:37:24

Not kernel bug.

--- Mike Frysinger 2009-01-08 00:44:34

that's a pretty old u-boot version ... maybe it's the flash reset command you

fixed a while ago in u-boot ?

Files

Changes

Commits

Dependencies

Duplicates

Associations