From owner-freebsd-current  Wed Aug 16 11:22:39 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA19667
          for current-outgoing; Wed, 16 Aug 1995 11:22:39 -0700
Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id LAB19647
          for <current@freebsd.org>; Wed, 16 Aug 1995 11:22:30 -0700
Received: from localhost (localhost [127.0.0.1])
	  by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id TAA03719
	  for <current@freebsd.org>; Wed, 16 Aug 1995 19:22:13 +0100
X-Message: This is a dial-up site. Quick responses to e-mails should
           not be relied upon. Thanks!
To: current@freebsd.org
Subject: syscons
Date: Wed, 16 Aug 1995 19:22:12 +0100
Message-ID: <3717.808597332@palmer.demon.co.uk>
From: Gary Palmer <gary@palmer.demon.co.uk>
Sender: current-owner@freebsd.org
Precedence: bulk


Hi there

I've noticed some annoying behaviour form syscons. It seems to happen
when switching VTY's when there is output on the one you are switching
from happening around the same time.

Effects have varied from the cursor being in the wrong place to parts
of the screen not being updated (i.e. bits of the old VTY are still
visable).

Maybe this only happens on my old, slow, 486DX33, but I've noticed it
a couple of times in the last few days/weeks and it's annoying. I'm
running a recent kernel from the 2.1-STABLE branch.

Is this behaviour known about? Is there a cure?

Thanks

Gary