Re: Kernel bug from 3.0 (was phy disks and vifs timing out in DomU)

From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Anthony Wright <anthony@overnetdata.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Todd Deshane <todd.deshane@xen.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Kernel bug from 3.0 (was phy disks and vifs timing out in DomU)
Date: Fri, 26 Aug 2011 10:26:06 -0400	[thread overview]
Message-ID: <20110826142606.GA25511@dumpdata.com> (raw)
In-Reply-To: <4E56B132.9050708@overnetdata.com>

On Thu, Aug 25, 2011 at 09:31:46PM +0100, Anthony Wright wrote:
> On 19/08/2011 13:56, Konrad Rzeszutek Wilk wrote:
> > On Fri, Aug 19, 2011 at 11:22:15AM +0100, Anthony Wright wrote:
> >> On 03/08/2011 16:28, Konrad Rzeszutek Wilk wrote:
> >>> On Fri, Jul 29, 2011 at 08:53:02AM +0100, Anthony Wright wrote:
> >>>> I've just upgraded to xen 4.1.1 with a stock 3.0 kernel on dom0 (with
> >>>> the vga-support patch backported). I can't get my DomU's to work due to
> >>>> the phy disks and vifs timing out in DomU and looking through my logs
> >>>> this morning I'm getting a consistent kernel bug report with xen
> >>>> mentioned at the top of the stack trace and vifdisconnect mentioned on
> >>> Yikes! Ian any ideas what to try?
> >>>
> >>> Anthony, can you compile the kernel with debug=y and when this happens
> >>> see what 'xl dmesg' gives? Also there is also the 'xl debug-keys g' which
> >>> should dump the grants in use.. that might help a bit.
> >> I've compiled a 3.0.1 kernel with CONFIG_DEBUG=Y (a number of other
> >> config values appeared at this point, and I took defaults for them).
> >>
> >> The output from /var/log/messages & 'xl dmesg' is attached. There was no
> >> output from 'xl debug-keys g'.
> > Ok, so I am hitting this too - I was hoping that the patch from Stefano
> > would have fixed the issue, but sadly it did not.
> >
> > Let me (I am traveling right now) see if I can come up with an internim
> > solution until Ian comes with the right fix.
> >
> Hi Konrad - any progress on this - it's a bit of a show stopper for me.

What is interesting is that it happens only with 32-bit guests and with
not-so fast hardware: Atom D510 for me and in your case MSI MS-7309 motherboard
(with what kind of processor?). I've a 64-bit hypervisor - not sure if you
are using a 32-bit or 64-bit.

I hadn't tried to reproduce this on the Atom D510 with a 64-bit Dom0.
But I was wondering if you had this setup before - with a 64-bit dom0?
Or is that really not an option with your CPU?