From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42594) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yq6ij-0000oH-9I for qemu-devel@nongnu.org; Wed, 06 May 2015 17:19:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yq6if-0001nN-4X for qemu-devel@nongnu.org; Wed, 06 May 2015 17:19:09 -0400 Received: from mail-qk0-x235.google.com ([2607:f8b0:400d:c09::235]:33097) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yq6if-0001n8-0c for qemu-devel@nongnu.org; Wed, 06 May 2015 17:19:05 -0400 Received: by qkx62 with SMTP id 62so15449856qkx.0 for ; Wed, 06 May 2015 14:19:04 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Programmingkid In-Reply-To: Date: Wed, 6 May 2015 17:19:01 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <18C7C30B-DC02-4CF1-8190-EFB063692272@gmail.com> Subject: Re: [Qemu-devel] Help with deadlock when using sound List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: qemu-devel qemu-devel On May 6, 2015, at 5:10 PM, Peter Maydell wrote: > On 6 May 2015 at 20:41, Programmingkid = wrote: >>=20 >> On May 6, 2015, at 1:00 PM, Peter Maydell wrote: >>=20 >>> On 6 May 2015 at 17:40, Programmingkid = wrote: >>>> (gdb) bt >>>> #0 0x00007fff824e2db6 in semaphore_wait_trap () >>>> #1 0x00007fff824e8417 in pthread_mutex_lock () >>>> #2 0x0000000100267199 in qemu_mutex_lock (mutex=3D) at = util/qemu-thread-posix.c:73 >>>> #3 0x003c44016e95153b in ?? () >>>>=20 >>>> My host is Mac OS 10.6.8. My guest isn't really anything. I have = used Windows XP before but it isn't necessary to reproduce the problem. >>>>=20 >>>> The ?? is what appears to be the problem. I can't even print = instructions at that address. Any ideas as to what is calling the = qemu_mutex_lock() function could help. >>>=20 >>> Recompile with optimization disabled and try again. It would >>> also be helpful to provide the backtraces for all threads. >>=20 >> Here is my info: >>=20 >> Configured like this: >> configure --target-list=3Dppc-softmmu,i386-softmmu --disable-gtk = --audio-drv-list=3Dsdl --enable-debug >=20 > Does that work? I would not expect anything other than the > coreaudio backend to necessarily work on OSX... At any rate, > better to start with debugging the issue under coreaudio for > simplicity, since you say it happens there too. Checking > whether it works OK on x86/Linux host would also help > narrow down the possibilities. Already tried that. Something is wrong with my Linux distro because = every time I try to run QEMU, I see a floating point exception. Maybe = somebody on the list who does use Linux could let us know if using = -soundhw pcspk works.=20 >=20 >> Thread 8 (process 29237): >> #0 tb_jmp_cache_hash_func (pc=3D1) at exec/exec-all.h:208 >> #1 0x000000010000c9d7 in tb_find_slow (env=3D0x103846620, = pc=3D133133655, cs_base=3D133118944, flags=3D244) at = /Users/user/Documents/Development/Projects/Qemu/qemu-git/cpu-exec.c:309 >> #2 0x000000010000cae3 in tb_find_fast (env=3D0x103846620) at = /Users/user/Documents/Development/Projects/Qemu/qemu-git/cpu-exec.c:327 >> #3 0x000000010000cf66 in cpu_x86_exec (env=3D0x103846620) at = /Users/user/Documents/Development/Projects/Qemu/qemu-git/cpu-exec.c:485 >> #4 0x000000010003978b in tcg_cpu_exec (env=3D0x103846620) at = /Users/user/Documents/Development/Projects/Qemu/qemu-git/cpus.c:1354 >> #5 0x0000000100039878 in tcg_exec_all () at = /Users/user/Documents/Development/Projects/Qemu/qemu-git/cpus.c:1387 >> #6 0x0000000100038dec in qemu_tcg_cpu_thread_fn (arg=3D0x10383e400) = at /Users/user/Documents/Development/Projects/Qemu/qemu-git/cpus.c:1032 >> #7 0x00007fff8251bfd6 in _pthread_start () >> #8 0x00007fff8251be89 in thread_start () >=20 > This backtrace says QEMU hasn't hung -- it is still executing > guest code (though possibly the guest has crashed or gone off > into the weeds, of course). If it were still executing guest code, then accessing the monitor would = still work.=20=