From owner-freebsd-current@FreeBSD.ORG Wed Apr 13 08:10:54 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEC4716A500; Wed, 13 Apr 2005 08:10:54 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EBF143D31; Wed, 13 Apr 2005 08:10:53 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) (8.13.4/8.13.3) with ESMTP id j3D8Ao0F077076 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 13 Apr 2005 10:10:50 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id j3D8AoWJ077075; Wed, 13 Apr 2005 10:10:50 +0200 (CEST) Date: Wed, 13 Apr 2005 10:10:50 +0200 From: Divacky Roman To: John Baldwin Message-ID: <20050413081050.GA76859@stud.fit.vutbr.cz> References: <20050406130909.GA90294@stud.fit.vutbr.cz> <200504112038.32964.jhb@FreeBSD.org> <20050412073810.GA89527@stud.fit.vutbr.cz> <200504121253.50950.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200504121253.50950.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 cc: current@freebsd.org Subject: Re: slow kbd input on 6-current on amd64@nforce3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 08:10:55 -0000 On Tue, Apr 12, 2005 at 12:53:50PM -0400, John Baldwin wrote: > On Tuesday 12 April 2005 03:38 am, Divacky Roman wrote: > > On Mon, Apr 11, 2005 at 08:38:32PM -0400, John Baldwin wrote: > > > On Wednesday 06 April 2005 09:09 am, Divacky Roman wrote: > > > > as I have mentioned on the list I have very slow keyboard input. it > > > > might be related to kbd not having an IRQ assigned. I repeat once again > > > > that it worked on 5.3R. > > > > > > Actually, now that I look at this, you have a buggy BIOS. It is lying > > > and claiming that some PCI interrupts are active-hi rather than > > > active-low. Hmm, the 5.3 dmesg you gave me included APIC, while this one > > > does not. Does disabling ACPI make your keyboard happy on 6.0 by chance? > > > > It doesnt boot with acpi enabled (stops in probing ata devices, but it > > never worked so I think ata is not the only culprit) > > Ok. > > > what can I do with it? would some quirk made the trick? why it worked in > > 5.3R? > > I don't know at this point. Does 6.0 in any configuration work ok? > (ACPI !APIC, ACPI APIC, !ACPI APIC, !ACPI !APIC) it doesnt boot with ACPI which eliminates first two cases, and I tried all combinations of # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) device atpic # 8259A compatability options NO_MIXED_MODE # Don't penalize working chipsets and none worked... ie. I think it eliminates later two cases you said the logic of active interrupts is reverted. where in the code can I revert this? I'll try it and if it works I can define some quirk... thnx for answer roman