From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:36228) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQ0Qr-000623-3v for qemu-devel@nongnu.org; Mon, 14 Nov 2011 12:35:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQ0Qn-00017d-6z for qemu-devel@nongnu.org; Mon, 14 Nov 2011 12:34:57 -0500 Received: from cantor2.suse.de ([195.135.220.15]:51765 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQ0Qm-00017V-Tv for qemu-devel@nongnu.org; Mon, 14 Nov 2011 12:34:53 -0500 Message-ID: <4EC1518A.1080401@suse.de> Date: Mon, 14 Nov 2011 18:36:10 +0100 From: Alexander Graf MIME-Version: 1.0 References: <4EBB047A.7070104@suse.de> <4EBB9A47.1020405@suse.de> <4EBB9F1A.3020103@suse.de> <5CC0A375-CD95-472E-9688-846DF13D78A1@suse.de> <4EBBB5AE.1050803@suse.de> <6964C9A2-5B0D-412D-91C7-ABBDF0344E7C@suse.de> <4EC14FE7.5000102@suse.de> In-Reply-To: <4EC14FE7.5000102@suse.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [TestDays] s390x emulation error List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Cc: Stefan Hajnoczi , qemu-devel Developers , Paolo Bonzini On 11/14/2011 06:29 PM, Andreas F=C3=A4rber wrote: > Am 10.11.2011 13:36, schrieb Alexander Graf: >> On 10.11.2011, at 12:29, Andreas F=C3=A4rber wrote: >> >>> Am 10.11.2011 11:32, schrieb Alexander Graf: >>>> On 10.11.2011, at 10:53, Andreas F=C3=A4rber wrot= e: >>>> >>>>> Is there a known issue with running multiple instances of >>>>> qemu-system-s390x? I got a hang on openSUSE 12.1 RC2 x86_64 host: >>>>> >>>>> 0x00007f0de7f698d4 in __lll_lock_wait () from /lib64/libpthread.so.= 0 >>>>> (gdb) bt >>>>> #0 0x00007f0de7f698d4 in __lll_lock_wait () from /lib64/libpthread= .so.0 >>>>> #1 0x00007f0de7f651c5 in _L_lock_883 () from /lib64/libpthread.so.= 0 >>>>> #2 0x00007f0de7f6501a in pthread_mutex_lock () from /lib64/libpthr= ead.so.0 >>>>> #3 0x000000000048b4a9 in qemu_mutex_lock (mutex=3D) >>>>> at /home/andreas/QEMU/qemu/qemu-thread-posix.c:54 >>>>> #4 0x00000000004cd3df in qemu_mutex_lock_iothread () >>>>> at /home/andreas/QEMU/qemu/cpus.c:843 >>>>> #5 0x0000000000467580 in main_loop_wait (nonblocking=3D) >>>>> at /home/andreas/QEMU/qemu/main-loop.c:459 >>>>> #6 0x0000000000408984 in main_loop () at /home/andreas/QEMU/qemu/v= l.c:1481 >>>>> #7 main (argc=3D, argv=3D, envp=3D) >>>>> at /home/andreas/QEMU/qemu/vl.c:3474 >>>>> >>>>> Key presses didn't work, SDL window doesn't close, at 99.9% CPU. >>>> Huh? This is all generic code O_o. And no, it's not a known issue. >>> Hm, reproducable by running >>> >>> $ s390x-softmmu/qemu-system-s390x >>> >>> (without arguments) on s390-next branch. >>> >>> I get compat_monitor0 console, but monitor or switching to real conso= le >>> don't work and neither does closing. Same backtrace. >>> >>> Doesn't happen with ppc-softmmu/qemu-system-ppc or x86_64. Maybe an >>> issue with the monitor, only apparent when then monitor is shown at >>> startup rather than later user-invoked? Any suggestions? >> Maybe the guest is executing an endless loop? Could you try to compile= this asm blob for ppc and execute it with -kernel? >> >> Test.S: >> >> _start: >> b . >> >> >> Compile with gcc test.S -nostdlib > Nope, doesn't hang. Hrm. Paolo, any idea? Alex