From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [regression] KVM: hangs and "irq timeout" booting HURD unless -no-kvm-irqchip passed Date: Mon, 07 Feb 2011 14:39:01 +0200 Message-ID: <4D4FE7E5.2040308@redhat.com> References: <1283171743-10766-1-git-send-email-avi@redhat.com> <1283171743-10766-2-git-send-email-avi@redhat.com> <20110207060030.GA1896@elie> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm@vger.kernel.org, Michael Tokarev , Guillem Jover To: Jonathan Nieder Return-path: Received: from mx1.redhat.com ([209.132.183.28]:51111 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751799Ab1BGMjM (ORCPT ); Mon, 7 Feb 2011 07:39:12 -0500 In-Reply-To: <20110207060030.GA1896@elie> Sender: kvm-owner@vger.kernel.org List-ID: On 02/07/2011 08:00 AM, Jonathan Nieder wrote: > Hi kvm-ers, > > When I boot the HURD with > > kvm -m 768 -net nic,model=ne2k_pci -net user hurd-installed.qemu > > it hangs and eventually produces two messages: > > hd0: unexpected_intr: status=0x58 { DriveReady SeekComplete DataRequest } > hd0: irq timeout: status=0x58 { DriveReady Seek Complete DataRequest } > > More details below[1]. > > Adding -no-kvm-irqchip to the kvm command line fixes it --- no > more hangs or confusing messages (thanks, Guillem!). > > Bisects (thanks to Michael for the idea) to > > v2.6.37-rc1~142^2~39 (KVM: Check for pending events before > attempting injection, 2010-07-27). > > Bisection log and kernel configuration available upon request (but > probably not too relevant --- the 2.6.37 distro kernel from Debian > exhibits the same problem). Reproducible with kvm/master (2d4b4d26, > 2011-02-01). > > CPU is a dual-core AMD Athlon II P360, family 16, model 6. > > Any hints for tracking this down? For those wanting to follow along > at home, you can find a HURD cd to try at [2]. > Reproduced on AMD, not on Intel. Given that I see a few PIC and PIT PIOs before the hang, the problem is likely at the PIT. Will look further. -- error compiling committee.c: too many arguments to function