[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1385043004.10637.34.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Thu, 21 Nov 2013 06:10:04 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Sander Eikelenboom <linux@...elenboom.it>
Cc: Eric Dumazet <edumazet@...gle.com>,
Francois Romieu <romieu@...zoreil.com>, netdev@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>
Subject: Re: kernel BUG at net/core/skbuff.c:2839 RIP [<ffffffff819109a2>]
skb_segment+0x6b2/0x6d0
On Thu, 2013-11-21 at 13:00 +0100, Sander Eikelenboom wrote:
> Hello Sander,
>
> Sunday, November 17, 2013, 8:17:44 PM, you wrote:
>
> > Hi Eric,
>
> > With the linux-net changes from this merge window i get the kernel panic below (not with 3.12.0).
>
> > It's on a machine running Xen, 2x rtl8169 nic, and using a bridge for guest networking.
> > This panic in the host kernel only seems to occur when generating a lot of network traffic to and from a guest.
>
> > I tried reverting "tcp: gso: fix truesize tracking" 0d08c42cf9a71530fef5ebcfe368f38f2dd0476f, but that didn't help.
> Hi Eric and Francois,
>
> I have tested some more:
>
> First tried with switching off GSO and GRO on the bridge, this didn't help.
> Then i only switched off GRO on eth0 (r8169) and left the bridge alone. That helped to prevent the oops.
>
> Below the output of ethtool -k for the bridge and eth0 after boot (so the default situation) with which the oops occurs.
> And the part of dmesg where the r8169 get initialized on boot (there are 2, eth0 and eth1).
As mentioned earlier, this problem is known and a patch is under review.
http://marc.info/?l=linux-netdev&m=138419594024851&w=2
Thanks
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists