From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55865) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQ0Lc-0002qf-60 for qemu-devel@nongnu.org; Mon, 14 Nov 2011 12:29:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQ0LX-0008HK-T3 for qemu-devel@nongnu.org; Mon, 14 Nov 2011 12:29:32 -0500 Received: from cantor2.suse.de ([195.135.220.15]:51326 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQ0LX-0008Gy-Jx for qemu-devel@nongnu.org; Mon, 14 Nov 2011 12:29:27 -0500 Message-ID: <4EC14FE7.5000102@suse.de> Date: Mon, 14 Nov 2011 18:29:11 +0100 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= 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> In-Reply-To: <6964C9A2-5B0D-412D-91C7-ABBDF0344E7C@suse.de> Content-Type: text/plain; charset=UTF-8 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: Alexander Graf Cc: Stefan Hajnoczi , qemu-devel Developers Am 10.11.2011 13:36, schrieb Alexander Graf: >=20 > On 10.11.2011, at 12:29, Andreas F=C3=A4rber wrote: >=20 >> Am 10.11.2011 11:32, schrieb Alexander Graf: >>> >>> On 10.11.2011, at 10:53, Andreas F=C3=A4rber wrote= : >>> >>>> 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/libpthre= ad.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/vl= .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 consol= e >> 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? >=20 > Maybe the guest is executing an endless loop? Could you try to compile = this asm blob for ppc and execute it with -kernel? >=20 > Test.S: >=20 > _start: > b . >=20 >=20 > Compile with gcc test.S -nostdlib Nope, doesn't hang. Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=BC= rnberg