This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] USB disk corruption on Xen 4.1.0 & Linux

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] USB disk corruption on Xen 4.1.0 & Linux
From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
Date: Thu, 2 Jun 2011 13:24:56 +0100 (BST)
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 02 Jun 2011 05:54:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110601142349.GD4081@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> 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.

> 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
Yes that's the motherboard.

Attachment: m2n68_am_plus-lspci-vvv
Description: Binary data

Xen-devel mailing list