From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IGioF-0004bN-Na for qemu-devel@nongnu.org; Thu, 02 Aug 2007 18:06:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IGioD-0004VV-3c for qemu-devel@nongnu.org; Thu, 02 Aug 2007 18:06:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IGioD-0004VC-0q for qemu-devel@nongnu.org; Thu, 02 Aug 2007 18:06:17 -0400 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IGioC-0004wG-GB for qemu-devel@nongnu.org; Thu, 02 Aug 2007 18:06:16 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IGio8-00006Y-Uy for qemu-devel@nongnu.org; Fri, 03 Aug 2007 00:06:12 +0200 Received: from fw2.isgenesis.com ([168.215.170.1]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Aug 2007 00:06:12 +0200 Received: from charles by fw2.isgenesis.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Aug 2007 00:06:12 +0200 From: Charles Duffy Date: Thu, 02 Aug 2007 17:06:03 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit In-Reply-To: Sender: news Subject: [Qemu-devel] Re: Network connections stalling (due to lost interrupts/ticks?) Reply-To: charles@dyfis.net, 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 Charles Duffy wrote: > There's a warning on startup that the system can't set a 1024Hz timer, > which persists even after I set /proc/sys/dev/rtc/max-user-freq to 1024, > and I occasionally get warnings at runtime ("Your time source seems to > be instable or some driver is hogging interrupts"). This was happening because my host kernel was compiled with CONFIG_HPET_RTC_IRQ=y. I've disabled this option, recompiled and rebooted, and it resolved the RTC warning (and apparently, the unstable time source messages) -- but my network connections are still stalling.