Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
On Fri, Jan 31, 2014 at 10:18 AM, Thomas Glanzmann wrote: >> Do you know if this happens with an older kernel or with a simpler topology? > > No, I don't. I just verified that the Ubuntu Mininet uses the > openvswitch kernel module from openvswitch and not the one that is > shipped with the kernel. Ubuntu precise does not crash with the exact same > topology. The kernel from Precise doesn't call the function that is triggering the problem, so it's not too surprising that it doesn't have the same issue. It's not clear that this is actually a bug in the OVS code since it happens in a different function and that function accesses data that OVS doesn't really touch. Do you know if this happens with the bridge? Or can you try bisecting? Or use gdb to track down the faulting address? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
On Fri, Jan 31, 2014 at 10:18 AM, Thomas Glanzmann tho...@glanzmann.de wrote: Do you know if this happens with an older kernel or with a simpler topology? No, I don't. I just verified that the Ubuntu Mininet uses the openvswitch kernel module from openvswitch and not the one that is shipped with the kernel. Ubuntu precise does not crash with the exact same topology. The kernel from Precise doesn't call the function that is triggering the problem, so it's not too surprising that it doesn't have the same issue. It's not clear that this is actually a bug in the OVS code since it happens in a different function and that function accesses data that OVS doesn't really touch. Do you know if this happens with the bridge? Or can you try bisecting? Or use gdb to track down the faulting address? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
Hello Jesse,
> Do you know what type of devices are being attached to OVS (i.e. tap,
> veth, etc.)?
my e-mail has a link to the debug log which contains that Information.
But from my understanding there are several tap devices: one per host,
4-5 per switch. Tap because it needs layer 2.
There are the last commands that are issued before it crashes:
*** Starting controller
*** Starting 4 switches
s1 *** s1 : ('ifconfig lo up',)
*** s1 : ('ovs-vsctl del-br', )
*** s1 : ('ovs-vsctl add-br', )
*** s1 : ('ovs-vsctl -- set Bridge', ,
'other_config:datapath-id=0001')
*** s1 : ('ovs-vsctl set-fail-mode', ,
'secure')
*** s1 : ('ovs-vsctl add-port', ,
)
and than it hangs. I think the last add-port command triggers it.
> Do you know if this happens with an older kernel or with a simpler topology?
No, I don't. I just verified that the Ubuntu Mininet uses the
openvswitch kernel module from openvswitch and not the one that is
shipped with the kernel. Ubuntu precise does not crash with the exact same
topology.
(ubuntu) [~] modinfo openvswitch
filename:
/lib/modules/3.2.0-58-generic/updates/dkms/openvswitch.ko
license:GPL
description:Open vSwitch switching datapath
srcversion: 7CBEB285B79D96D51E0C633
depends:
vermagic: 3.2.0-58-generic SMP mod_unload modversions
Cheers,
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
On Thu, Jan 30, 2014 at 6:33 PM, Thomas Glanzmann wrote: > Hello Jesse, > >> This looks like the kernel module included with upstream Linux instead >> of from OVS git, is that correct? > > coorect. > >> Can you please describe what you are doing instead of just giving your >> script? > > I created 8 hosts. 2 hosts are connected two each switches. That gives > me 4 switches which are connected using a ring topology. The reason for > that is that I want to test the Layer2, Layer3 IPv4 and IPv6 > capabilities of OpenDayLight. Do you know what type of devices are being attached to OVS (i.e. tap, veth, etc.)? Do you know if this happens with an older kernel or with a simpler topology? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
On Thu, Jan 30, 2014 at 6:33 PM, Thomas Glanzmann tho...@glanzmann.de wrote: Hello Jesse, This looks like the kernel module included with upstream Linux instead of from OVS git, is that correct? coorect. Can you please describe what you are doing instead of just giving your script? I created 8 hosts. 2 hosts are connected two each switches. That gives me 4 switches which are connected using a ring topology. The reason for that is that I want to test the Layer2, Layer3 IPv4 and IPv6 capabilities of OpenDayLight. Do you know what type of devices are being attached to OVS (i.e. tap, veth, etc.)? Do you know if this happens with an older kernel or with a simpler topology? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
Hello Jesse,
Do you know what type of devices are being attached to OVS (i.e. tap,
veth, etc.)?
my e-mail has a link to the debug log which contains that Information.
But from my understanding there are several tap devices: one per host,
4-5 per switch. Tap because it needs layer 2.
There are the last commands that are issued before it crashes:
*** Starting controller
*** Starting 4 switches
s1 *** s1 : ('ifconfig lo up',)
*** s1 : ('ovs-vsctl del-br', OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694 )
*** s1 : ('ovs-vsctl add-br', OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694 )
*** s1 : ('ovs-vsctl -- set Bridge', OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694 ,
'other_config:datapath-id=0001')
*** s1 : ('ovs-vsctl set-fail-mode', OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694 ,
'secure')
*** s1 : ('ovs-vsctl add-port', OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694 ,
Intf s1-eth1)
and than it hangs. I think the last add-port command triggers it.
Do you know if this happens with an older kernel or with a simpler topology?
No, I don't. I just verified that the Ubuntu Mininet uses the
openvswitch kernel module from openvswitch and not the one that is
shipped with the kernel. Ubuntu precise does not crash with the exact same
topology.
(ubuntu) [~] modinfo openvswitch
filename:
/lib/modules/3.2.0-58-generic/updates/dkms/openvswitch.ko
license:GPL
description:Open vSwitch switching datapath
srcversion: 7CBEB285B79D96D51E0C633
depends:
vermagic: 3.2.0-58-generic SMP mod_unload modversions
Cheers,
Thomas
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
Hello Jesse, > This looks like the kernel module included with upstream Linux instead > of from OVS git, is that correct? coorect. > Can you please describe what you are doing instead of just giving your script? I created 8 hosts. 2 hosts are connected two each switches. That gives me 4 switches which are connected using a ring topology. The reason for that is that I want to test the Layer2, Layer3 IPv4 and IPv6 capabilities of OpenDayLight. Cheers, Thomas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
On Thu, Jan 30, 2014 at 12:44 PM, Thomas Glanzmann wrote: > Hello, > open vswitch git head with Linus tip OOPses for me reproducable when I > load the following mininet topology: This looks like the kernel module included with upstream Linux instead of from OVS git, is that correct? Can you please describe what you are doing instead of just giving your script? It would also be helpful if you could use GDB to find out the source of the faulting address. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
On Thu, Jan 30, 2014 at 12:44 PM, Thomas Glanzmann tho...@glanzmann.de wrote: Hello, open vswitch git head with Linus tip OOPses for me reproducable when I load the following mininet topology: This looks like the kernel module included with upstream Linux instead of from OVS git, is that correct? Can you please describe what you are doing instead of just giving your script? It would also be helpful if you could use GDB to find out the source of the faulting address. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
Hello Jesse, This looks like the kernel module included with upstream Linux instead of from OVS git, is that correct? coorect. Can you please describe what you are doing instead of just giving your script? I created 8 hosts. 2 hosts are connected two each switches. That gives me 4 switches which are connected using a ring topology. The reason for that is that I want to test the Layer2, Layer3 IPv4 and IPv6 capabilities of OpenDayLight. Cheers, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
