Date: Mon, 20 Jun 2011 01:05:04 +0200 From: Damjan Marion <damjan.marion@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: atkbdc broken on current ? Message-ID: <27649E5F-4EEC-4796-ACC6-5548780BF825@gmail.com> In-Reply-To: <201106171721.50686.jhb@freebsd.org> References: <5BEF0D0F-3717-42CE-ADF7-8876558004CA@gmail.com> <BA80BDCA-AC38-487D-910D-1001316747B7@gmail.com> <201105061147.33766.jhb@freebsd.org> <201106171721.50686.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 17, 2011, at 11:21 PM, John Baldwin wrote: > On Friday, May 06, 2011 11:47:33 am John Baldwin wrote: >> On Thursday, May 05, 2011 5:04:54 pm Damjan Marion wrote: >>>=20 >>> On May 5, 2011, at 7:43 PM, John Baldwin wrote: >>>=20 >>>> On Thursday, May 05, 2011 9:21:04 am Damjan Marion wrote: >>>>>=20 >>>>> Hi, >>>>>=20 >>>>> I have issue with old HP DL380G3 server. When I use ILO virtual = console to=20 >>>> manage server. Seems that 9-CURRENT fails to detect atkbdc. >>>>> When I boot 8.2-RELEASE it works well. >>>>>=20 >>>>> 8.2 dmesg shows: >>>>>=20 >>>>> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on = acpi0 >>>>>=20 >>>>> 9.0: >>>>>=20 >>>>> atkbdc0: <Keyboard controller (i8042)> failed to probe at port = 0x60 on isa0 >>>>>=20 >>>>> Is this a known issue? >>>>>=20 >>>>> Should I enable some additional outputs, like KBDIO_DEBUG? >>>>=20 >>>> I suspect this is a resource issue stemming from changes I made to = the acpi(4)=20 >>>> 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=20 >>>> output from 9? >>>=20 >>> Here it is: >>>=20 >>> http://web.me.com/dmarion/atkbdc.txt >>=20 >> Ohh, hmm. Your BIOS has done "odd" things: >>=20 >> isab0 pnpinfo vendor=3D0x1166 device=3D0x0201 subvendor=3D0x1166= subdevice=3D0x0201 class=3D0x060100 at slot=3D15 function=3D0 = handle=3D\_SB_.PCI0.IBRG >> isa0 >> I/O ports: >> 0x0-0xf >> 0x20-0x21 >> 0x40-0x43 >> 0x60 >> 0x61 >> 0x64 >> 0x80-0x8f >> 0xa0-0xa1 >> 0xc0-0xdf >> 0x4d6 >>=20 >> 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? >=20 > So I think I just found the explanation for this and I think the = change I > just committed will fix your system: >=20 > Author: jhb > Date: Fri Jun 17 21:19:01 2011 > New Revision: 223207 > URL: http://svn.freebsd.org/changeset/base/223207 Hi John, sorry for not coming back to you on your previous email, it was on my = todo list but I haven't time to do it. I tried now new kernel and it works well. Thanks for fixing this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27649E5F-4EEC-4796-ACC6-5548780BF825>