2009-11-11 02:03:24     Problem related with PPPoE

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

2009-11-11 02:03:24     Problem related with PPPoE

Bob Liu (CHINA)

Message: 82263   

 

I used uClinux 2007R1.1-RC3 and enable pppoe function. Then running web server on it.

 

But when I try to access a web page larger than 10k through pppoe connection, the kernel locked and print following message.

 

And I found that if I slowed the web server send operation, like sleep for every 512 bytes, it will avoid the lock.

 

Anyone can help?

 

 

 

BUG: soft lockup detected on CPU#0!

Hardware Trace:

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

   Source : <0x00022452> { _softlockup_tick + 0x8a }

1 Target : <0x0002244c> { _softlockup_tick + 0x84 }

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

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

   Source : <0x0000b73e> { _vprintk + 0x2e2 }

3 Target : <0x0000b732> { _vprintk + 0x2d6 }

   Source : <0x0000b6fa> { _vprintk + 0x29e }

4 Target : <0x0000b6f4> { _vprintk + 0x298 }

   Source : <0x0000bb56> { _release_console_sem + 0x232 }

5 Target : <0x0000bb50> { _release_console_sem + 0x22c }

   Source : <0x0000bb40> { _release_console_sem + 0x21c }

6 Target : <0x0000bb22> { _release_console_sem + 0x1fe }

   Source : <0x0000bb14> { _release_console_sem + 0x1f0 }

7 Target : <0x0000bb10> { _release_console_sem + 0x1ec }

   Source : <0x0000bb08> { _release_console_sem + 0x1e4 }

8 Target : <0x0000bb06> { _release_console_sem + 0x1e2 }

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

9 Target : <0x0000bad2> { _release_console_sem + 0x1ae }

   Source : <0x0000b9a8> { _release_console_sem + 0x84 }

10 Target : <0x0000b97e> { _release_console_sem + 0x5a }

   Source : <0x0000bac2> { _release_console_sem + 0x19e }

11 Target : <0x0000babc> { _release_console_sem + 0x198 }

   Source : <0x0000b360> { __call_console_drivers + 0x64 }

12 Target : <0x0000b35a> { __call_console_drivers + 0x5e }

   Source : <0x0000b324> { __call_console_drivers + 0x28 }

13 Target : <0x0000b2fc> { __call_console_drivers + 0x0 }

   Source : <0x0000bab8> { _release_console_sem + 0x194 }

14 Target : <0x0000baaa> { _release_console_sem + 0x186 }

   Source : <0x0000ba8c> { _release_console_sem + 0x168 }

15 Target : <0x0000ba82> { _release_console_sem + 0x15e }

   Source : <0x0000b2fa> { ___call_console_drivers + 0x4e }

Stack from 01157b40:

        00012750 00012750 00133024 01061d60 00000006 000007df 00000000 ffa083ae

        00000000 00000000 00000001 00000000 000226dc 000226dc 00133024 00000000

        00000000 01157b80 0000f3ca 00176074 0002351c 001365b8 00000000 01060be0

        00000000 0000003f ffa084fc ffc00014 ffa084ca ffc00014 01162060 00000000

        00000000 ffa091a0 ffa091a0 fffffff5 000b2cc8 00000006 000d6168 0000f602

        00008050 00000000 00000000 01158000 006c9338 0000f602 000cfbe0 00000006

Call Trace:

[<000cfbe0>] _tcp_sendmsg+0x8bc/0x8ec

[<000cfbe0>] _tcp_sendmsg+0x8bc/0x8ec

[<000acff2>] _sock_sendmsg+0x96/0xb0

[<0001a77c>] _autoremove_wake_function+0x0/0x30

[<000226dc>] _handle_IRQ_event+0x28/0x50

[<0000f3ca>] ___do_softirq+0x4e/0xa0

[<000ad0c4>] _sys_sendto+0xb8/0xdc

[<00008050>] _set_load_weight+0x30/0x68

[<000ad00c>] _sys_sendto+0x0/0xdc

[<000ad0fa>] _sys_send+0x12/0x18

[<0000819e>] _scheduler_tick+0xa/0x294

[<00012766>] _update_process_times+0x46/0x54

[<00011f1c>] _run_timer_softirq+0x14/0x150

[<000ad0fa>] _sys_send+0x12/0x18

[<000ad0e8>] _sys_send+0x0/0x18

[<00008000>] _recalc_task_prio+0x88/0xa8

QuoteReplyEditDelete

 

 

2009-11-11 22:22:42     Re: Problem related with PPPoE

Yi Li (CHINA)

Message: 82280   

 

Bob,

 

Can you update to 2009R1-RC6 release and have a test?

 

I think these isssue may not be related with PPPOE. The "soft lockup" happens when the kernel is busily doing something (e.g handling softirq) for a long time, even a high priority "watchdog" thread cannot be scheduled to run. You can disable CONFIG_DETECT_SOFTLOCKUP to disable soft lockup detection, but it is better to find out where kernel spends so much time.

 

-Yi

Attachments

    Outcomes