LKML Archive on
help / color / mirror / Atom feed
From: dean gaudet <>
To: Andy <>
Subject: Re: console scroll lock causes DOS
Date: Sun, 18 Feb 2007 20:58:15 -0800 (PST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20070207194137.GA25325@thumper2>

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 


      reply	other threads:[~2007-02-19  4:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 19:41 Andy
2007-02-19  4:58 ` dean gaudet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: console scroll lock causes DOS' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).