public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Campos <rodrigo@sdfg.com.ar>
To: Erik Rull <spamfolder@rdsoftware.de>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Serial Port Driver does not handle interrupt
Date: Tue, 17 Nov 2009 15:40:09 -0300	[thread overview]
Message-ID: <20091117184009.GB26817@debian> (raw)
In-Reply-To: <4B02E4D8.5040103@rdsoftware.de>

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

      reply	other threads:[~2009-11-17 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 15:54 Serial Port Driver does not handle interrupt Erik Rull
2009-11-16 22:59 ` Erik Rull
2009-11-16 23:01 ` Erik Rull
2009-11-16 23:27   ` Rodrigo Campos
2009-11-17 18:00     ` Erik Rull
2009-11-17 18:40       ` Rodrigo Campos [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091117184009.GB26817@debian \
    --to=rodrigo@sdfg.com.ar \
    --cc=kvm@vger.kernel.org \
    --cc=spamfolder@rdsoftware.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox