Date: Tue, 28 Nov 1995 13:10:20 -0500 (EST) From: "Marc G. Fournier" <scrappy@hub.org> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: Frank Durda IV <uhclem%nemesis@fw.ast.com>, current@FreeBSD.org Subject: Re: Theory Failed: screen vs keyboard lock-up Message-ID: <Pine.BSF.3.91.951128130740.7163F-100000@hub.org> In-Reply-To: <199511280751.IAA09519@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.951128130740.7163F-100000>