From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1O2S3x-00071y-TW
	for qemu-devel@nongnu.org; Thu, 15 Apr 2010 12:37:09 -0400
Received: from [140.186.70.92] (port=50755 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1O2S3v-0006J0-4G
	for qemu-devel@nongnu.org; Thu, 15 Apr 2010 12:37:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <blauwirbel@gmail.com>) id 1O2S0R-0002Q7-7g
	for qemu-devel@nongnu.org; Thu, 15 Apr 2010 12:33:35 -0400
Received: from mail-pv0-f173.google.com ([74.125.83.173]:39196)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <blauwirbel@gmail.com>) id 1O2S0Q-0002Pm-HR
	for qemu-devel@nongnu.org; Thu, 15 Apr 2010 12:33:31 -0400
Received: by pvd12 with SMTP id 12so903876pvd.4
	for <qemu-devel@nongnu.org>; Thu, 15 Apr 2010 09:33:29 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <773976174.623921271284601521.JavaMail.root@mail-01.cse.ucsc.edu>
References: <741428003.623901271284473416.JavaMail.root@mail-01.cse.ucsc.edu>
	<773976174.623921271284601521.JavaMail.root@mail-01.cse.ucsc.edu>
Date: Thu, 15 Apr 2010 19:33:29 +0300
Message-ID: <v2vf43fc5581004150933o4c9462baz3064f5d8e7b2226d@mail.gmail.com>
Subject: Re: [Qemu-devel] sparc-linux-usermode broken after latest pull
From: Blue Swirl <blauwirbel@gmail.com>
Content-Type: text/plain; charset=UTF-8
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: David Munday <cromom@soe.ucsc.edu>
Cc: qemu-devel@nongnu.org

On 4/15/10, David Munday <cromom@soe.ucsc.edu> wrote:
> Hello,
>  Our lab just did a pull from the qemu repository and now we are unable to run a 32-bit sparc target on a 64-bit host. This functionality was working before we did the pull. The error message we get is:mmap: No such device or address
>
>  And then the process dies. We are not sure why this is occuring but have verified against our earlier qemu copy that the behavior did not exist before our pull on Sunday.
>
>  We appreciate any insights anyone might have.

I can't replicate this, sparc-linux-user, sparc32plus-linux-user and
sparc64-linux-user still work like before on amd64 Linux host.

What is the host and which program? Could you bisect the problem,
there haven't been that many commits in last few days?