From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: [Qemu-devel] Re: irq problems after live migration with 0.12.4 Date: Tue, 25 May 2010 23:27:16 +0400 Message-ID: <4BFC2494.7010305@msgid.tls.msk.ru> References: <4BF905B7.2040003@msgid.tls.msk.ru> <4BFBAE6D.4010507@dlh.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Peter Lieven Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:36296 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755804Ab0EYT1U (ORCPT ); Tue, 25 May 2010 15:27:20 -0400 In-Reply-To: <4BFBAE6D.4010507@dlh.net> Sender: kvm-owner@vger.kernel.org List-ID: 25.05.2010 15:03, Peter Lieven wrote: > Michael Tokarev wrote: >> 23.05.2010 13:55, Peter Lieven wrote: [] >>> [64442.298521] irq 10: nobody cared (try booting with the "irqpoll" option) [] >>> [64442.299433] handlers: >>> [64442.299840] [] (e1000_intr+0x0/0x190 [e1000]) >>> [64442.300046] Disabling IRQ #10 Apparently, for some reason, e1000_intr decided it's not interesting IRQ or somehow wrong or not for that NIC. I dunno. But something fishy is going on with IRQs here. >> See also LP bug #584131 (https://bugs.launchpad.net/bugs/584131) >> and original Debian bug#580649 (http://bugs.debian.org/580649) >> Not sure if they're related... It looks they are actually the same thing, but happens with different devices and/or IRQs. Either spurious, or unwanted, or unrecognized or somesuch IRQ which is not recognized by the irq handler, which results in disabling that IRQ by the kernel, which is a bad thing (In your case it works because e1000 works in 2 modes, interrupts and polling). > michael, do you have any ideas what i got do to debug whats happening? Unfortunately, no idea. I don't know neither kernel nor kvm internals. > looking at launchpad and debian bug tracker i found other bugs also > with a maybe related problem. so this issue might be greater... Can you share your findings? I don't know other debian bugs which are similar to this one. Thanks! /mjt