From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M8iXS-0003Ln-3f for qemu-devel@nongnu.org; Mon, 25 May 2009 18:20:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M8iXQ-0003Kt-8B for qemu-devel@nongnu.org; Mon, 25 May 2009 18:20:57 -0400 Received: from [199.232.76.173] (port=33360 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M8iXP-0003Kn-QZ for qemu-devel@nongnu.org; Mon, 25 May 2009 18:20:55 -0400 Received: from mx03.syneticon.net ([78.111.66.105]:50258) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M8iXP-00064j-Ef for qemu-devel@nongnu.org; Mon, 25 May 2009 18:20:55 -0400 Message-ID: <4A1B19C9.8050103@wpkg.org> Date: Tue, 26 May 2009 00:20:57 +0200 From: Tomasz Chmielewski MIME-Version: 1.0 Subject: Re: [Qemu-devel] [Fwd: Re: i8042 buffer size?] References: <4A14300B.4000204@wpkg.org> <20090525220905.GA8583@amt.cnet> In-Reply-To: <20090525220905.GA8583@amt.cnet> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcelo Tosatti Cc: qemu-devel@nongnu.org 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