From mboxrd@z Thu Jan 1 00:00:00 1970 From: Erik Rull Subject: Re: Serial Port Driver does not handle interrupt Date: Tue, 17 Nov 2009 19:00:56 +0100 Message-ID: <4B02E4D8.5040103@rdsoftware.de> References: <4AF83B47.9030405@rdsoftware.de> <4B01D9B4.3080607@rdsoftware.de> <20091116232753.GB11762@debian> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Rodrigo Campos Return-path: Received: from moutng.kundenserver.de ([212.227.126.187]:61650 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752718AbZKQSAw (ORCPT ); Tue, 17 Nov 2009 13:00:52 -0500 In-Reply-To: <20091116232753.GB11762@debian> Sender: kvm-owner@vger.kernel.org List-ID: Rodrigo Campos wrote: > On Tue, Nov 17, 2009 at 12:01:08AM +0100, Erik Rull wrote: >> Erik Rull wrote: >>> Any Ideas? I also tested other IRQ lines and other ttyS* on the >>> system - same behaviour. >> fixed, apic on host side was disabled, kvm / qemu seems to need it. > > I think I hit the same issue. What did you do exactly to solve it ? Enable a > kernel option ? May I ask which one ? :) > > Sorry, I dont have the hardware right now (so I can't play with apic options). I > will have it in a few weeks, so that's why I am asking :) > I enabled the APIC stuff in Kernel and removed my lapic noapic boot parameters. APIC is enabled if you look into /proc/interrupts and the IRQ type is something with apic and not pc / xt. Also ensure that the IRQ line of the serial port matches those of your linux drivers! Otherwise the interrupt gets lost and you'll see some strange behaviours (Chars missing, delayed responses,...). Best regards, Erik