>Number:         10316
>Category:       port-i386
>Synopsis:       wscons doesn't respond to keyboard events on 486PCI board
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 07 19:43:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     David Rankin
>Release:        NetBSD-1.4.2
>Organization:
	
>Environment:
	
System: NetBSD albert 1.4.2 NetBSD 1.4.2 (ALBERT) #0: Tue May 30 13:10:12 EDT 2000 root@hilda:/usr/src/sys/arch/i386/compile/ALBERT i386


>Description:
When booting with a wscons kernel, the OS will fail to respond to any and all
keyboard activities, including Caps Lock, Scroll Lock, and Num. Lock. This
occurs in 1.4.1, 1.4.2, and in current as of the last i386 snapshot.
This problem doesn't occur under the pc0 driver. (I have not tested the
vt0 driver) Please note that, in all cases, the system was a clean build
from the 1.4.1/1.4.2/snapshot boot disks (NOT an upgrade) to isolate /dev
issues.

The motherboard is a UUC 486PCI motherboard, MB-8433/40. It has the Award
BIOS V4.50 (2/17/95 - UMC - 891/886A-2A4X5B03-00). It is based on the UMC
UM8881F (?) Chipset, with (appearantly) a UMC keyboard chip.

Here is the dmesg output from a working (pc0) kernel:

NetBSD 1.4.2 (ALBERT) #0: Tue May 30 13:10:12 EDT 2000
    root@hilda:/usr/src/sys/arch/i386/compile/ALBERT
cpu0: Intel 486DX (486-class)
real mem  = 7995392
avail mem = 5648384
using 123 buffers containing 503808 bytes of memory
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o enabled, memory enabled
ncr0 at pci0 dev 13 function 0: ncr 53c825a fast10 wide scsi
ncr0: interrupting at irq 12
ncr0: minsync=25, maxsync=206, maxoffs=8, 128 dwords burst, large dma fifo
ncr0: single-ended, open drain IRQ driver, using on-chip SRAM
ncr0: restart (scsi reset).
scsibus0 at ncr0: 16 targets, 8 luns per target
st0 at scsibus0 targ 0 lun 0: <EXABYTE, EXB-8200, 263H> SCSI1 1/sequential removable
st0: rogue, drive empty
de0 at pci0 dev 14 function 0
de0: interrupting at irq 15
de0: ZNYX ZX312 21040 [10Mb/s] pass 2.4
de0: address 00:c0:95:ed:ac:6d
pchb0 at pci0 dev 16 function 0
pchb0: vendor 0x1060 product 0x8881 (rev. 0x01)
pcib0 at pci0 dev 18 function 0
pcib0: vendor 0x1060 product 0x886a (rev. 0x01)
isa0 at pcib0
aic0 at isa0 port 0x340-0x35f irq 11
scsibus1 at aic0: 8 targets, 8 luns per target
sd0 at scsibus1 targ 0 lun 0: <MICROP, 4110-09NB_Nov18F, TN0F> SCSI2 0/direct fixed
sd0: 1002MB, 2428 cyl, 9 head, 93 sec, 512 bytes/sect x 2053880 sectors
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
npx0 at isa0 port 0xf0-0xff: using exception 16
pc0 at isa0 port 0x60-0x6f irq 1: color
pc0: console
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
biomask 1840 netmask 9840 ttymask 9842
boot device: sd0
root on sd0a dumps on sd0b
WARNING: NVRAM century is 20 but RTC year is 1994
WARNING: clock time much less than file system time
WARNING: using file system time
WARNING: CHECK AND RESET THE DATE!
root file system type: ffs
de0: enabling 10baseT port

I will add a dmesg for a wscons kernel if requested, but there are no messages
within dmesg or at the console indicating error messages. Also, I am capable
of running compiled test kernels with diagnostic messages if needed.

>How-To-Repeat:
See above.
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: