All of these stack traces seem completely different to me (and some don't even involve OVS) so it's pretty difficult to tell what's going on. However, if I had to guess, I suspect that you have a loop with your GRE configuration.
On Tue, Nov 19, 2013 at 12:17 AM, nicolas prochazka <prochazka.nico...@gmail.com> wrote: > hello, > It's 100% reproductible on physical server ( dell , network card > driver bnx2 ) , with a virtual vm i can't reproducte it. > it's near this description : > http://permalink.gmane.org/gmane.linux.network/269580 > > More information : > GRE tunnel are active but huge traffic is on standard port (not gre) > two poor screenshot of kernel panic > https://drive.google.com/file/d/0B7ff7G-ktDxjRkMwaHBXbDV1VjA/edit?usp=sharing > https://drive.google.com/file/d/0B7ff7G-ktDxjdjlBRE5UNFZldWs/edit?usp=sharing > > Regards, > Nicolas Prochazka. > > 2013/11/18 Jesse Gross <je...@nicira.com>: >> On Mon, Nov 18, 2013 at 10:15 AM, nicolas prochazka >> <prochazka.nico...@gmail.com> wrote: >>> Hello, >>> >>> my configuration : >>> kernel 3.11.8 + with openvswitch kernel module, and gre kernel >>> openvswitch 2.0.0 >>> >>> Test : >>> When i do GRE over IPSEC ( strongswan on neoEtap interface ) >>> a kernel panic occur when high traffic is done >>> - in cpuacct_charge >>> or >>> - xfrm_output >> >> Can you please post some kind of backtrace or screenshot? Also, >> whether this is 100% reproducible, if it happens in other situations, >> etc.? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
