From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Dreier Subject: Re: trivial Makefile patch + problem report Date: Wed, 29 Nov 2006 14:29:36 -0800 Message-ID: References: <456D76B2.3040001@qumranet.com> <456D7F4B.1000307@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: To: Avi Kivity In-Reply-To: <456D7F4B.1000307-atKUWr5tajBWk0Htik3J/w@public.gmane.org> (Avi Kivity's message of "Wed, 29 Nov 2006 14:38:35 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org I still see the rtc: lost some interrupts at 1024Hz. message with your patch applied. One thing I noticed is that my serial console seems to be related to the messages. I just booted my machine with the serial console printing kernel messages, and I saw the lost interrupt messages when starting a guest twice in a row. Then I did echo 0 0 > /proc/sys/kernel/printk and started a guest with no lost interrupt messages. And then I did echo 8 8 > /proc/sys/kernel/printk and the messages started spewing out and my machine was hosed to the point where I couldn't kill the guest again. The only message that actually printed on the serial console before the machine got stuck spewing rtc messages was device tap0 entered promiscuous mode (I'm using tun and bridging for my qemu networking) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV