From mboxrd@z Thu Jan  1 00:00:00 1970
From: Zoltan Kiss <zoltan.kiss@linaro.org>
Subject: Re: netback: Carrier off / Carrier on again, rinse,
	repeat
Date: Thu, 11 Dec 2014 14:59:39 +0000
Message-ID: <5489B15B.9040506@linaro.org>
References: <B5D21A64-6E2E-4FB4-B970-DB90B815A93E@theshore.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <B5D21A64-6E2E-4FB4-B970-DB90B815A93E@theshore.net>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Christopher S. Aker" <caker@theshore.net>, xen devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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
>