Re: xen-detect fail.

[Keir Fraser <keir.fraser@eu.citrix.com>]

Your output indicates that it is different rip values that cause the
exception on the two platforms. Did you rebuild xen-detect on each platform?
Otherwise it might indicate that some other instruction than UD2A is
faulting on the bad platform, and causing a general protection fault rather
than undefined opcode fault.

 -- Keir

On 14/04/2010 15:45, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

> Hi,
> 
> Where the code calls signal(SIGILL, ...) can you try changing it to
> signal(SIGSEGV, ...) instead? Could be that some versions of Linux deliver
> invalid opcode exceptions as SIGSEGV rather than SIGILL. Would be weird, but
> we can handle it if that's what's happening.
> 
>  Thanks,
>  Keir
> 
> On 08/04/2010 06:56, "Qiang Fu" <fu7iang@gmail.com> wrote:
> 
>> Hi,
>> 
>> xen-detect may hang on some cases.
>> I hit this issue on one of my box. And I found that
>> it hang when executing "ud2a". Seems it not trap
>> and sig the user.
>> 
>> OS: RHEL 5.4       2.6.18-164.15.1.el5
>> glibc-2.5-42.el5_4.3.x86_64
>> 
>> /var/log/message
>> kernel: xen-detect general protection rip:400665 rsp:7fff3a922888 error:0
>> 
>> On platform it work correctly, the message is
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel