From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FzoxU-00055C-H2 for qemu-devel@nongnu.org; Mon, 10 Jul 2006 02:09:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FzoxR-000550-LB for qemu-devel@nongnu.org; Mon, 10 Jul 2006 02:09:27 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FzoxR-00054x-GO for qemu-devel@nongnu.org; Mon, 10 Jul 2006 02:09:25 -0400 Received: from [203.190.192.17] (helo=wasp.net.au) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FzoyS-0002bv-Tf for qemu-devel@nongnu.org; Mon, 10 Jul 2006 02:10:29 -0400 Message-ID: <44B1EF07.9060302@wasp.net.au> Date: Mon, 10 Jul 2006 10:09:11 +0400 From: Brad Campbell MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] rtc: lost some interrupts at 1024Hz. 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 G'day all, Just wonder if anyone else is seeing this. I've not had a chance to track it down or try to debug it yet. I'm running latest QEMU CVS with kqemu and the -no-tsc patch on a vanilla 2.6.17.3 kernel with suspend2. The VM behaves perfectly until I do a suspend/resume of the host. When the machine comes back, most of the time (not all the time however) it ends up flooding my logs with this message. Jul 8 17:26:03 localhost kernel: [43299223.910000] rtc: lost some interrupts at 1024Hz. Jul 8 17:26:03 localhost kernel: [43299223.930000] rtc: lost some interrupts at 1024Hz. Jul 8 17:26:03 localhost kernel: [43299223.950000] rtc: lost some interrupts at 1024Hz. Jul 8 17:26:03 localhost kernel: [43299223.970000] rtc: lost some interrupts at 1024Hz. Of course if I shutdown/reboot the VM the problem goes away. I've seen this before but it's been a while from memory. I'm running a vanilla 2.6.17.3 kernel in the guest booted with GRUB and both host and guest are configured with HZ=100. I seem to recall mplayer does the same thing if I leave something playing over a suspend/resume, but I've not had a chance to look at it further. It's pretty reproducible here with qemu anyway. This is about the only remaining thing that is preventing me leaving VM's up over suspend/resume now. Other than that, it's all good. I'll probably get to looking at it in the next couple of weeks if nobody has any pointers. Brad -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams