From: Vasily Evseenko <svpcom@gmail.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: domU crash with kernel BUG at drivers/net/xen-netfront.c:305
Date: Tue, 31 Dec 2013 18:23:54 +0400 [thread overview]
Message-ID: <52C2D37A.1020000@gmail.com> (raw)
In-Reply-To: <CAJ75kXaT7cRnR6cjs2hF6N4Xwy7S6bd84Q-FWQznUE5GvCe4bw@mail.gmail.com>
I've found workaround:
Run "ethtool -K vifX.Y tx off tso off gso off"
on dom0 side (in addition to "ethtool -K eth0 tx off tso off gso off"
on domU).
Disabling offloading only in domU is not sufficient.
On 12/31/2013 04:56 PM, William Dauchy wrote:
> On Fri, Dec 27, 2013 at 1:21 PM, Vasily Evseenko <svpcom@gmail.com> wrote:
>> There are no clear steps to reproduce.
>> Bug triggered only by high tcp network load (webserver pattern - many
>> small connections) every one - two days.
>> See xen, dom0 and domU's info in attachment. I can provide any
>> additional info.
>> I've tried dom0/domU kernels 3.10.23 (vanilla, from centos-xen) and
>> 3.10.25, xen 4.2.3 and 4.3.1.
> maybe testing with kmemleak enabled on the domU will help getting more info.
next prev parent reply other threads:[~2013-12-31 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 11:09 domU crash with kernel BUG at drivers/net/xen-netfront.c:305 Vasily Evseenko
2013-12-27 11:53 ` Wei Liu
2013-12-27 12:21 ` Vasily Evseenko
2013-12-27 14:20 ` Wei Liu
2013-12-31 12:56 ` William Dauchy
2013-12-31 14:23 ` Vasily Evseenko [this message]
2014-01-02 5:09 ` annie li
2014-01-02 11:40 ` Pasi Kärkkäinen
2014-01-02 12:01 ` Wei Liu
2014-01-03 6:15 ` annie li
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=52C2D37A.1020000@gmail.com \
--to=svpcom@gmail.com \
--cc=wdauchy@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.