qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel Developers <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [TestDays] s390x emulation error
Date: Mon, 14 Nov 2011 18:36:10 +0100	[thread overview]
Message-ID: <4EC1518A.1080401@suse.de> (raw)
In-Reply-To: <4EC14FE7.5000102@suse.de>

On 11/14/2011 06:29 PM, Andreas Färber wrote:
> Am 10.11.2011 13:36, schrieb Alexander Graf:
>> On 10.11.2011, at 12:29, Andreas Färber<afaerber@suse.de>  wrote:
>>
>>> Am 10.11.2011 11:32, schrieb Alexander Graf:
>>>> On 10.11.2011, at 10:53, Andreas Färber<afaerber@suse.de>  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/libpthread.so.0
>>>>> #3  0x000000000048b4a9 in qemu_mutex_lock (mutex=<optimized out>)
>>>>>    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=<optimized out>)
>>>>>    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=<optimized out>, argv=<optimized out>, envp=<optimized out>)
>>>>>    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 console
>>> 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

  reply	other threads:[~2011-11-14 17:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 22:53 [Qemu-devel] [TestDays] s390x emulation error Andreas Färber
2011-11-09 23:17 ` Andreas Färber
2011-11-09 23:20   ` Alexander Graf
2011-11-09 23:18 ` Alexander Graf
2011-11-09 23:20   ` Andreas Färber
2011-11-09 23:21     ` Alexander Graf
2011-11-09 23:23       ` Andreas Färber
2011-11-09 23:26         ` Alexander Graf
2011-11-10  9:32 ` Andreas Färber
2011-11-10  9:53   ` Andreas Färber
2011-11-10 10:32     ` Alexander Graf
2011-11-10 11:29       ` Andreas Färber
2011-11-10 12:36         ` Alexander Graf
2011-11-14 17:29           ` Andreas Färber
2011-11-14 17:36             ` Alexander Graf [this message]
2011-11-14 17:39               ` Paolo Bonzini
2011-11-12 10:08         ` Andreas Färber
2011-11-12 10:40           ` Stefan Weil
2011-11-12 12:50             ` Alexander Graf
2011-11-13  8:48           ` Paolo Bonzini
2011-11-14 14:37             ` Andreas Färber
2011-11-18 15:16           ` Andreas Färber
2011-11-10 10:31   ` Alexander Graf
2011-11-18 15:33   ` Alexander Graf
2011-11-21 18:39     ` Andreas Färber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EC1518A.1080401@suse.de \
    --to=agraf@suse.de \
    --cc=afaerber@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).