From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MDgSQ-0004pd-FX for qemu-devel@nongnu.org; Mon, 08 Jun 2009 11:08:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MDgSM-0004kP-Ud for qemu-devel@nongnu.org; Mon, 08 Jun 2009 11:08:18 -0400 Received: from [199.232.76.173] (port=51323 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MDgSM-0004kD-Pn for qemu-devel@nongnu.org; Mon, 08 Jun 2009 11:08:14 -0400 Received: from mx03.syneticon.net ([78.111.66.105]:46022) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MDgSM-0005vL-6o for qemu-devel@nongnu.org; Mon, 08 Jun 2009 11:08:14 -0400 Message-ID: <4A2D2973.6030101@wpkg.org> Date: Mon, 08 Jun 2009 17:08:35 +0200 From: Tomasz Chmielewski MIME-Version: 1.0 Subject: Re: [Qemu-devel] [SOLUTION] "i8042.c: No controller found" -> OS sees no keyboard if I type "in BIOS" References: <4A0C232D.1020201@wpkg.org> <4A13CDC4.3000704@wpkg.org> <4A1405E1.70405@wpkg.org> <20090607040410.GA25831@amt.cnet> <4A2D1752.1080004@wpkg.org> <4A2D1C75.2040006@wpkg.org> <4A2D2743.4050501@redhat.com> In-Reply-To: <4A2D2743.4050501@redhat.com> 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: Avi Kivity Cc: Anthony Liguori , Marcelo Tosatti , qemu-devel@nongnu.org Avi Kivity wrote: >>> PS2_QUEUE_SIZE 256 was introduced in qemu-0.8.0. >> >> BTW, with "PS2_QUEUE_SIZE 16" I'm still able to trigger: >> >> i8042.c: No controller found. >> >> >> Only with "PS2_QUEUE_SIZE 15" keyboard is detected every time I boot >> the guest (unless that's what you meant by setting it to 16). >> > > I think this points to a bug in the bios. The keyboard-internal queue > size shouldn't cause any problems. It could be. That's something along the lines with what Vojtech Pavlik suggested[1]: 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. [1] http://lists.gnu.org/archive/html/qemu-devel/2009-05/msg00943.html -- Tomasz Chmielewski http://wpkg.org