From: Anthony Wright <anthony@overnetdata.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: USB disk corruption on Xen 4.1.0 & Linux 2.6.38.7
Date: Thu, 09 Jun 2011 14:11:27 +0100 [thread overview]
Message-ID: <4DF0C67F.6040602@overnetdata.com> (raw)
In-Reply-To: <20110602144411.GA31559@dumpdata.com>
I've got things running on a number of systems now, and have tried a
number of combinations. I have changed machines and USB memory sticks,
and the fault seems to be related to the machine rather than the memory
stick. I have 3 machines with >4GB ram & 2 memory sticks, changing
memory sticks doesn't have any effect, but only two out of the three
machines I tried has a problem, the third works fine.
I have previously attached the lspci -vvv for one of the machines that
fails, and the lspci -vvv for the second machine is attached to an email
relating to the screen corruption problems I was having a few days ago
(Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on
some systems).
Cheers,
Anthony
On 02/06/2011 15:44, Konrad Rzeszutek Wilk wrote:
> On Thu, Jun 02, 2011 at 10:38:07AM -0400, Konrad Rzeszutek Wilk wrote:
>> 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.
> I've an BIOSTART motherboard that looks to have a similar EHCI controller - MCP61 based.
> Is the USB stick that you are using any special? Or is just a normal one?
next prev parent reply other threads:[~2011-06-09 13:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8150663.20.1306842333642.JavaMail.root@zimbra.overnetdata.com>
2011-05-31 12:07 ` USB disk corruption on Xen 4.1.0 & Linux 2.6.38.7 Anthony Wright
2011-05-31 14:54 ` Konrad Rzeszutek Wilk
2011-06-01 9:52 ` Anthony Wright
2011-06-01 14:23 ` Konrad Rzeszutek Wilk
2011-06-02 12:24 ` Anthony Wright
2011-06-02 14:38 ` Konrad Rzeszutek Wilk
2011-06-02 14:44 ` Konrad Rzeszutek Wilk
2011-06-02 15:59 ` Anthony Wright
2011-06-09 13:11 ` Anthony Wright [this message]
2011-06-09 13:25 ` Ian Pratt
2011-06-09 13:32 ` Konrad Rzeszutek Wilk
2011-06-09 13:40 ` Anthony Wright
2011-06-10 16:46 ` Konrad Rzeszutek Wilk
2011-06-13 22:06 ` Konrad Rzeszutek Wilk
2011-06-15 10:45 ` Anthony Wright
2011-06-15 11:43 ` Ian Pratt
2011-06-16 20:10 ` Konrad Rzeszutek Wilk
2011-06-17 9:45 ` Anthony Wright
2011-06-20 12:39 ` Konrad Rzeszutek Wilk
2011-07-29 19:24 ` Anthony Wright
2011-06-01 8:53 ` Ian Pratt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF0C67F.6040602@overnetdata.com \
--to=anthony@overnetdata.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).