Re: regression in atkbd?

From: Brandon Gooch <jamesbrandongooch_at_gmail.com>
Date: Thu, 10 Sep 2009 09:09:54 -0500
On Wed, Jul 8, 2009 at 3:33 AM, Kevin Foo<chflags_at_gmail.com> wrote:
> Hi hackers,
>
> Did anyone experience issue with atkbd on 8.0? I encountered issue with
> keyboard and touchpad on HP presario V3400 when trying to upgrade from
> 7.2-RELEASE to 8.0 prior to and on BETA1.The keyboard and touchpad are
> working fine on 7.2. On 8.0 prior to BETA1, I managed to obtain dmesg via
> ssh despite having a non-operational keyboard. The laptop was totally
> inaccessible on 8.0 BETA1 as it freezed after the line atkbdc0. No
> information could be obtained.
>
> Any ideas? Thanks.
>
> /boot/device.hints (default, no changes made)
> hint.atkbdc.0.at="isa"
> hint.atkbdc.0.port="0x060"
> hint.atkbd.0.at="atkbdc"
> hint.atkbd.0.irq="1"
> hint.psm.0.at="atkbdc"
> hint.psm.0.irq="12"
>
> 1) FreeBSD 8.0-BETA1 amd64 as of today with GENERIC kernel:-
> <---snip---<
> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
> system hangs......
>
>
> 2) FreeBSD 8.0-CURRENT amd64 prior to BETA1 custom kernel without
> debug/invariant/witness:-
> <---snip---<
> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
> atkbd0: <AT Keyboard> irq 1 on atkbdc0
> atkbd: the current kbd controller command byte 0047
> atkbd: unable to set the command byte.
> kbd0 at atkbd0
> kbd0: atkbd0, generic (0), config:0x0, flags:0x3d0000
> ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 55
> atkbd0: [GIANT-LOCKED]
> atkbd0: [ITHREAD]
> psm0: unable to allocate IRQ
> psmcpnp0: <PS/2 mouse port> irq 12 on acpi0
> psm0: current command byte:0047
> psm0: unable to set the command byte.
> <---snip---<
> Full verbosed dmesg at http://ms.shit.la/FreeBSD/dmesg.8.txt
>
>
> 3) FreeBSD 7.2-RELEASE-p2 amd64:-
> <---snip---<
> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
> atkbd0: <AT Keyboard> irq 1 on atkbdc0
> atkbd: the current kbd controller command byte 0047
> atkbd: keyboard ID 0x41ab (2)
> kbd0 at atkbd0
> kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
> ioapic0: routing intpin 1 (ISA IRQ 1) to vector 57
> atkbd0: [GIANT-LOCKED]
> atkbd0: [ITHREAD]
> psm0: unable to allocate IRQ
> psmcpnp0: <PS/2 mouse port> irq 12 on acpi0
> psm0: current command byte:0047
> psm0: <PS/2 Mouse> irq 12 on atkbdc0
> ioapic0: routing intpin 12 (ISA IRQ 12) to vector 58
> psm0: [GIANT-LOCKED]
> psm0: [ITHREAD]
> psm0: model IntelliMouse, device ID 3-00, 3 buttons
> psm0: config:00000000, flags:00000008, packet size:4
> psm0: syncmask:08, syncbits:00
> <---snip---<
> Full verbosed dmesg at http://ms.shit.la/FreeBSD/dmesg.7.txt
>
> --
> Regards
> Kevin Foo
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>

What does your /boot/loader.conf look like?

I had a similar issue when:

1. booting GENERIC kernel but without debugging and WITNESS compiled in

and

2. my /boot/loader.conf contained the leftover entry 'ukbd_load="YES"'
from when I was using my custom, modular kernel

If either one of those or both was not true, I was able to boot as
usual. Strange. I never investigated any further...

-Brandon
Received on Thu Sep 10 2009 - 12:09:55 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:55 UTC