Re: [Xen-devel] Xen 4 rc2: pv domU memory corruption

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

Can you post your domU config?

 -- Keir

On 06/02/2010 04:25, "Yasir Assam" <mail@xxxxxxxxxxxxxxx> wrote:

> 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@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >  
> >
> >
> >
> > No virus found in this incoming message.
> > Checked by AVG - www.avg.com <http://www.avg.com>  
> > Version: 9.0.733 / Virus Database: 271.1.1/2668 - Release Date: 02/05/10 06:35:00
> >
> >   



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