All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Kiss <zoltan.kiss@linaro.org>
To: "Christopher S. Aker" <caker@theshore.net>,
	xen devel <xen-devel@lists.xensource.com>
Subject: Re: netback: Carrier off / Carrier on again, rinse, repeat
Date: Thu, 11 Dec 2014 14:59:39 +0000	[thread overview]
Message-ID: <5489B15B.9040506@linaro.org> (raw)
In-Reply-To: <B5D21A64-6E2E-4FB4-B970-DB90B815A93E@theshore.net>

Hi,

This has been fixed by "f48da8: xen-netback: fix unlimited guest Rx 
internal queue and carrier flapping", it's already in 3.18, I don't know 
if it is going to be backported to 3.17

Zoli

On 11/12/14 14:42, Christopher S. Aker wrote:
> Xen: 4.4.2-pre (28573:f6f6236af933) + xsa111, xsa112, xsa114
> Dom0: 3.17.4
>
> We recently moved our dom0 from 3.10.x to 3.17.4, in order to avoid a netback host crash that has been plaguing us.  After doing so, the new multi-queue netback stuff constantly on/offs carrier on the vif, spamming the console, and making the bridge device leave forwarding state and then immediately reenter forwarding state.
>
> vif vif-43-0 vif43.0: Carrier off due to lack of guest response on queue 0
> br0: port 44(vif43.0) entered disabled state
> vif vif-43-0 vif43.0: Carrier on again
> br0: port 44(vif43.0) entered forwarding state
> br0: port 44(vif43.0) entered forwarding state
> br0: port 44(vif43.0) entered forwarding state
> vif vif-43-0 vif43.0: Carrier off due to lack of guest response on queue 0
> br0: port 44(vif43.0) entered disabled state
> vif vif-43-0 vif43.0: Carrier on again
> br0: port 44(vif43.0) entered forwarding state
> br0: port 44(vif43.0) entered forwarding state
> br0: port 44(vif43.0) entered forwarding state
> vif vif-113-0 vif113.0: Carrier off due to lack of guest response on queue 0
> br0: port 108(vif113.0) entered disabled state
> vif vif-113-0 vif113.0: Carrier on again
> br0: port 108(vif113.0) entered forwarding state
> br0: port 108(vif113.0) entered forwarding state
> br0: port 108(vif113.0) entered forwarding state
> vif vif-43-0 vif43.0: Carrier off due to lack of guest response on queue 0
> br0: port 44(vif43.0) entered disabled state
> vif vif-43-0 vif43.0: Carrier on again
> br0: port 44(vif43.0) entered forwarding state
> br0: port 44(vif43.0) entered forwarding state
> br0: port 44(vif43.0) entered forwarding state
> vif vif-43-0 vif43.0: Carrier off due to lack of guest response on queue 0
> br0: port 44(vif43.0) entered disabled state
> vif vif-43-0 vif43.0: Carrier on again
> br0: port 44(vif43.0) entered forwarding state
> br0: port 44(vif43.0) entered forwarding state
> br0: port 44(vif43.0) entered forwarding state
>
> (This is in the span of a few minutes, however it is non-stop)
>
> If this is normal expected operation then obviously we can live with the console messages, but - I just wanted to report this in the case it is not expected behavior.
>
> Thanks,
> -Chris
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

      reply	other threads:[~2014-12-11 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 14:42 netback: Carrier off / Carrier on again, rinse, repeat Christopher S. Aker
2014-12-11 14:59 ` Zoltan Kiss [this message]

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=5489B15B.9040506@linaro.org \
    --to=zoltan.kiss@linaro.org \
    --cc=caker@theshore.net \
    --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.