Date: Sun, 18 Feb 2007 20:58:15 -0800 (PST)
From: dean gaudet <dean@arctic.org>
To: Andy <genanr@emsphone.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: console scroll lock causes DOS
In-Reply-To: <20070207194137.GA25325@thumper2>
Message-ID: <Pine.LNX.4.64.0702182057120.12754@twinlark.arctic.org>
References: <20070207194137.GA25325@thumper2>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1109
Lines: 27

On Wed, 7 Feb 2007, Andy wrote:

> If the scroll lock is on and there is a bunch of console output, the machine
> will eventually stop responding to the network, until scroll lock is turned
> off (at sometimes that doesn't even help). 
> 
> Easy test:
> 
> hit scroll lock
> do a few echo t > /proc/sysrq-trigger on that machine from a ssh/telnet session
> and it should stop responding after two or three of them.
> 
> This is bad (for me) because we have a stupid switch box that uses scroll
> lock to bring up the system selection menu, so sometimes scroll lock gets
> left on by accident, and the machine eventually locks up.

something similar happens on serial console with hardware flow control if 
the other side goes away.  on some boxes i've wired special connectors 
with CTS=RTS to avoid this... mind you i haven't tested this problem in 
years.

-dean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/