Monthly ping :). We're ready to test if there's a potential fix.
Thanks in advance, Laurent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi again,
Was the information presented sufficient for reproducing the issue?
Thanks for your time,
Laurent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Wed, 8 Oct 2014 13:02:42 -0700 Ben Pfaff b...@nicira.com wrote:
I can't reproduce this problem with OVS master and upstream kernel
3.16, or with OVS branch-2.3 on the commit from which the Debian
packages were made. Now I'm downloading a Debian ISO so that I can
try it with the exact
On Mon, Oct 13, 2014 at 10:47:19AM +0200, Laurent GUERBY wrote:
On Wed, 8 Oct 2014 13:02:42 -0700 Ben Pfaff b...@nicira.com wrote:
I can't reproduce this problem with OVS master and upstream kernel
3.16, or with OVS branch-2.3 on the commit from which the Debian
packages were made. Now I'm
When I was testing this with 3.17 I had seen similar errors. It was because
the kernel module loaded was the one that came with 3.17 kernel and not the
one I compiled with the latest ovs. I remember they get installed in
different locations. Could you pl check your /lib/modules directory and
make
On Wed, Oct 08, 2014 at 08:20:25AM -0700, Madhu Challa wrote:
When I was testing this with 3.17 I had seen similar errors. It was because
the kernel module loaded was the one that came with 3.17 kernel and not the
one I compiled with the latest ovs. I remember they get installed in
different
I can't reproduce this problem with OVS master and upstream kernel
3.16, or with OVS branch-2.3 on the commit from which the Debian
packages were made. Now I'm downloading a Debian ISO so that I can
try it with the exact kernel and OVS packaging against which the bug
was reported.
--
To
7 matches
Mail list logo
