All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Fwd: Re: i8042 buffer size?]
Date: Tue, 26 May 2009 00:20:57 +0200	[thread overview]
Message-ID: <4A1B19C9.8050103@wpkg.org> (raw)
In-Reply-To: <20090525220905.GA8583@amt.cnet>

Marcelo Tosatti wrote:

>>> 18 ff 00 18 ff 00 18 ff 00 18 fe 00 18 ff 00 18 ff 00 18 fe 00 18 ff 00 
>>> 18 ff 00 18 ff 00 18 ff 00 18 ff 00 18 ff 00 08 00 01 18 ff 00 18 ff 00 
>>> 18 ff 01 18 ff 00 08 00 01 18 ff 00 18 fe 02 18 ff 00 18 ff 00 18 ff 01 
>>> 18 fd 00 18 fd 00 18 fa 00 18 f7 00 18 f7 00 18 f4 00 18 f3 00 18 ef 00 
>>> 18 ee 01 18 ed 03 18 ec 04 18 e9 02 08 7f 08 08 7f 00 08 44 00 09 00 00 
>>> 19 fc 01 08 00 00 38 81 ff 18 92 00 
>> This looks seriously like uninitialized memory (12-bit FAT perhaps?) -
>> and very much like a Qemu bug. It doesn't even make sense if interpreted
>> as keyboard scancodes - 00 is reserved and ff is an error condition.
> 
> Tomasz, 
> 
> Can you provide a recipe on how to reproduce this?

I used it with KVM, but it doesn't look KVM specific. I'll see if it 
happens with "pure" Qemu.

To reproduce:

- start a guest; connect to VNC
- type on the keyboard (just tap as much keys as you can) as you see 
BIOS, bootloader, Linux booting
- if it didn't work on the first time, reboot the guest, type on the 
keyboard, change windows with your mouse etc. (make the VNC window 
"always on top" usually helps to have focus)

I can reproduce it almost always.


-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2009-05-25 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 16:30 [Qemu-devel] [Fwd: Re: i8042 buffer size?] Tomasz Chmielewski
2009-05-25 22:09 ` Marcelo Tosatti
2009-05-25 22:20   ` Tomasz Chmielewski [this message]
2009-05-25 22:57     ` Tomasz Chmielewski
2009-05-28  8:44       ` Tomasz Chmielewski
2009-05-28 11:49         ` Marcelo Tosatti

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=4A1B19C9.8050103@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=mtosatti@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.