On Thu, Jul 16, 2015 at 3:07 PM, Alex Wang <al...@nicira.com> wrote:

> Sorry for this very delayed reply,
>
> I think I found the issue, in branch 2.1.*
>
> Will send out a fix soon,
>
>
Sorry I found my theory was wrong, things seem to be trickier~

Want to know if you have modified the source code?

Also, could you provide backtraces for all other threads?

Thanks,
Alex Wang,




> At the same time, it branch >= 2.3 do not have this issue due to the use of
> ovs-rcu...  And since branch 2.3 is the LTS branch, I would really
> recommend
> you to switch to 2.3+
>
> Thanks,
> Alex Wang,
>
> On Sun, Jul 12, 2015 at 6:31 AM, 马啸 <cumtb_max...@163.com> wrote:
>
>> Hi,all
>>
>> Is anybody know what the problem caused by and how to solve it ?
>>
>> Look forward for your replying.
>>
>>
>>
>>
>>
>>
>> At 2015-07-10 18:32:07, "马啸" <cumtb_max...@163.com> wrote:
>>
>> Hi,all
>>
>> The version is 2.1.2 .   openvswitch-2.1.2-26.el6.x86_64
>>
>> The information as bellow:
>>
>> ========================================================
>> =========================
>>
>> Core was generated by `ovs-vswitchd unix:/var/run/openvswitch/db.sock
>> -vconsole:emer -vsyslog:err -vfi'.
>>
>> Program terminated with signal 6, Aborted.
>>
>> #0  0x00007f78d4073925 in ?? () from /lib64/libc.so.6
>>
>>
>> ………………….
>>
>>
>> Thread 2 (Thread 0x7f78d2067700 (LWP 31449)):
>>
>> #0  0x00007f78d465c40d in aio_suspend (list=0x7f78d20554b8,
>> nent=-771402644, timeout=0x0) at ../sysdeps/pthread/aio_suspend.c:172
>>
>> #1  0x00000000004cea46 in async_append_wait (ap=0xc741a0) at
>> lib/async-append-aio.c:106
>>
>> #2  0x00000000004ceaa8 in async_append_flush (ap=0xc741a0) at
>> lib/async-append-aio.c:161
>>
>> #3  0x00000000004ab618 in vlog_valist (module=0x75c620, level=VLL_EMER,
>> message=0x4fbf88 "%s: assertion %s failed in %s()", args=0x7f78d20555c0) at
>> lib/vlog.c:914
>>
>> #4  0x00000000004ab64b in vlog_abort_valist (module_=<value optimized
>> out>, message=0x4fbf88 "%s: assertion %s failed in %s()",
>> args=0x7f78d20555c0) at lib/vlog.c:991
>>
>> #5  0x00000000004ab6e6 in vlog_abort (module=0x7f78d205546c, message=0x80
>> <Address 0x80 out of bounds>) at lib/vlog.c:1006
>>
>> #6  0x00000000004a7161 in ovs_assert_failure (where=<value optimized
>> out>, function=<value optimized out>, condition=<value optimized out>) at
>> lib/util.c:68
>>
>> #7  0x000000000042a903 in dpif_sflow_ref (ds_=<value optimized out>) at
>> ofproto/ofproto-dpif-sflow.c:342
>>
>> #8  0x000000000042ee8a in xlate_receive (backer=0xd9e420,
>> packet=0x7f7878000900, key=<value optimized out>, key_len=<value optimized
>> out>, flow=0x7f78d2066ad0, fitnessp=0x7f78d2055850,
>>
>>     ofproto=0x7f78d20668a0, ipfix=0x7f78d2066890, sflow=0x7f78d2066898,
>> netflow=0x0, odp_in_port=0x7f78d20668ac) at ofproto/ofproto-dpif-xlate.c:593
>>
>> #9  0x000000000042cf67 in handle_upcalls (handler=<value optimized out>,
>> upcalls=0x7f78d2066bd0) at ofproto/ofproto-dpif-upcall.c:960
>>
>> #10 0x000000000042dad9 in udpif_upcall_handler (arg=0xe7a0a8) at
>> ofproto/ofproto-dpif-upcall.c:680
>>
>> #11 0x00007f78d3e2b9d1 in start_thread (arg=0x7f78d2067700) at
>> pthread_create.c:301
>>
>> #12 0x00007f78d4129b6d in epoll_pwait (epfd=<value optimized out>,
>> events=<value optimized out>, maxevents=<value optimized out>,
>> timeout=<value optimized out>, set=<value optimized out>)
>>
>>     at ../sysdeps/unix/sysv/linux/epoll_pwait.c:50
>>
>> #13 0x0000000000000000 in ?? ()
>>
>> (gdb) t 2
>>
>> [Switching to thread 2 (Thread 0x7f78d2067700 (LWP 31449))]#0
>> 0x00007f78d465c40d in aio_suspend (list=0x7f78d20554b8, nent=-771402644,
>> timeout=0x0) at ../sysdeps/pthread/aio_suspend.c:172
>>
>> 172           AIO_MISC_WAIT (result, cntr, timeout, 1);
>>
>> (gdb) f 6
>>
>> #6  0x00000000004a7161 in ovs_assert_failure (where=<value optimized
>> out>, function=<value optimized out>, condition=<value optimized out>) at
>> lib/util.c:68
>>
>> 68              VLOG_ABORT("%s: assertion %s failed in %s()",
>>
>> (gdb) f 7
>>
>> #7  0x000000000042a903 in dpif_sflow_ref (ds_=<value optimized out>) at
>> ofproto/ofproto-dpif-sflow.c:342
>>
>> 342             ovs_assert(orig > 0);
>>
>> (gdb) p orig
>>
>> $1 = 0
>>
>> (gdb)
>> ========================================================
>> =========================
>>
>> Thanks!
>>
>>
>>
>>
>> At 2015-07-10 11:54:00, "Jesse Gross" <je...@nicira.com> wrote:
>> >This could be related to b953042214201e2693a485a8ba8b19f69e5bdf34
>> >("datapath: simplify sample action implementation"). I would check
>> >that you are using OVS 2.3.2 for anything related to sampling.
>> >
>> >On Thu, Jul 9, 2015 at 8:43 PM, Alex Wang <al...@nicira.com> wrote:
>> >> Hey,
>> >>
>> >> Could you send the core dump info (did not see any attachment)?  I assume
>> >> you
>> >> mean the gdb printout showing what causes the crash.  Also, could you
>> >> provide
>> >> the ovs version you are using?
>> >>
>> >> I'm trying to debug an ipfix related crash, could we related,
>> >>
>> >> Thanks, 谢谢,
>> >> Alex Wang,
>> >>
>> >> On Thu, Jul 9, 2015 at 8:01 PM, 马啸 <cumtb_max...@163.com> wrote:
>> >>
>> >>> Hi,all
>> >>>
>> >>>
>> >>>   I am one engineer from UnitedStack, one OpenStack Provider.
>> >>>   We are using OpenvSwitch as the software-switch in OpenStack Compute 
>> >>> and
>> >>> Network Node, and we enabled sflow to monitor the traffic.
>> >>>  And one crash happened. The core-dump information is attached, could
>> >>> anybody help us to solve the problem?
>> >>>
>> >>>
>> >>>   Thanks.
>> >>> _______________________________________________
>> >>> dev mailing list
>> >>> dev@openvswitch.org
>> >>> http://openvswitch.org/mailman/listinfo/dev
>> >>>
>> >> _______________________________________________
>> >> dev mailing list
>> >> dev@openvswitch.org
>> >> http://openvswitch.org/mailman/listinfo/dev
>>
>>
>>
>>
>>
>>
>
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to