From: Sander Eikelenboom <linux@eikelenboom.it>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: kernel BUG at net/core/skbuff.c:2839 RIP [<ffffffff819109a2>] skb_segment+0x6b2/0x6d0
Date: Thu, 21 Nov 2013 16:46:18 +0100 [thread overview]
Message-ID: <4310398001.20131121164618@eikelenboom.it> (raw)
In-Reply-To: <1385043004.10637.34.camel@edumazet-glaptop2.roam.corp.google.com>
Thursday, November 21, 2013, 3:10:04 PM, you wrote:
> 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
Ok seems to work for me!
Thx,
Sander
next prev parent reply other threads:[~2013-11-21 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 19:17 kernel BUG at net/core/skbuff.c:2839 RIP [<ffffffff819109a2>] skb_segment+0x6b2/0x6d0 Sander Eikelenboom
2013-11-17 19:59 ` Cong Wang
2013-11-21 12:00 ` Sander Eikelenboom
2013-11-21 14:10 ` Eric Dumazet
2013-11-21 14:14 ` Sander Eikelenboom
2013-11-21 15:46 ` Sander Eikelenboom [this message]
2013-11-21 18:17 ` David Miller
2013-11-21 18:23 ` Eric Dumazet
2013-11-21 18:38 ` David Miller
2013-11-21 19:10 ` [PATCH v2] gso: handle new frag_list of frags GRO packets Eric Dumazet
2013-11-21 19:12 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4310398001.20131121164618@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox