commit 61e22e8b500afd8b03f32441398c8cebcf7cbb11

Author: Anthony Minessale <anthm@freeswitch.org>

Date: Tue Apr 22 23:25:34 2014 +0500

FS-6476 --resolve

On Apr 25, 2014, at 10:47 AM, rockxsj <rockxsj@gmail.com> wrote:

Not today,but yestoday!Could you check the code about the ws?

于 2014年04月25日 05:03, Michael Jerris 写道:

is this the same with the most recent git master from today?

On Apr 24, 2014, at 9:28 PM, rockxsj <rockxsj@gmail.com> wrote:

I found that the socket have already closed! Should the code must check the socket status? And when the socket is closed,it should stop retry and return a error.

于 2014年04月24日 12:31, Michael Jerris 写道:

can you get it stuck in this state, get a gcore of the process in the stuck state, and file a jira with a thread apply all bt full from this core file?

On Apr 24, 2014, at 10:08 AM, rockxsj <rockxsj@gmail.com> wrote:

I have try the master code,and the bug is still there.What should I do?

于 2014年04月23日 14:13, Michael Jerris 写道:

Have you tried this with more recent git master code? we fixed a block in the secure websocket code a few weeks back.

On Apr 23, 2014, at 8:34 AM, rockxsj <rockxsj@gmail.com> wrote:

I use sipml5 call to freeswitch, the most time it work well.But sometimes if too many calls at a time, it did not work. When I capture package on client and server, I found that my client cannot recive package from the server.The below message is the cpu info when I cannot call, and I found the server can not send data to the socket.

BUG: soft lockup - CPU#14 stuck for 60s! [freeswitch:10399]
CPU 14:
Modules linked in: be2iscsi ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp bnx2i cnic ipv6 xfrm_nalgo crypto_api uio cxgb3i libcxgbi cxgb3 8021q libiscsi_tcp libiscsi2 scsi_transport_iscsi2 scsi_transport_iscsi dm_mirror dm_multipath scsi_dh video backlight sbs power_meter hwmon i2c_ec i2c_core dell_wmi wmi button battery asus_acpi acpi_memhotplug ac parport_pc lp parport joydev sr_mod cdrom sg tpm_tis tg3 tpm tpm_bios pcspkr dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache ahci libata shpchp megaraid_sas sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 10399, comm: freeswitch Not tainted 2.6.18-348.el5 #1
RIP: 0033:[<0000003d26c0d55b>] [<0000003d26c0d55b>]
RSP: 002b:00002b87166103d8 EFLAGS: 00000246
RAX: 0000000000000002 RBX: 0000000000000004 RCX: 0000003d26c0e021
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 00002b8716612000 R08: 00002b8716611940 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000003303 R14: 00002b8716610480 R15: 0000000000000004
FS: 00002b8716611940(0000) GS:ffff810107ba9cc0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002b877542b000 CR3: 00000002aba9c000 CR4: 00000000000006a0

Call Trace:

When it send failure,it will re-try,the below picture is the screenshot of capture pacakte.

http://yazi.whoknow.me/wp-content/uploads/2014/04/cpuinfo.jpg

Somebody can help me? Is there some wrong with webrtc support?