The following reply was made to PR port-amd64/34203; it has been noted by GNATS.

From: "=?ISO-8859-1?Q?St=E9phane_Witzmann?=" <stephane.witzmann@gmail.com>
To: gnats-bugs@netbsd.org, "Frank van der Linden" <fvdl@netbsd.org>
Cc: 
Subject: Re: port-amd64/34203: kbc: cmd word write error
Date: Tue, 15 Aug 2006 13:34:01 +0200

 On 8/15/06, Frank van der Linden <fvdl@netbsd.org> wrote:
 > The following reply was made to PR port-amd64/34203; it has been noted by
 > GNATS.
 >
 > From: Frank van der Linden <fvdl@netbsd.org>
 > To: gnats-bugs@NetBSD.org
 > Cc:
 > Subject: Re: port-amd64/34203: kbc: cmd word write error
 > Date: Tue, 15 Aug 2006 13:24:33 +0200
 >
 >  Is this an Acer laptop? I've seen this problem with an Acer laptop (but
 >  sadly don't have a fix for it right now).
 >
 >  - Frank
 
 The laptop is a brand new Fujitsu-Siemens AMILO with an AMD Turion 64x2 CPU.
 
 I'm trying to fix the bug. I can boot from a USB stick, so it is quite
 easy to try a custom kernel. Here is what I found:
 
 - other OSes (Linux, FreeBSD) work in their default configuration
 
 - If I add a panic() in main() before configure(), the keyboard works
 in DDB. There are some pckbc functions called before the copyright is
 printed, in consinit() I suppose, and none of them seems to fail.
 
 - The actual error (before "cmd word write error") is in
 pckbc_wait_output(), the backtrace at that time is:
 pckbc_wait_output()
 pckbc_put8042cmd()
 pckbc_attach()     /* set initial cmd byte */