Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-09 Thread Joe Stringer
On 9 January 2017 at 01:25, Pravin Shelar wrote: > On Sun, Jan 8, 2017 at 8:00 PM, Uri Foox wrote: >> >> Hi Pravin, >> >> That's great, thank you! I hope that it gets picked up and backported to >> 3.13 in a new version. Do you know the likelihood of them

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-09 Thread Pravin Shelar
On Sun, Jan 8, 2017 at 8:00 PM, Uri Foox wrote: > > Hi Pravin, > > That's great, thank you! I hope that it gets picked up and backported to 3.13 > in a new version. Do you know the likelihood of them incorporating it or the > timeline that these things generally take? > I am not

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-07 Thread Uri Foox
Hi Pravin, Thanks. Does this mean it is a confirmed bug? How would I be able to get the patch and install it into our environment? Thanks, Uri On Sat, Jan 7, 2017 at 1:01 PM, Pravin Shelar wrote: > Thanks for all investigation. > > On Sat, Jan 7, 2017 at 12:57 AM, Joe

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-07 Thread Pravin Shelar
Thanks for all investigation. On Sat, Jan 7, 2017 at 12:57 AM, Joe Stringer wrote: > > > On 5 January 2017 at 19:24, Uri Foox wrote: >> >> Hey Joe, >> >> Thank you so much for responding! After 10 days of trying to figure this >> out I'm at a loss. >> >>

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-06 Thread Uri Foox
Hey Joe, I agree with you. It dumbfounded us that a single packet could kernel panic a host so easily and in fact made me believe for at least a few days that this was a red herring. The fact that we cannot replicate it and randomly occurs (within a given time period) also makes it impossible

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-06 Thread Joe Stringer
On 6 January 2017 at 11:47, Uri Foox wrote: > Hey Joe, > > I do agree that the patches for the Linux Kernel were not 1:1 with what > our stack trace showed but it was the only thing we remotely found that > explained our issue. Granted, after upgrading the kernel it was clear that

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-06 Thread Joe Stringer
On 5 January 2017 at 19:24, Uri Foox wrote: > Hey Joe, > > Thank you so much for responding! After 10 days of trying to figure this > out I'm at a loss. > > root@node-8:~# modinfo openvswitch > filename: /lib/modules/3.13.0-106-generic/kernel/net/ >

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-05 Thread Uri Foox
Hey Joe, Thank you so much for responding! After 10 days of trying to figure this out I'm at a loss. root@node-8:~# modinfo openvswitch filename: /lib/modules/3.13.0-106-generic/kernel/net/openvswitch/openvswitch.ko license:GPL description:Open vSwitch switching datapath srcversion:

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-05 Thread Joe Stringer
On 5 January 2017 at 17:13, Uri Foox wrote: > Hi, > > Since about 10 days ago, every few hours, one of our 10 compute nodes on > our Openstack cluster kernel panics at the host level kernel panics > (captured through netconsole). The kernel panic is identical across all 10 > nodes

[ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

2017-01-05 Thread Uri Foox
Hi, Since about 10 days ago, every few hours, one of our 10 compute nodes on our Openstack cluster kernel panics at the host level kernel panics (captured through netconsole). The kernel panic is identical across all 10 nodes and happens at random times but at least 1 node kernel panics every