All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yasir Assam <mail@endlessvoid.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen 4 rc2: pv domU memory corruption
Date: Sat, 06 Feb 2010 15:25:45 +1100	[thread overview]
Message-ID: <4B6CEF49.6040103@endlessvoid.com> (raw)
In-Reply-To: <20100205163703.GC7906@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 2136 bytes --]

The seg faults are only in domU - dom0 is fine (as I said, I ran 
memtester in dom0 with no problems).

Keir Fraser asked me to try passing "no-tmem" as a boot parameter to the 
hypervisor but that didn't stop the memory corruption.

I only have one memory module (nothing to swap) and given that it's fine 
under Xen 3.4.2 it looks likely to be a software-only problem (esp. as 
repeated memtest86 runs yield no faults).

I have an Intel Core i3 530, which has "onboard" graphics (which I use). 
I also have the Asus P7H55M-Pro motherboard.

Thanks,
Yasir
> On Fri, Feb 05, 2010 at 04:42:16PM +1100, Yasir Assam wrote:
>    
>> I think I've narrowed down my random crashes to Xen 4.0.0 rc2 causing
>> memory corruption in domUs.
>>
>> Xen 3.4.2 is ok, and it doesn't seem to matter which domU or dom0 kernel
>> I'm using.
>>
>> I have two domUs, both PV
>>
>> * 2.6.32.7 from kernel.org
>> * 2.6.18-xen
>>
>> Everything is 64-bit.
>>
>> The random segfaults I was getting looked like bad RAM, but memtest86
>>      
> These segfaults - were they in dom0 or domU? What CPU do you have?
> AMD/Intel?
>
> Did you try to swap the memory modules when you were trying to narrow
> this down?
>
>    
>> didn't report any problems. So I ran memtester
>> (http://pyropus.ca/software/memtester/), a userspace mem test app.
>>
>> When I ran memtester on the dom0 (assigning all available RAM to the
>> dom0) there was no problem. However, when I ran it against either of the
>> domUs, it reported problems with RAM. See memtester output below. The
>> corruption starts at around address 0x02404900.
>>
>> Uninstalling 4.0 rc2 and installing 3.4.2 got rid of the problem, so it
>> looks like 4.0.0 rc2 could be the problem, rather than any of the
>> kernels or the hardware.
>>      
> Did you compile 4.0.0-rc2 with debug=y?
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.733 / Virus Database: 271.1.1/2668 - Release Date: 02/05/10 06:35:00
>
>    


[-- Attachment #1.2: Type: text/html, Size: 2968 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-02-06  4:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  5:42 Xen 4 rc2: pv domU memory corruption Yasir Assam
2010-02-05 16:37 ` Konrad Rzeszutek Wilk
2010-02-06  4:25   ` Yasir Assam [this message]
2010-02-06  8:27     ` Keir Fraser

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=4B6CEF49.6040103@endlessvoid.com \
    --to=mail@endlessvoid.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.