[#4278] In 08r1 branch, when ping/telnet/ftp to BF533-EZKIT, xenomai kernel shows warning messages

Submitted By: Vivi Li

Open Date

2008-07-25 03:18:22 Close Date

2009-04-20 04:35:08

Priority:

Medium Assignee:

Yi Li

Status:

Closed Fixed In Release:

N/A

Found In Release:

2008R1.5-RC3 Release:

Category:

N/A Board:

N/A

Processor:

BF533 Silicon Revision:

Is this bug repeatable?:

Yes Resolution:

Assigned (Not Start)

Uboot version or rev.:

Toolchain version or rev.:

08r1.5-13

App binary format:

N/A

Summary: In 08r1 branch, when ping/telnet/ftp to BF533-EZKIT, xenomai kernel shows warning messages

Details:

In 08r1 branch, the first time to ping/telnet/ftp to BF533-EZKIT, xenomai kernel will give following messages:

Linux version 2.6.22.19-ADI-2008R1.5-svn5045 (test@uclinux46-bf533ezkit) (gcc version 4.1.2 (ADI sv8

Hardware Trace Active and Enabled

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

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: 594 MHz core clock and 118 MHz System Clock

Board Memory: 32MB

Kernel Managed Memory: 32MB

Memory map:

text = 0x00001000-0x0011f170

rodata = 0x00120000-0x0016ad60

data = 0x0016b000-0x0017c000

stack = 0x0016c000-0x0016e000

init = 0x0017c000-0x0049b000

bss = 0x0049b000-0x004c56d0

available = 0x004c56d0-0x01eff000

DMA Zone = 0x01f00000-0x02000000

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists. Total pages: 7874

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

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 128 (order: 7, 512 bytes)

I-pipe 1.7-00: pipeline enabled.

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

Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)

Memory available: 26556k/32768k RAM, (3196k init code, 1144k kernel code, 541k data, 1024k dma, 308)

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

Security Framework v1.0.0 initialized

Mount-cache hash table entries: 512

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: 1024 (order: 1, 8192 bytes)

TCP bind hash table entries: 1024 (order: 0, 4096 bytes)

TCP: Hash tables configured (established 1024 bind 1024)

TCP reno registered

I-pipe: Domain Xenomai registered.

Xenomai: hal/blackfin started.

Xenomai: real-time nucleus v2.4.0 (Bells Of Lal) loaded.

Xenomai: starting default API services.

Xenomai: starting POSIX services.

Xenomai: starting RTDM services.

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

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

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 Contoller Driver, Version 1.0, regs_base@ffc00500, 5

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

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 2004-05-31 22:31:25 (1086042685)

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: 3196k freed

dma_alloc_init: dma_page @ 0x00498000 - 256 pages at 0x01f00000

eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1

_____________________________________

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.4.1 (2008-07-24 16:24:17 CST) Built-in shell (msh)

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

root:/>

(Ping from local PC to BF533-EZKIT)

root:/> WARNING: at kernel/softirq.c:138 local_bh_enable()

Hardware Trace:

0 Target : <0x00004888> { _dump_stack + 0x0 }

Source : <0x00012eb0> { _local_bh_enable + 0x8c }

1 Target : <0x00012eb0> { _local_bh_enable + 0x8c }

Source : <0x0000e506> { _printk + 0x5a }

2 Target : <0x0000e4fc> { _printk + 0x50 }

Source : <0x0000e380> { _vprintk + 0x1d4 }

3 Target : <0x0000e374> { _vprintk + 0x1c8 }

Source : <0x0002c9e6> { ___ipipe_restore_root + 0x46 }

4 Target : <0x0002c9a0> { ___ipipe_restore_root + 0x0 }

Source : <0x0000e370> { _vprintk + 0x1c4 }

5 Target : <0x0000e36e> { _vprintk + 0x1c2 }

Source : <0x0000e1a6> { _wake_up_klogd + 0x36 }

6 Target : <0x0000e1a2> { _wake_up_klogd + 0x32 }

Source : <0x0002c9e6> { ___ipipe_restore_root + 0x46 }

7 Target : <0x0002c9a0> { ___ipipe_restore_root + 0x0 }

Source : <0x0000b2ec> { ___wake_up + 0x4c }

8 Target : <0x0000b2e2> { ___wake_up + 0x42 }

Source : <0x0000a1fa> { ___wake_up_common + 0x52 }

9 Target : <0x0000a1ec> { ___wake_up_common + 0x44 }

Source : <0x0000a1e2> { ___wake_up_common + 0x3a }

10 Target : <0x0000a1dc> { ___wake_up_common + 0x34 }

Source : <0x0001ec48> { _autoremove_wake_function + 0x2c }

11 Target : <0x0001ec2e> { _autoremove_wake_function + 0x12 }

Source : <0x0000b004> { _try_to_wake_up + 0x40 }

12 Target : <0x0000affc> { _try_to_wake_up + 0x38 }

Source : <0x0002c9e6> { ___ipipe_restore_root + 0x46 }

13 Target : <0x0002c9a0> { ___ipipe_restore_root + 0x0 }

Source : <0x0000aff8> { _try_to_wake_up + 0x34 }

14 Target : <0x0000aff2> { _try_to_wake_up + 0x2e }

Source : <0x0000b098> { _try_to_wake_up + 0xd4 }

15 Target : <0x0000b096> { _try_to_wake_up + 0xd2 }

Source : <0x0000b074> { _try_to_wake_up + 0xb0 }

Stack from 019c1e70:

004a5cc8 00012eb4 004a5cc8 00000000 000d97b8 0014aafc 0000008a 00120c8c

000d970c 019af800 ae04640a 019af800 3204640a 00106f80 019e2f00 00482820

01abd960 00015dbc 0001be80 00171c28 019af800 3204640a 00000000 019af930

00000000 000ddf74 00482820 01abd960 00171c28 00000003 00000000 00000100

0017341c 019c1f30 000158f4 004a5ec0 000159f8 004a5ec0 019c1f28 000dde40

00482820 019c0000 004a7aa0 00000017 00172b5c 00000000 019c1f28 019c1f28

Call Trace:

[<00012abc>] ___do_softirq+0x60/0xc4

[<000089f0>] _do_irqd+0xc0/0x138

[<00008a38>] _do_irqd+0x108/0x138

[<0001e9f8>] _kthread+0x50/0x64

[<00008930>] _do_irqd+0x0/0x138

[<00001686>] _kernel_thread_helper+0x6/0xc

Follow-ups

--- Yi Li 2008-07-28 02:29:52

Tested on BF537-STAMP. The warning not happen.

This warning comes out from:

void local_bh_enable(void)

{

WARN_ON_ONCE(irqs_disabled());

[snip]

Kernel will output warning when it finds IRQ is disabled before it execute

pending softirq.

--- Yi Li 2008-07-28 03:23:36

Tested on BF533-ezkit, this bug can be reproduced.

--- Yi Li 2008-07-29 07:10:03

This should be a bug - softirq must not be executed when IRQ is disabled.

--- Yi Li 2008-07-29 07:12:30

It is also reproducible on BF533-STAMP. But has not idea how to fix it.

--- Yi Li 2009-01-08 05:38:32

Will re-test this bug in 2009R1 release. Leave it open.

--- Yi Li 2009-03-18 02:22:50

Seems this bug has disappear on pre-2009R1 svn trunk kernel, with

xenomai-2.4.7.

Verifed on BF533-EZKIT 1.6, chip rev. 0.3.

Linux version 2.6.28.7-ADI-2009R1-pre-svn6200 (adam@adam-desktop) (gcc version

4.1.2 (ADI svn)) #6 Wed Mar 18 14:06:54 CST 2009.

--- Vivi Li 2009-04-20 04:35:08

Now it's OK on 09r1, so close it.

Files

Changes

Commits

Dependencies

Duplicates

Associations

Partner Forums

Partner Libraries

[#4278] In 08r1 branch, when ping/telnet/ftp to BF533-EZKIT, xenomai kernel shows warning messages