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 Subject: i386/1983: syscons fails/hangs during system boot if kbd offline Message-ID: <199611082210.OAA03098@base.jnx.com> Resent-Message-ID: <199611082220.OAA13747@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611082210.OAA03098>