From owner-freebsd-bugs  Fri Nov  8 14:20:07 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA13776
          for bugs-outgoing; Fri, 8 Nov 1996 14:20:07 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA13747;
          Fri, 8 Nov 1996 14:20:04 -0800 (PST)
Resent-Date: Fri, 8 Nov 1996 14:20:04 -0800 (PST)
Resent-Message-Id: <199611082220.OAA13747@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org,
        Received:from.red.jnx.com.by.freefall.freebsd.org.with.ESMTP.id.OAA13134;Fri; (red.jnx.com [208.197.169.254]) (8.7.5/8.7.3);,
        8 Nov 1996 14:11:17.-0800 (PST)
Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id OAA16671; Fri, 8 Nov 1996 14:10:45 -0800 (PST)
Received: (from pst@localhost) by base.jnx.com (8.7.6/8.7.3) id OAA03098; Fri, 8 Nov 1996 14:10:44 -0800 (PST)
Message-Id: <199611082210.OAA03098@base.jnx.com>
Date: Fri, 8 Nov 1996 14:10:44 -0800 (PST)
From: pst@jnx.com
To: FreeBSD-gnats-submit@freebsd.org
Cc: bde@freebsd.org, sos@freebsd.org
X-Send-Pr-Version: 3.2
Subject: i386/1983: syscons fails/hangs during system boot if kbd offline
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         1983
>Category:       i386
>Synopsis:       syscons fails/hangs during system boot if kbd offline
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Nov  8 14:20:02 PST 1996
>Last-Modified:
>Originator:     Paul Traina
>Organization:
Juniper Networks
>Release:        FreeBSD 3.0-CURRENT i386
>Environment:

3.0-CURRENT (have seen this since at least the 10/28 release).
P5-133 and P6-200 machines
Syscons driver enabled.

>Description:

Syscons can be configured to operate whether or not a keyboard is present.
When I boot a system with syscons enabled, however the keyboard is not
currently plugged in (it's on a switch-box),  the syscons probe completes
successfully,  isa.c prints out the probe information, the system goes to
do a SC attach, which must hang or fail somehow, as the probe success
message is the last thing I see on the screen.

The system boots normally, however the keyboard/screen is no longer
usable.

I believe this problem may be related to the keyboard command (update leds)
code in syscons.

>How-To-Repeat:

Unplug your keyboard and reboot your system, see

sc0 at 0x60-0x6f irq 1 on motherboard

appear on your screen...followed by nothing.

Then telnet into the machine, login and see the rest of the kernel
output via dmesg:


sc0: VGA color <16 virtual consoles, flags=0x0>


>Fix:
	
Make syscons work properly when a keyboard is not present.
>Audit-Trail:
>Unformatted: