Running with dpdk 16.04 and latest ovs from git, and removing "mrg_rxbuf=off"
from virtio params, the crash is no longer observed. However, we are
wittnessing ovs gets stuck, and will post to ovs mailing
list:2016-05-02T17:26:18.804Z|00111|ovs_rcu|WARN|blocked 1000 ms waiting for
pmd145 to
On Tue, Apr 05, 2016 at 08:36:19PM +, Yi Ba wrote:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ff1ddffb700 (LWP 21287)]
> 0x00450da7 in update_secure_len (vec_idx=0x7ff1ddff27f8,
> secure_len=0x7ff1ddff27fc, id=13948, vq=0x7fe7992c8940)
> at
This OVS crash was first sent to openvswitch bug report mailing list, but it
was suggested it is posted to dpdk as crash is in netdev code.
What you did that make the problem appear.
- We have an openstack kilo setup. it has 3 controllers and 3 computes. 1 of
the controllers runs an
3 matches
Mail list logo
