i can reproduce this daily using flowtable on a wifi enabled PC on -HEAD.
-adrian
On 12 January 2017 at 06:13, Jakub Palider wrote:
> An update: eventually, FLOWTABLE option also resulted in crash with
> __rw_lock_hard on FreeBSD release/11.0.0 (also on VM).
> This time, however, the backtrace
An update: eventually, FLOWTABLE option also resulted in crash with
__rw_lock_hard on FreeBSD release/11.0.0 (also on VM).
This time, however, the backtrace was different, instead of
tcp_output->ip_output->ether_output() chain, it happened in
flowtable_clean_vnet()
On Wed, Jan 11, 2017 at 10:42 AM
On Tue, 29 Nov 2016 11:05:09 -0800
Gleb Smirnoff wrote:
> On Mon, Nov 28, 2016 at 02:10:33PM -0800, hiren panchasara wrote:
> h> > Hi,
> h> > I have found that last month (19 Oct) the problem appeared on this list,
> h> > and to my experience it persists, both on VM and bare metal installation
>
On Mon, Nov 28, 2016 at 02:10:33PM -0800, hiren panchasara wrote:
h> > Hi,
h> > I have found that last month (19 Oct) the problem appeared on this list,
h> > and to my experience it persists, both on VM and bare metal installation
h> > (HEAD from yesterday). I looks that enabling FLOWTABLE option i
+ Mike and Gleb who may provide some help/pointers.
On 11/25/16 at 04:33P, Jakub Palider wrote:
> Hi,
> I have found that last month (19 Oct) the problem appeared on this list,
> and to my experience it persists, both on VM and bare metal installation
> (HEAD from yesterday). I looks that enabling
