On Tue, Nov 17, 2009 at 07:00:56PM +0100, Erik Rull wrote: > 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. Ahh, thanks :) > > 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,...). I will check that too. Thanks a lot, Rodrigo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
