From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: Re: PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0 Date: Mon, 1 Dec 2014 15:47:32 +0000 (GMT) Message-ID: <13856190.12.1417448852473.JavaMail.root@zimbra.overnetdata.com> References: <547C79C0.4010608@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <547C79C0.4010608@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > On 28/11/14 15:19, Anthony Wright wrote: > > 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 > > The guest's frontend driver isn't putting valid requests onto the ring > (it crosses a page boundary) so this is a frontend bug. > > What guest are you running? We're running a custom built 64 bit para-virtualised DomU with a stock Linux 3.17.3 downloaded from kernel.org. The problem only started happening when we upgraded the DomU Linux kernel from 3.3.2