Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Nov 1995 05:59:54 -0500 (EST)
From:      "Marc G. Fournier" <scrappy@hub.org>
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   kern/834: the console keyboard locks up randonly under pcvt
Message-ID:  <199511221059.FAA00304@hub.org>
Resent-Message-ID: <199511221110.DAA27072@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         834
>Category:       kern
>Synopsis:       the console keyboard locks up randonly under pcvt
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 22 03:10:03 PST 1995
>Last-Modified:
>Originator:     Marc G. Fournier
>Organization:
Knowledge, Information and Communications, Inc (ki.net)
>Release:        FreeBSD 2.1-STABLE i386
>Environment:

> dmesg
FreeBSD 2.1-STABLE #0: Sun Nov 19 20:12:40 EST 1995
    scrappy@hub.org:/usr/src/sys/compile/hub
CPU: i386DX (386-class CPU)
real memory  = 8650752 (8448K bytes)
avail memory = 7131136 (6964K bytes)
Probing for devices on the ISA bus:
pcvt: doreset() - got KEYB_R_RESEND response ... [one time only msg]
vt0 at 0x60-0x6f irq 1 on motherboard
vt0: tvga 9000, 80/132 col, color, 8 scr, mf2-kbd, [R3.20-b24]
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 not found at 0x2f8
lpt0 not found at 0xffffffff
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 765
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <Maxtor 7345 AT>
wd0: 329MB (675450 sectors), 790 cyls, 15 heads, 57 S/T, 512 B/S
aha0 at 0x330-0x333 irq 11 drq 5 on isa
aha0 waiting for scsi devices to settle
(aha0:0:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2
sd0(aha0:0:0): Direct-Access 327MB (670506 512 byte sectors)
npx0 on motherboard
npx0: 387 emulator

>Description:

Sometime early Wednesday morning (problem was noticed at 5:44am), the
console on my machine locked up.  When turning the screen on, the clock
that was present on my console was still ticking away, and was showing
5:44, indicating that the problem was completely within the keyboard
(nothing typed showed up on the screen)

Of note: it was working when I went to bed 2 hours earlier, and the 
         system continued to work.  If I had a terminal, I am 
         comfortable with assuming that I would have been able to login
         using it.

As is shown in the above dmesg, I am running pcvt, with the following
/etc/rc.i386 settings, which I got from a friend, who is using the
same settings:


#!/bin/sh -
#
#	rc.i386,v 1.9 1995/05/26 18:06:52 rgrimes Exp
#	Do i386 specific processing
#

echo -n 'enabling FreeBSD/i386 options:'
echo -n ' pcvt'

if [ -s /usr/share/misc/pcvtfonts/vt220l.808 -a \
     -s /usr/share/misc/pcvtfonts/vt220h.808 ] ; then
        loadfont -c 6 -f /usr/share/misc/pcvtfonts/vt220l.808
        loadfont -c 7 -f /usr/share/misc/pcvtfonts/vt220h.808
        for vty in /dev/ttyv* ; do
                scon -d $vty -s 50
                cursor -d $vty -s0 -e16
        done
fi
scon -c 1

echo '.'

>How-To-Repeat:

It does it randomly, sometimes within minutes of rebooting, somethings,
as is this case, after over a days uptime/usage.

>Fix:
	
	

>Audit-Trail:
>Unformatted:



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