All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wright <anthony@overnetdata.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0
Date: Fri, 28 Nov 2014 15:19:06 +0000	[thread overview]
Message-ID: <5478926A.80503@overnetdata.com> (raw)

We have a 64 bit PV DomU that we recently upgraded from linux 3.3.2 to
3.17.3 running on a 64 bit 3.17.3 Dom0 with Xen 4.4.0.

Shortly after the upgrade we started to lose network connectivity to the
DomU a few times a day that required a reboot to fix. We see nothing in
the xen logs or xl dmesg, but when we looked at the dmesg output we saw
the following output for the two incidents we investigated in detail:

[69332.026586] vif vif-4-0 vif4.0: txreq.offset: 85e, size: 4002, end: 6144
[69332.026607] vif vif-4-0 vif4.0: fatal error; disabling device
[69332.031069] br-default: port 2(vif4.0) entered disabled state


[824365.530740] vif vif-9-0 vif9.0: txreq.offset: a5e, size: 4002, end: 6656
[824365.530748] vif vif-9-0 vif9.0: fatal error; disabling device
[824365.531191] br-default: port 2(vif9.0) entered disabled state

We have a very similar setup running on another machine with a 3.17.3
DomU, 3.17.3 Dom0 and Xen 4.4.0 but we can't reproduce the issue on this
machine. This is a test system rather than a production system so has a
different workload and fewer CPUs.

The piece of code that outputs the error is in
drivers/net/xen-netback/netback.c.

The DomU has 4000MB of RAM and 8 CPUs.

Any ideas?

Thanks,

Anthony.

             reply	other threads:[~2014-11-28 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 15:19 Anthony Wright [this message]
2014-11-28 15:23 ` PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0 Ian Campbell
2014-11-28 16:34   ` Anthony Wright
2014-12-01 14:22 ` David Vrabel
2014-12-01 15:47   ` Anthony Wright
2014-12-01 18:17   ` David Vrabel
2014-12-02 15:40     ` Anthony Wright
2014-12-04 15:36     ` Anthony Wright
2014-12-04 15:53       ` David Vrabel
2014-12-05 12:48         ` Zoltan Kiss
2014-12-05 14:16           ` David Vrabel
2014-12-08 12:03 ` David Vrabel
2014-12-09 16:46   ` Anthony Wright
     [not found] <E3A471111497714D953FBC6F551B7AA7B6BD43C9@USALMELXP004.LUXGROUP.NET>
2014-12-09 22:39 ` Anthony Wright

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=5478926A.80503@overnetdata.com \
    --to=anthony@overnetdata.com \
    --cc=xen-devel@lists.xensource.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 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.