From owner-freebsd-hackers Mon Nov 25 18:21:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA28518 for hackers-outgoing; Mon, 25 Nov 1996 18:21:00 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA28344; Mon, 25 Nov 1996 18:19:36 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id NAA20353; Tue, 26 Nov 1996 13:10:40 +1100 Date: Tue, 26 Nov 1996 13:10:40 +1100 From: Bruce Evans Message-Id: <199611260210.NAA20353@godzilla.zeta.org.au> To: jgreco@brasil.moneng.mei.com, sos@freebsd.org Subject: Re: Hang your machine with ScrollLock Cc: hackers@freebsd.org, mtaylor@cybernet.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > > As soon as I hit the scroll-lock key, everything was fine- >> > > all of the uptime processes completed, and name serving >> > > went on as usual. >> >> I belive this to be fixed in what was 2.2-current long ago... Nope. There is no bug to fix. Scroll lock says to stop output, so the tty buffer fills up after a while and the tty driver sleeps on "ttywri". Workaround: `comcontrol /dev/console drainwait 10' times out the sleep after 10 seconds. write() returns -1/EIO or a short count. Applications may be confused by this. EIO normally means hangup. Bruce