Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 May 2011 11:47:33 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        Damjan Marion <damjan.marion@gmail.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: atkbdc broken on current ?
Message-ID:  <201105061147.33766.jhb@freebsd.org>
In-Reply-To: <BA80BDCA-AC38-487D-910D-1001316747B7@gmail.com>
References:  <5BEF0D0F-3717-42CE-ADF7-8876558004CA@gmail.com> <201105051343.02898.jhb@freebsd.org> <BA80BDCA-AC38-487D-910D-1001316747B7@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, May 05, 2011 5:04:54 pm Damjan Marion wrote:
> 
> On May 5, 2011, at 7:43 PM, John Baldwin wrote:
> 
> > 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: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
> >> 
> >> 9.0:
> >> 
> >> atkbdc0: <Keyboard controller (i8042)> 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?
> 
> Here it is:
> 
> http://web.me.com/dmarion/atkbdc.txt

Ohh, hmm.  Your BIOS has done "odd" things:

        isab0 pnpinfo vendor=0x1166 device=0x0201 subvendor=0x1166 subdevice=0x0201 class=0x060100 at slot=15 function=0 handle=\_SB_.PCI0.IBRG
          isa0
              I/O ports:
                  0x0-0xf
                  0x20-0x21
                  0x40-0x43
                  0x60
                  0x61
                  0x64
                  0x80-0x8f
                  0xa0-0xa1
                  0xc0-0xdf
                  0x4d6

Still, I don't know how the ISA bus is actually allocating resources.  Can
you add some code to the x86 nexus driver to drop into kdb when it receives
a SYS_RES_IOPORT allocation request from "isa0" and get a stack trace from
DDB and reply with the trace?

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201105061147.33766.jhb>