From owner-freebsd-current Tue Nov 28 00:51:44 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA17494 for current-outgoing; Tue, 28 Nov 1995 00:51:44 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA17368 for ; Tue, 28 Nov 1995 00:49:22 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA28041; Tue, 28 Nov 1995 09:16:13 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA19189; Tue, 28 Nov 1995 09:16:12 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id IAA09519; Tue, 28 Nov 1995 08:51:51 +0100 From: J Wunsch Message-Id: <199511280751.IAA09519@uriah.heep.sax.de> Subject: Re: Theory Failed: screen vs keyboard lock-up To: uhclem%nemesis@fw.ast.com (Frank Durda IV) Date: Tue, 28 Nov 1995 08:51:51 +0100 (MET) Cc: current@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Frank Durda IV" at Nov 27, 95 10:14:00 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 621 Sender: owner-current@FreeBSD.org Precedence: bulk As Frank Durda IV wrote: > > You could effectively cause the lockup to happen by rapidly changing > between screens that had updates occuring on them, such as "ls -alR /" > on a couple of screens, then toggle between them. That appears to be the "set LEDs" lockup (collision between input and output data streams on the serial keyboard line). The originator of this problem report however experienced a lockup while _nothing_ was going (during the night). -- 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. ;-)