On Wed, Mar 04, 2015 at 03:56:41PM -0500, Xu (Simon) Chen wrote:
> Now I think about it... Maybe I run into this problem because I turned on
> Sflow collection on my OVS nodes...
Yes, I was also running sflow collection. I think the bug will only bite
when doing sflow collection because it's the s
On Wed, Mar 4, 2015 at 6:16 AM, Chris Dunlop wrote:
> On Sat, Feb 28, 2015 at 12:49:31PM +1100, Chris Dunlop wrote:
>> On Fri, Feb 27, 2015 at 08:30:42PM -0500, Xu (Simon) Chen wrote:
>> > On Fri, Feb 27, 2015 at 6:14 PM, Pravin Shelar wrote:
>> > > So it looks like vhost is generating shared skb
On Sat, Feb 28, 2015 at 12:49:31PM +1100, Chris Dunlop wrote:
> On Fri, Feb 27, 2015 at 08:30:42PM -0500, Xu (Simon) Chen wrote:
> > On Fri, Feb 27, 2015 at 6:14 PM, Pravin Shelar wrote:
> > > So it looks like vhost is generating shared skb. Can you try same test
> > > on latest upstream kernel?
>
On Fri, Feb 27, 2015 at 08:33:13PM -0500, Xu (Simon) Chen wrote:
> On Fri, Feb 27, 2015 at 7:13 PM, Chris Dunlop wrote:
> > On Fri, Feb 27, 2015 at 11:08:21AM -0800, Pravin Shelar wrote:
> > > Can you reproduce this bug on hypervisor to hypervisor
> > > test without any VMs?
> >
> > The thought ju
On Fri, Feb 27, 2015 at 08:31:46PM -0500, Xu (Simon) Chen wrote:
> On Fri, Feb 27, 2015 at 6:49 PM, Chris Dunlop wrote:
> > On Fri, Feb 27, 2015 at 06:06:25PM -0500, Xu (Simon) Chen wrote:
> > > On Friday, February 27, 2015, Chris Dunlop wrote:
> > > > Simon, are you able to try your test running
On Fri, Feb 27, 2015 at 08:30:42PM -0500, Xu (Simon) Chen wrote:
> On Fri, Feb 27, 2015 at 6:14 PM, Pravin Shelar wrote:
> > So it looks like vhost is generating shared skb. Can you try same test
> > on latest upstream kernel?
>
> I don't know whether it's vhost, as for me the VM receiving high v
On Fri, Feb 27, 2015 at 7:13 PM, Chris Dunlop wrote:
> On Fri, Feb 27, 2015 at 11:08:21AM -0800, Pravin Shelar wrote:
> > On Thu, Feb 26, 2015 at 9:13 PM, Chris Dunlop
> wrote:
> > > Hi,
> > >
> > > "Me too" on Simon's BUG() described below (apologies for the top post).
> > > Basically:
> > >
>
On Fri, Feb 27, 2015 at 6:49 PM, Chris Dunlop wrote:
> On Fri, Feb 27, 2015 at 06:06:25PM -0500, Xu (Simon) Chen wrote:
> > On Friday, February 27, 2015, Chris Dunlop wrote:
> > > Simon, are you able to try your test running direct hypervisor
> > > to hypervisor?
> >
> > Nope... I have only see
On Fri, Feb 27, 2015 at 6:14 PM, Pravin Shelar wrote:
> On Fri, Feb 27, 2015 at 3:06 PM, Xu (Simon) Chen
> wrote:
> >
> >
> > On Friday, February 27, 2015, Chris Dunlop wrote:
> >>
> >> On Fri, Feb 27, 2015 at 11:08:21AM -0800, Pravin Shelar wrote:
> >> > On Thu, Feb 26, 2015 at 9:13 PM, Chris
On Fri, Feb 27, 2015 at 11:08:21AM -0800, Pravin Shelar wrote:
> On Thu, Feb 26, 2015 at 9:13 PM, Chris Dunlop wrote:
> > Hi,
> >
> > "Me too" on Simon's BUG() described below (apologies for the top post).
> > Basically:
> >
> > [ 7318.409796] kernel BUG at net/core/skbuff.c:1041!
> > ...
> > [ 73
On Fri, Feb 27, 2015 at 06:06:25PM -0500, Xu (Simon) Chen wrote:
> On Friday, February 27, 2015, Chris Dunlop wrote:
> > Simon, are you able to try your test running direct hypervisor
> > to hypervisor?
>
> Nope... I have only seen this between VMs. After repeated tests, it has
> got worse that
On Fri, Feb 27, 2015 at 3:06 PM, Xu (Simon) Chen wrote:
>
>
> On Friday, February 27, 2015, Chris Dunlop wrote:
>>
>> On Fri, Feb 27, 2015 at 11:08:21AM -0800, Pravin Shelar wrote:
>> > On Thu, Feb 26, 2015 at 9:13 PM, Chris Dunlop
>> > wrote:
>> > > Hi,
>> > >
>> > > "Me too" on Simon's BUG() d
On Friday, February 27, 2015, Chris Dunlop wrote:
> On Fri, Feb 27, 2015 at 11:08:21AM -0800, Pravin Shelar wrote:
> > On Thu, Feb 26, 2015 at 9:13 PM, Chris Dunlop > wrote:
> > > Hi,
> > >
> > > "Me too" on Simon's BUG() described below (apologies for the top post).
> > > Basically:
> > >
> > >
On Fri, Feb 27, 2015 at 11:08:21AM -0800, Pravin Shelar wrote:
> On Thu, Feb 26, 2015 at 9:13 PM, Chris Dunlop wrote:
> > Hi,
> >
> > "Me too" on Simon's BUG() described below (apologies for the top post).
> > Basically:
> >
> > [ 7318.409796] kernel BUG at net/core/skbuff.c:1041!
> > ...
> > [ 73
On Thu, Feb 26, 2015 at 9:13 PM, Chris Dunlop wrote:
> Hi,
>
> "Me too" on Simon's BUG() described below (apologies for the top post).
> Basically:
>
> [ 7318.409796] kernel BUG at net/core/skbuff.c:1041!
> ...
> [ 7318.591562] RIP: 0010:[] []
> pskb_expand_head+0x234/0x270
> ...
> [ 7318.705710
Hi,
"Me too" on Simon's BUG() described below (apologies for the top post).
Basically:
[ 7318.409796] kernel BUG at net/core/skbuff.c:1041!
...
[ 7318.591562] RIP: 0010:[] []
pskb_expand_head+0x234/0x270
...
[ 7318.705710] [] __pskb_pull_tail+0x4c/0x330
[ 7318.711571] [] skb_checksum_help+0x1
Sorry, click send too fast...
I think this line causes the KP:
https://github.com/torvalds/linux/blob/v3.14/net/core/skbuff.c#L1039
But this is weird, because as I read from this mailing list, OVS doesn't
allow shared skb.
I tried turn off GRO: it made receive side slower, but it eventually
crash
Hi folks,
I can now consistently reproduce a kernel panic on my system. I am using
OVS 2.3.0 on 3.14.29 kernel, a sender and a receiver (two VMs) on two
identical hypervisors, using VXLAN tunnel connecting the two VMs. Iperf is
used inside of VMs for generating traffic. The sender side has no pro
18 matches
Mail list logo
