From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: xen-detect fail.
Date: Wed, 14 Apr 2010 15:55:30 +0100
Message-ID: <C7EB95F2.FE2E%keir.fraser@eu.citrix.com>
References: <C7EB9398.FE1F%keir.fraser@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C7EB9398.FE1F%keir.fraser@eu.citrix.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Qiang Fu <fu7iang@gmail.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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,
>=20
> Where the code calls signal(SIGILL, ...) can you try changing it to
> signal(SIGSEGV, ...) instead? Could be that some versions of Linux delive=
r
> invalid opcode exceptions as SIGSEGV rather than SIGILL. Would be weird, =
but
> we can handle it if that's what's happening.
>=20
>  Thanks,
>  Keir
>=20
> On 08/04/2010 06:56, "Qiang Fu" <fu7iang@gmail.com> wrote:
>=20
>> Hi,
>>=20
>> 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.
>>=20
>> OS: RHEL 5.4=A0=A0=A0=A0=A0=A0 2.6.18-164.15.1.el5
>> glibc-2.5-42.el5_4.3.x86_64
>>=20
>> /var/log/message
>> kernel: xen-detect general protection rip:400665 rsp:7fff3a922888 error:=
0
>>=20
>> On platform it work correctly, the message is
>=20
>=20
>=20
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel