2008-06-19 12:51:27     BUG: soft lockup detected on CPU#0!

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

2008-06-19 12:51:27     BUG: soft lockup detected on CPU#0!

Tinku Jose (INDIA)

Message: 57593   

 

Hi,

 

I was facing a strange problem in the BF533 uClinux. This is observed after i insert a WLAN driver module. (the same code if i try to use it as builtin driver we are not seeing this issue).

 

For most of the network related commands (like ifconfig etc) i am seeing the following error. Also the system recovers after 20-30 sec and can work normally.

 

Please do let me know what can be the potential issue

 

***************************

 

BUG: soft lockup detected on CPU#0!

Hardware Trace:

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

   Source : <0x003249fe> { _softlockup_tick + 0x7e }

1 Target : <0x003249f8> { _softlockup_tick + 0x78 }

   Source : <0x0030b452> { _printk + 0x16 }

2 Target : <0x0030b44e> { _printk + 0x12 }

   Source : <0x0030b2dc> { _vprintk + 0x1b0 }

3 Target : <0x0030b2d0> { _vprintk + 0x1a4 }

   Source : <0x0030b2c2> { _vprintk + 0x196 }

4 Target : <0x0030b2bc> { _vprintk + 0x190 }

   Source : <0x0030b67a> { _release_console_sem + 0x42 }

5 Target : <0x0030b672> { _release_console_sem + 0x3a }

   Source : <0x0030b83a> { _release_console_sem + 0x202 }

6 Target : <0x0030b81a> { _release_console_sem + 0x1e2 }

   Source : <0x0030b80c> { _release_console_sem + 0x1d4 }

7 Target : <0x0030b802> { _release_console_sem + 0x1ca }

   Source : <0x0030b7f4> { _release_console_sem + 0x1bc }

8 Target : <0x0030b7d4> { _release_console_sem + 0x19c }

   Source : <0x0030b6ba> { _release_console_sem + 0x82 }

9 Target : <0x0030b68a> { _release_console_sem + 0x52 }

   Source : <0x0030b7b6> { _release_console_sem + 0x17e }

10 Target : <0x0030b7b0> { _release_console_sem + 0x178 }

   Source : <0x0030affa> { __call_console_drivers + 0x62 }

11 Target : <0x0030aff4> { __call_console_drivers + 0x5c }

   Source : <0x0030afc4> { __call_console_drivers + 0x2c }

12 Target : <0x0030af98> { __call_console_drivers + 0x0 }

   Source : <0x0030b7ac> { _release_console_sem + 0x174 }

13 Target : <0x0030b7a2> { _release_console_sem + 0x16a }

   Source : <0x0030b740> { _release_console_sem + 0x108 }

14 Target : <0x0030b73a> { _release_console_sem + 0x102 }

   Source : <0x0030af94> { ___call_console_drivers + 0x50 }

15 Target : <0x0030af88> { ___call_console_drivers + 0x44 }

   Source : <0x0038ef88> { _bfin_serial_console_write + 0x44 }

Stack from 023afc78:

        0031304e 0031304e 0046e190 02e372e0 00000006 00000043 00000000 ffa0033e

        00000000 00000000 00000001 00468b14 00000000 00324ca0 00432ff8 00000006

        00000000 00000000 0046dfd8 0046df88 0046fa48 00325bc0 004363bc 00000000

        023afe90 023ad000 ffa00482 004715cc 00000003 ffa00458 004715cc 00000003

        023afd0c 0030f210 00000000 ffa01112 ffc00014 006e0e60 00000003 02de400a

        006912a0 00396cd0 00008050 00000000 00000000 023b0000 0228da42 00396cd0

 

 

 

***************************

 

thanks

 

tinku

QuoteReplyEditDelete

 

 

2008-06-19 14:40:30     Re: BUG: soft lockup detected on CPU#0!

Mike Frysinger (UNITED STATES)

Message: 57598   

 

likely some code in the driver is spinning for an inordinate amount of time without scheduling ... if you have JTAG, you can profile where the kernel is spinning during this hang

 

QuoteReplyEditDelete

 

 

2008-06-20 14:19:34     Re: BUG: soft lockup detected on CPU#0!

Tinku Jose (INDIA)

Message: 57641   

 

Hi Mike,

 

Thanks for the info. Infact we did locate the place where it is getting looped.

 

The scenario is as follows.

 

bringup eth0 interface (SMSC 9215)

 

bringdown eth0 interface

 

insert WLAN driver module. this will comeup in eth1

 

bringup eth1 interface (WLAN)

 

after this any ifconfig operation done the code is getting looped in smsc911x_get_stats() function. This is called from dev->get_stats() from the stack.

 

Have anyone faced such as issue. Any pointers on debugging will be very helpful. 

 

thanks

 

tinku

QuoteReplyEditDelete

 

 

2008-10-16 23:45:27     Re: BUG: soft lockup detected on CPU#0!

w w (CHINA)

Message: 63821   

 

hi, tinku

 

What's about the question ?

 

I mat the same question.

QuoteReplyEditDelete

 

 

2008-10-17 12:54:55     Re: BUG: soft lockup detected on CPU#0!

Tinku Jose (INDIA)

Message: 63858   

 

basically there were two issues,

 

1. interrupt mapping/config was improper.

 

2. net register was not handled properly (porting issue from 2.4 to 2.6 kernel)

 

due to this, the response from the H/W was not coming and it was whiling out!!!

Attachments

    Outcomes