From owner-freebsd-current Tue Nov 28 10:12:49 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA23494 for current-outgoing; Tue, 28 Nov 1995 10:12:49 -0800 Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA23478 for ; Tue, 28 Nov 1995 10:12:32 -0800 Received: (from scrappy@localhost) by hub.org (8.7.1/8.7.1) id NAA07482; Tue, 28 Nov 1995 13:10:26 -0500 (EST) Date: Tue, 28 Nov 1995 13:10:20 -0500 (EST) From: "Marc G. Fournier" To: Joerg Wunsch cc: Frank Durda IV , current@FreeBSD.org Subject: Re: Theory Failed: screen vs keyboard lock-up In-Reply-To: <199511280751.IAA09519@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Tue, 28 Nov 1995, J Wunsch wrote: > 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). > Oops, glad you reminded me of that...I had totally forgotten that it did do that :( I've been trying everyone's suggestions on how to see where the problem is too... But it still leaves us effectively nowhere. It happens with screen...it happens without screen... It happens with or without keyboard activity... It happens with or without a keyboard extendor... It happens with two different keyboards... And so far... I have yet to find it happen any more then randomly... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc