Subject: Re: port-amd64/34203: kbc: cmd word write error
To: None <,,>
From: =?ISO-8859-1?Q?St=E9phane_Witzmann?= <>
List: netbsd-bugs
Date: 08/15/2006 20:25:01
The following reply was made to PR port-amd64/34203; it has been noted by GNATS.

From: "=?ISO-8859-1?Q?St=E9phane_Witzmann?=" <>
Cc: "Frank van der Linden" <>,
	"Jeremy C. Reed" <>,
	"Martin Husemann" <>
Subject: Re: port-amd64/34203: kbc: cmd word write error
Date: Tue, 15 Aug 2006 22:22:06 +0200

 On 8/15/06, St=E9phane Witzmann <> wrote:
 > By adding a panic() in the attach() function of the devices, I could
 > determine which one makes the keyboard stop working in DDB. And the
 > winner is: ohci. Disabling it makes the system boot with no keyboard
 > error.
 I found another way. GENERIC.MPACPI works fine, where GENERIC.MP and
 GENERIC fail. Only tested on i386. I suggest adding a boot-acpi.iso in
 the 4_BETA snapshots (i386 and amd64), since there is an INSTALL_ACPI
 kernel (at least on amd64).
 Should we also try to fix ohci so that it doesn't break anything
 without ACPI or just tell people to use ACPI-enabled kernels ? I'd
 choose the former if possible, but I'm no ACPI expert.