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:45:28 +0100
Message-ID: <C7EB9398.FE1F%keir.fraser@eu.citrix.com>
References: <x2g7ca980ca1004072256i84934d7axf42657db1b8450ad@mail.gmail.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: <x2g7ca980ca1004072256i84934d7axf42657db1b8450ad@mail.gmail.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

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, bu=
t
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,
>=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