Re: [Xen-devel] Low memory corruption - trap invalid opcode ip:7f5c688028b0 sp:7ffff97af848 error:0 in ld-2.11.2.so[7f5c687ef000+1e000]

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Thu, 2011-12-01 at 14:45 +0000, anatoly techtonik wrote:
> On Thu, Dec 1, 2011 at 4:59 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> wrote:
>         On Tue, 2011-11-29 at 17:54 +0000, anatoly techtonik wrote:
>         > My first message didn't get to the list, so I am trying once
>         more.
>         >
>         > ---------- Forwarded message ----------
>         > From: anatoly techtonik <techtonik@xxxxxxxxx>
>         > Date: Mon, Nov 14, 2011 at 5:46 PM
>         > Subject: Low memory corruption - trap invalid opcode
>         ip:7f5c688028b0
>         > sp:7ffff97af848 error:0 in ld-2.11.2.so[7f5c687ef000+1e000]
>         > To: xen-devel@xxxxxxxxxxxxxxxxxxx
>         >
>         >
>         > I was redirected here from this bug report in Debian against
>         > 'svn-buildpackage' after I started getting 'Illegal
>         instruction' error
>         > after running 'svn-inject' and similar command on a brand
>         new VM
>         > instance for Debian Squeeze.
>         > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646945#54
>         >
>         > dmesg from VM
>         > 17067.210187] svn-inject[6026] trap invalid opcode
>         ip:7f5c688028b0
>         > sp:7ffff97af848 error:0 in ld-2.11.2.so[7f5c687ef000+1e000]
>         
>         
>         This is more than likely the same issue as
>         http://bugs.debian.org/646549.
> 
> 
> Thanks. The processor is the same Intel Xeon E31270, so I am going to
> subscribe to this bug. In the meanwhile - is it possible to disable
> this AVX somehow or find another workaround until it is fixed in
> Squeeze? 

There is some additional information about the Xen-specific
manifestation of this bug in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649349

One workaround is to use xsave=1 on your hypervisor command line, but
the cost is that you cannot migrate guests anymore.

Ian.




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