From owner-freebsd-current@FreeBSD.ORG Thu May 5 17:43:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF580106564A for ; Thu, 5 May 2011 17:43:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 847878FC1E for ; Thu, 5 May 2011 17:43:04 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 38D9946B32; Thu, 5 May 2011 13:43:04 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CC1AA8A027; Thu, 5 May 2011 13:43:03 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 5 May 2011 13:43:02 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <5BEF0D0F-3717-42CE-ADF7-8876558004CA@gmail.com> In-Reply-To: <5BEF0D0F-3717-42CE-ADF7-8876558004CA@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105051343.02898.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 05 May 2011 13:43:03 -0400 (EDT) Cc: Damjan Marion Subject: Re: atkbdc broken on current ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 05 May 2011 17:43:04 -0000 On Thursday, May 05, 2011 9:21:04 am Damjan Marion wrote: > > Hi, > > I have issue with old HP DL380G3 server. When I use ILO virtual console to manage server. Seems that 9-CURRENT fails to detect atkbdc. > When I boot 8.2-RELEASE it works well. > > 8.2 dmesg shows: > > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > > 9.0: > > atkbdc0: failed to probe at port 0x60 on isa0 > > Is this a known issue? > > Should I enable some additional outputs, like KBDIO_DEBUG? I suspect this is a resource issue stemming from changes I made to the acpi(4) bus driver quite a while ago to make it use rman_reserve_resource(). Can you capture a full verbose dmesg from 9 along with devinfo -rv and devinfo -ur output from 9? -- John Baldwin