[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 3.5-release console lockup



On Wed, May 05, 2004 at 06:23:01PM +0300, Alexey E. Suslikov wrote:
>     deraadt_(_at_)_i386_(_dot_)_openbsd_(_dot_)_org:/usr/src/sys/arch/i386/compile/GENERIC
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pms0 mux 0
> pckbcintr: no dev for slot 1

>     deraadt_(_at_)_i386_(_dot_)_openbsd_(_dot_)_org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0

It seems the problem is somehow related to your ps/2 mouse port. The
GENERIC kernel detects it and soon after spews a pckbcintr problem,
most likely disabling interrupts for the keyboard driver.

The RAMDISK_CD kernel will not mess with the ps/2 port and then seems
to work ok.

Perhaps you can try booting with the mouse unplugged, or if you don't
have a mouse disable that ps/2 port in the BIOS' setup.

HTH

-- 
  -= Fábio Olivé Leite  =-
  olive at unixforge . org
http://unixforge.org/~olive/



Visit your host, monkey.org