All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wright <anthony@overnetdata.com>
To: xen-devel@lists.xensource.com
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: USB disk corruption on Xen 4.1.0 & Linux 2.6.38.7
Date: Fri, 29 Jul 2011 20:24:41 +0100	[thread overview]
Message-ID: <4E3308F9.9010903@overnetdata.com> (raw)
In-Reply-To: <20110620123955.GB2973@dumpdata.com>

On 20/06/2011 13:39, Konrad Rzeszutek Wilk wrote:
> On Fri, Jun 17, 2011 at 10:45:41AM +0100, Anthony Wright wrote:
>> On 16/06/2011 21:10, Konrad Rzeszutek Wilk wrote:
>>> So a couple of things popped at when looking at this:
>>> a). "sata_nv 0000:00:08.1: BMDMA: failed to set dma mask, falling back to PIO"
>>>
>>> That is not good. Somehow it wasn't able to set a 32-bit mask. Don't know
>>> if that is due to the driver or just that the kernel can't do it (b/c it
>>> was compiled with some special options).
>> I never saw anything in dmesg or any other logs.
> Uh, I copied that from your logs.
>
>>> b). Are you using some special .config option? If you were to use a normal
>>>  distro would you see this?
>> My config is attached.
> Great.
>>> c). You are using a 32-bit dom0. Didn't notice it until now so I wonder
>>>   if there are some lingering issues (for example not flushing the highmemory
>>>   mappings) that are at foot. Had you tried a 64-bit kernel before?
>> I haven't tried 64 bit because I need a 32 bit kernel.
>>> d). Does the problem exist if you try it with a 2.6.39 kernel or the 3.0-rc3?
>> It happens on every kernel I've tried which is 2.6.39, 2.6.39.x & 3.0-rc3
>>> e). Can you run lspci -n ? There is a pretty big file in drivers/usb/host/pci-quirks.c
>>>   Want to check against your machine.
>> I have the problem on two machines and have attached the lspci -n for
>> both of them.
> Is it possible for you provide this binary blob/USB disk somewhere so I can
> test it on my hardware?
>
Just to let the list know, that after a lot of work by konrad we
discovered that the problem while present in 3.0-rc3 was no longer
present in the final 3.0 release of linux. We never quite understood the
cause and I was the only person who could reproduce it reliably, but
since it's now fixed we're regarding the issue as closed.

thanks,

Anthony.

  reply	other threads:[~2011-07-29 19:24 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
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 [this message]
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=4E3308F9.9010903@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.