From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LQ6Ii-0000DF-Lk
	for qemu-devel@nongnu.org; Thu, 22 Jan 2009 15:37:20 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LQ6Ih-0000CP-1g
	for qemu-devel@nongnu.org; Thu, 22 Jan 2009 15:37:20 -0500
Received: from [199.232.76.173] (port=51035 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LQ6Ig-0000CK-O1
	for qemu-devel@nongnu.org; Thu, 22 Jan 2009 15:37:18 -0500
Received: from moutng.kundenserver.de ([212.227.17.10]:59025)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <martin.mohring@opensuse.org>) id 1LQ6Ig-0004Ze-8t
	for qemu-devel@nongnu.org; Thu, 22 Jan 2009 15:37:18 -0500
Message-ID: <4978D8FB.30801@opensuse.org>
Date: Thu, 22 Jan 2009 21:37:15 +0100
From: Martin Mohring <martin.mohring@opensuse.org>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] linux-user/arm  unsupported syscalls
References: <200901222014.39864.dl9pf@gmx.de>
In-Reply-To: <200901222014.39864.dl9pf@gmx.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Jan-Simon Möller wrote:
> Hi!
>
> I'm running some debian-lenny/arm binaries in user-mode emulation and get these 2 messages:
>
> qemu: Unsupported ARM syscall: 0x9000e5
> qemu: Unsupported ARM syscall: 0x9000e2
>
>
> Any are these known already ? It doesn't seem critical as execution continues.
>
> Best,
> Jan-Simon
>   
Does anybody here know what the 0x9 number in front of e5 and e2 means?
When such an error comes in qemu, for me usually a decimal number of a
syscall from any of the "linux-user/<arch>/syscall_nr.h file is printed.
But not a hexnumber with 0x9000 in front....

Martin