From owner-freebsd-hackers Fri Oct 18 00:52:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA04309 for hackers-outgoing; Fri, 18 Oct 1996 00:52:34 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA04304 for ; Fri, 18 Oct 1996 00:52:29 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA10166 for ; Fri, 18 Oct 1996 09:51:25 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA12296 for freebsd-hackers@freebsd.org; Fri, 18 Oct 1996 09:51:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id JAA25957 for freebsd-hackers@freebsd.org; Fri, 18 Oct 1996 09:27:41 +0200 (MET DST) From: J Wunsch Message-Id: <199610180727.JAA25957@uriah.heep.sax.de> Subject: Re: 2.2-961006-SNAP keyboard lockup To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 18 Oct 1996 09:27:41 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610171704.LAA18599@rocky.mt.sri.com> from Nate Williams at "Oct 17, 96 11:04:29 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Nate Williams wrote: > I can also lockup vty switching by attempting to switch out of X before > it's completely initialized, which confuses the heck out of syscons. If This is an artifact of the way how VT switching in X11 is handled (the so-called ``process mode'' of the VT). The keyboard lockups are most likely bus arbitration failures for the keyboard bus. The keyboard bus has been designed to be uni-directional, and abused as a bi-directional bus later. There's no hardware support for an arbitration protocol, this is what makes it a fairly hard job to get it right. > it's any consolation, the *exact* same behavior occurs under SCO, so > syscons is doing a pretty good job of emulating both the good and bad > features of the SCO console driver. :) Btw., i've also seen SCO's jamming the keyboard of an HP Vectra (which is a _supported_ machine for SCO!) right at the first press of the CapsLock key. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)