From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: USB disk corruption on Xen 4.1.0 & Linux 2.6.38.7
Date: Wed, 1 Jun 2011 10:23:49 -0400
Message-ID: <20110601142349.GD4081@dumpdata.com>
References: <20110531145409.GN14641@dumpdata.com>
	<10950255.34.1306921970059.JavaMail.root@zimbra.overnetdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <10950255.34.1306921970059.JavaMail.root@zimbra.overnetdata.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Anthony Wright <anthony@overnetdata.com>
Cc: Ian.Pratt@eu.citrix.com, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

> > Does the issue go away if you limit the total amount of memory visible to xen to 4GB? (mem=4096M on the xen command line)
> > 
> > If so, I suspect this is a swiotlb or latent UHCI driver issue. The easiest way of working around it is just to ensure all > dom0 memory gets allocated below 4GB, but it would be good to investigate properly.
> 
> Yes! I put mem=4096M on the xen command line as asked and everything starts working as it should yea!

<scratches his head> This is most unexpected. Do you get the same problem if you boot
baremetal and do 'iommu=soft' (without the mem=4G)? You should see the same error.
Can you attach your lspci -vvv output too please? This is the motherboard you have right?
http://www.newegg.com/Product/Product.aspx?Item=N82E16813131613