[#5374] Bluetooth kernel crashed in bf537-stamp with cf extender

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

[#5374] Bluetooth kernel crashed in bf537-stamp with cf extender

Submitted By: Vivi Li

Open Date

2009-07-20 04:14:05     Close Date

2009-07-22 05:22:27

Priority:

Medium High     Assignee:

Michael Hennerich

Status:

Closed     Fixed In Release:

N/A

Found In Release:

N/A     Release:

Category:

Drivers     Board:

STAMP

Processor:

BF537     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Fixed

Uboot version or rev.:

    Toolchain version or rev.:

gcc4.1_2009r1-rc9

App binary format:

N/A     

Summary: Bluetooth kernel crashed in bf537-stamp with cf extender

Details:

 

Bluetooth kernel crashed in bf537-stamp with cf extender.

 

Hardware config on bf537-stamp:

--

sw5: all OFF

sw6: ON/ON/OFF/OFF

--

 

Bellow is the log:

--

Linux version 2.6.28.10-ADI-2009R1-svn7029 (test@uclinux50-bf537-ad9960-ad1836) (gcc version 4.1.2 (ADI svn)) #32 Mon Jul 20 07:9

bootconsole [early_shadow0] enabled

bootconsole [early_BFuart0] enabled

early printk enabled on early_BFuart0

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

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x0011f000

  rodata    = 0x0011f000-0x001763e8

  bss       = 0x00177000-0x001887c0

  data      = 0x001887c0-0x0019a000

    stack   = 0x00198000-0x0019a000

  init      = 0x0019a000-0x00993000

  available = 0x00993000-0x037ff000

  DMA Zone  = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Boot Mode: 0

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

Compiled for ADSP-BF537 Rev 0.2

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

Processor Speed: 500 MHz core clock and 62 MHz System Clock

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

Data Cache Enabled for CPU0 (write-back)

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

Kernel command line: root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600 ip=10.100.4.50f

Configuring Blackfin Priority Driven Interrupts

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

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

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

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

Memory available: 46968k/65536k RAM, (8164k init code, 1144k kernel code, 492k data, 1024k dma, 7744k reserved)

Calibrating delay loop... 993.28 BogoMIPS (lpj=1986560)

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 (36 KB free)

net_namespace: 288 bytes

NET: Registered protocol family 16

Blackfin DMA Controller

stamp_init(): registering device resources

Bluetooth: Core ver 2.13

NET: Registered protocol family 31

Bluetooth: HCI device and connection manager initialized

Bluetooth: HCI socket layer initialized

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 91

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 = 18) is a BFIN-UART

brd: module loaded

bfin_mii_bus: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=11)@sclk=62MHz)

bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1

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

bfin_cf_pcmcia bfin_cf_pcmcia: Blackfin CompactFlash/PCMCIA Socket Driver

bfin_cf_pcmcia bfin_cf_pcmcia: : on irq 54

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 17

Bluetooth: L2CAP ver 2.11

Bluetooth: L2CAP socket layer initialized

Bluetooth: SCO (Voice Link) ver 0.6

Bluetooth: SCO socket layer initialized

Bluetooth: RFCOMM socket layer initialized

Bluetooth: RFCOMM TTY layer initialized

Bluetooth: RFCOMM ver 1.10

Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Bluetooth: BNEP filters: protocol multicast

Bluetooth: HIDP (Human Interface Emulation) ver 1.2

rtc-bfin rtc-bfin: setting system clock to 1970-01-01 00:01:22 UTC (82)

pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0

pcmcia 0.0: pcmcia: registering new device pcmcia0.0

Hardware Trace:

   0 Target : <0x0000483c> { _dump_bfin_trace_buffer + 0x0 }

     Source : <0x000b48dc> { _bluecard_interrupt + 0x124 } CALL pcrel

   1 Target : <0x000b48dc> { _bluecard_interrupt + 0x124 }

     Source : <0x000b47c4> { _bluecard_interrupt + 0xc } IF !CC JUMP

   2 Target : <0x000b47b8> { _bluecard_interrupt + 0x0 }

     Source : <0x0002ca14> { _request_irq + 0xac } CALL (P4)

   3 Target : <0x0002ca0a> { _request_irq + 0xa2 }

     Source : <0x0002c656> { _disable_irq + 0x3e } RTS

   4 Target : <0x0002c64a> { _disable_irq + 0x32 }

     Source : <0x0002c606> { _disable_irq_nosync + 0x5a } RTS

   5 Target : <0x0002c5ec> { _disable_irq_nosync + 0x40 }

     Source : <0x0002c616> { _disable_irq_nosync + 0x6a } JUMP.S

   6 Target : <0x0002c616> { _disable_irq_nosync + 0x6a }

     Source : <0x00005a84> { _set_gpio_maska + 0x40 } RTS

   7 Target : <0x00005a68> { _set_gpio_maska + 0x24 }

     Source : <0x00005a48> { _set_gpio_maska + 0x4 } IF CC JUMP

   8 Target : <0x00005a44> { _set_gpio_maska + 0x0 }

     Source : <0x00008cc4> { _bfin_gpio_mask_irq + 0x4 } JUMP.L

   9 Target : <0x00008cc0> { _bfin_gpio_mask_irq + 0x0 }

     Source : <0x0002c614> { _disable_irq_nosync + 0x68 } CALL (P2)

  10 Target : <0x0002c608> { _disable_irq_nosync + 0x5c }

     Source : <0x0002c5ea> { _disable_irq_nosync + 0x3e } IF !CC JUMP

  11 Target : <0x0002c5ac> { _disable_irq_nosync + 0x0 }

     Source : <0x0002c646> { _disable_irq + 0x2e } CALL pcrel

  12 Target : <0x0002c618> { _disable_irq + 0x0 }

     Source : <0x0002ca06> { _request_irq + 0x9e } CALL pcrel

  13 Target : <0x0002ca00> { _request_irq + 0x98 }

     Source : <0x0002c9f8> { _request_irq + 0x90 } IF CC JUMP

  14 Target : <0x0002c9f4> { _request_irq + 0x8c }

     Source : <0x0002c782> { ___setup_irq + 0x1a } RTS

  15 Target : <0x0002c77a> { ___setup_irq + 0x12 }

     Source : <0x0002c834> { ___setup_irq + 0xcc } JUMP.S

BUG: failure at drivers/bluetooth/bluecard_cs.c:552/bluecard_interrupt()!

Kernel panic - not syncing: BUG!

--

 

Follow-ups

 

--- Sonic Zhang                                              2009-07-21 03:30:24

This bug is root caused to be the same bug in CPLD logic of the CF/IDE/NAND

add-on card. The interrupt out PIN of CPLD is set high by default rather than

correct tristat.

 

 

--- Michael Hennerich                                        2009-07-21 06:08:54

 

 

This bug is caused by the CONFIG_DEBUG_SHIRQ option being enabled.

The bluecard_cs card service driver is not prepared for spurious

interrupts caused by CONFIG_DEBUG_SHIRQ.

 

So the bluecard_cs card service driver needs to be fixed.

Return IRQ_NONE instead of BUG_ON().

-Michael

 

 

--- Sonic Zhang                                              2009-07-21 23:55:10

Fixed

 

--- Vivi Li                                                  2009-07-22 05:22:27

It can boot without crash now.

Close this bug.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

config.bluetoothcf    application/octet-stream    32228    Vivi Li

Attachments

Outcomes