[microblaze-uclinux] BUG when completing commands

[ggastebois@xxxxxxxxxx]

Hello,

I run Petalinux 0.20 on a spartan 3e500
starter kit rev D from reference design (just modified memory interface
config for 64MB).

when typing TAB for name completion
I often have this BUG :

BUG: scheduling while atomic: sh/0xfff70000/63

Stack:
  23cfde80 00000004 23cfe00c 00000059
23cd3134 22001c84 221bacd0 22633b54
  fff70000 0000003f 00989680 00000012
23cfc000 00000008 23cce344 23cfe178
  00000004 23cfe00c 00000059 23cd3134
22620000 00000002 00000000 0000000b
Call Trace:
[<22001c84>] ret_from_intr+0x1c/0x40

I also have a test script on a jffs2
flash filesystem :

#!/bin/sh
I=0
J=0
while [ $J -le 255 ]
        do
        while [
$I -le 255 ]
           
    do
           
    gpio-test -o $I
           
    I=`expr $I + 1`
           
    done
        I=255
        while [
$I -ne 0 ]
           
    do
           
    gpio-test -o $I
           
    I=`expr $I - 1`
           
    done
        I=0
        done

which produce BUG to :
BUG: scheduling while atomic: toto/0x221e9dfc/54

Stack:
  226fe350 000000c4 00001000 225fe000
00000003 22001c84 221bacd0 23de9430
  221e9dfc 00000036 22224070 0000000a
226fe000 00000008 226fe460 225fe014
  000000c4 00001000 225fe000 00000003
226fe460 00000010 23c60aa0 00000000
Call Trace:
[<22001c84>] ret_from_intr+0x1c/0x40
[<2210d168>] uart_console_write+0x3c/0x90
[<2210e37c>] ulite_console_write+0x58/0x9c
[<2210d168>] uart_console_write+0x3c/0x90
[<2210d168>] uart_console_write+0x3c/0x90
[<22008e28>] __call_console_drivers+0x64/0x88
[<2210e37c>] ulite_console_write+0x58/0x9c
[<2210e37c>] ulite_console_write+0x58/0x9c
[<22008e28>] __call_console_drivers+0x64/0x88
[<22008e28>] __call_console_drivers+0x64/0x88
[<220091f4>] release_console_sem+0xf8/0x28c
[<22008ee4>] _call_console_drivers+0x98/0xb0
[<220f77c0>] vscnprintf+0xc/0x38
[<220f7500>] vsnprintf+0x37c/0x630
[<2210d168>] uart_console_write+0x3c/0x90
[<220091f4>] release_console_sem+0xf8/0x28c
[<2210e37c>] ulite_console_write+0x58/0x9c
[<22009564>] vprintk+0x1b8/0x398
[<22009408>] vprintk+0x5c/0x398
[<22009564>] vprintk+0x1b8/0x398
[<2210d168>] uart_console_write+0x3c/0x90
[<22008e28>] __call_console_drivers+0x64/0x88
[<22009764>] printk+0x20/0x34
[<2210e37c>] ulite_console_write+0x58/0x9c
[<22008ee4>] _call_console_drivers+0x98/0xb0
[<22008e28>] __call_console_drivers+0x64/0x88
[<220091f4>] release_console_sem+0xf8/0x28c
[<22008ee4>] _call_console_drivers+0x98/0xb0
[<22009564>] vprintk+0x1b8/0x398
[<220f77c0>] vscnprintf+0xc/0x38
[<220f7500>] vsnprintf+0x37c/0x630
[<22024230>] __print_symbol+0x9c/0xec
[<220091f4>] release_console_sem+0xf8/0x28c
[<22009564>] vprintk+0x1b8/0x398
[<22009408>] vprintk+0x5c/0x398
[<22009764>] printk+0x20/0x34
[<220f78b8>] sprintf+0x28/0x3c
[<22024230>] __print_symbol+0x9c/0xec
[<22001c60>] _interrupt+0x110/0x118
[<22001c60>] _interrupt+0x110/0x118
[<22024230>] __print_symbol+0x9c/0xec
[<22000dac>] show_trace+0x94/0xc4
[<2210d168>] uart_console_write+0x3c/0x90
[<2210e37c>] ulite_console_write+0x58/0x9c
[<22012680>] update_process_times+0x68/0xa4
[<22008e28>] __call_console_drivers+0x64/0x88
[<220053e4>] scheduler_tick+0x18/0xa8
[<22001728>] do_IRQ+0x40/0x54
[<22012680>] update_process_times+0x68/0xa4
[<22001728>] do_IRQ+0x40/0x54
[<22012680>] update_process_times+0x68/0xa4
[<220053e4>] scheduler_tick+0x18/0xa8
[<22001aa8>] timer_interrupt+0x6c/0x98
[<22024d94>] handle_IRQ_event+0x50/0xb0
[<22024f00>] __do_IRQ+0x10c/0x12c
[<2200e320>] do_softirq+0x44/0x54
[<22024e88>] __do_IRQ+0x94/0x12c
[<2200171c>] do_IRQ+0x34/0x54
[<22001728>] do_IRQ+0x40/0x54
[<22001c60>] _interrupt+0x110/0x118

and sometimes freeze the card after
some bugs.

What's this problem ?

Thank you

Guillaume Gastebois
-------------------------------------------
IN-SNEC
02 31 29 48 88
2 rue de Caen
14 740 Bretteville l'orgueilleuse
-------------------------------------------