All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Anthony Wright <anthony@overnetdata.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: Fri, 10 Jun 2011 12:46:56 -0400	[thread overview]
Message-ID: <20110610164656.GA27518@dumpdata.com> (raw)
In-Reply-To: <20110609133208.GB17525@dumpdata.com>

On Thu, Jun 09, 2011 at 09:32:08AM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Jun 09, 2011 at 02:11:27PM +0100, Anthony Wright wrote:
> > 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.
> 
> One of them was an MCP61 based (BIOSTAR) and the other is
> SB600 (Gigabyte gs_ma69vm_s2) Southbridge. Both are AMD based ... and
> I vagually remember something about quirks for those boards for the AHCI
> controller.
> 
> Let me see if I can reproduce this issue on my box next week.

I tried on my BIOSTAR Group N61PB-M2S which has 4GB physically
and couldn't reproduce it. But let me try to put in some more memory and see.

> > 
> > 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
> 
> Right, and the screen corruption was due to a lacking patch (the VGA support).
> > (Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on
> > some systems).
> 
> There was a crash too? What was that due too?
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2011-06-10 16:46 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 [this message]
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=20110610164656.GA27518@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=anthony@overnetdata.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.