qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brian Wheeler <bdwheele@indiana.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] weird mouse troubles in latest git
Date: Fri, 15 Oct 2010 11:28:48 -0400	[thread overview]
Message-ID: <1287156528.27028.78.camel@nibbler.dlib.indiana.edu> (raw)

I'm trying to run openstep 2.4 on the latest git and the mouse hangs
after a few seconds of running.  I turned on debugging some debugging
flags:
ps2.c:  DEBUG_MOUSE
pckbd.c: DEBUG_KEYBOARD
i8259.c: DEBUG_PIC

I'm still not sure where the problem is, but here's what I've
discovered:  If I filter out all messages except ones with irq=12 I get
this sequence (when using the sdl ui):

* a bunch of set_irq level=1 followed immediately by a level=0 which is
what I'd expect.
* when the mouse hangs, it hangs with a level=1
* hitting ctrl-alt to release focus gives me a bunch of level=1/level=0
pairs along with a bunch of pic_interrupts for irq 12


When I use the vnc ui, I get 2 pairs of "set_irq irq=12 level=1/0"
followed by a pic: pic_interrupt: irq=12.  When I move the mouse into
the vnc window I get the set_irq level = 1 and the mouse is done.

So, is the guest not picking up the interrupts correctly or is there
some problem with the UI not sending mouse requests through if the guest
hasn't handled them?

There are mouse troubles with OS/2 4.0 as well which may be related (the
button stops working but the mouse would still move.

Its not terribly important, but I thought someone should know.

                 reply	other threads:[~2010-10-15 15:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1287156528.27028.78.camel@nibbler.dlib.indiana.edu \
    --to=bdwheele@indiana.edu \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).