From owner-freebsd-current  Sun Jan 11 16:34:29 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA24497
          for current-outgoing; Sun, 11 Jan 1998 16:34:29 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from silverback.gorilla.net (silverback.gorilla.net [208.128.8.1])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA24488
          for <freebsd-current@freebsd.org>; Sun, 11 Jan 1998 16:34:21 -0800 (PST)
          (envelope-from tom@gorilla.net)
Received: from ygordial056.gorilla.net (ygordial056.gorilla.net [208.143.84.56]) by silverback.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id oa029706 for <freebsd-current@freebsd.org>; Sun, 11 Jan 1998 18:33:38 -0600
Received: (from tom@localhost)
	by gorilla.net (8.8.8/8.8.8) id SAA01561;
	Sun, 11 Jan 1998 18:33:47 -0600 (CST)
	(envelope-from tom)
Message-ID: <19980111183307.21448@TOJ.org>
Date: Sun, 11 Jan 1998 18:33:07 -0600
From: Tom Jackson <toj@silverback.gorilla.net>
To: FreeBSD Current <freebsd-current@freebsd.org>
Subject: pcvt keyboard buffer overflows
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Only on the source cvsup'd from the tenth do I get a keyboard
lockup with both the standard and slice kernel. Looked in
/var/log/messages and saw plenty of these. Can't really see
anything lately that should cause this. Kernel of the ninth
works fine.

Anyone seen this?

Tom