From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KK9Yg-0003Zo-VM for qemu-devel@nongnu.org; Sat, 19 Jul 2008 06:20:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KK9Yf-0003Vk-3l for qemu-devel@nongnu.org; Sat, 19 Jul 2008 06:20:58 -0400 Received: from [199.232.76.173] (port=45219 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KK9Ye-0003VK-Cr for qemu-devel@nongnu.org; Sat, 19 Jul 2008 06:20:56 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:51522) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KK9Ye-0002OA-4J for qemu-devel@nongnu.org; Sat, 19 Jul 2008 06:20:56 -0400 Received: from smtp07.web.de (fmsmtp07.dlan.cinetic.de [172.20.5.215]) by fmmailgate01.web.de (Postfix) with ESMTP id F1090E89F553 for ; Sat, 19 Jul 2008 12:20:54 +0200 (CEST) Received: from [88.65.43.154] (helo=[192.168.1.198]) by smtp07.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1KK9Yc-0006OW-00 for qemu-devel@nongnu.org; Sat, 19 Jul 2008 12:20:54 +0200 Message-ID: <4881C001.5010006@web.de> Date: Sat, 19 Jul 2008 12:20:49 +0200 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig41ED896FE670BAEA03ECD01F" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: dyntick timer stall Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig41ED896FE670BAEA03ECD01F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable andrzej zaborowski wrote: > With dyntick enabled I see qemu-system-arm lock up after a while (stay > in code_gen_buffer) due to no more signals reaching qemu. This happens > after a couple of seconds of constantly rearming the host timer with > 250usec period (MIN_TIMER_REARM_US). >=20 > The offender is audio which, if the QEMU_AUDIO_TIMER_PERIOD env > variable is unset, requests audio_timer() be called every 1 vm_clock > tick, resulting in a negative period in qemu_next_deadline_dyntick > which is then trimmed to MIN_TIMER_REARM_US. It seems to be a problem > in host's timer_settime() though. >=20 > timer_settime is constantly called with 250usec as parameter without > the timeout having passed, and then after it's called for the last > time, no signal arrives in the main thread for at least a couple of > minutes. The host is x86_64 Linux 2.6, what may be causing this and > what may be a fix? Cannot confirm: I'm running the Musicpal with SVN head on OpenSuse 11.0 (2.6.25.9, SMP) without problems. And when I attach strace to that process, I see continuous dumps of timer_settime(0, 0, {it_interval=3D{0, 0}, it_value=3D{0, 250000}}, NULL)= =3D 0 --- SIGALRM (Alarm clock) @ 0 (0) --- Can you capture the strace of qemu, or does the issue flee in that case? Jan --------------enig41ED896FE670BAEA03ECD01F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkiBwAYACgkQniDOoMHTA+k9nACfTlKQ1Kqk6QrjRHpbsyLAxCWl o4UAn05zRAVvHXFUUsuwMFigoNNhlc5p =End+ -----END PGP SIGNATURE----- --------------enig41ED896FE670BAEA03ECD01F--