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: Thu, 2 Jun 2011 10:38:07 -0400
Message-ID: <20110602143807.GA31439@dumpdata.com>
References: <20110601142349.GD4081@dumpdata.com>
	<19639651.14.1307017496558.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: <19639651.14.1307017496558.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 <Ian.Pratt@eu.citrix.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Thu, Jun 02, 2011 at 01:24:56PM +0100, Anthony Wright wrote:
> > Do you get the same problem if you boot baremetal and do 'iommu=soft' (without the mem=4G)? You should see the same error.
> I'm not quite sure what you mean by "boot baremetal", but I've just done a boot where I removed the mem=4096M options from the Xen boot line and added an 'iommu=soft' option. The result of this was a corrupt USB device again.

Baremetal = no Xen.
> 
> > Can you attach your lspci -vvv output too please?
> attached.
> 
> > This is the motherboard you have right?
> > http://www.newegg.com/Product/Product.aspx?Item=N82E16813131613
> Yes that's the motherboard.