From owner-freebsd-stable Wed Dec 31 22:59:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA24517 for stable-outgoing; Wed, 31 Dec 1997 22:59:56 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from radford.i-plus.net (root@NS.i-Plus.net [208.24.67.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA24509 for ; Wed, 31 Dec 1997 22:59:53 -0800 (PST) (envelope-from rewt@i-Plus.net) Received: from b.nu (old@b.nu [208.24.67.58]) by radford.i-plus.net (8.8.8/8.8.5) with SMTP id BAA08948 for ; Thu, 1 Jan 1998 01:59:42 -0500 (EST) Message-ID: <00d601bd1683$d0f9ca80$3a4318d0@b.nu> From: "Troy Settle" To: "(ML) FreeBSD Stable" Subject: syscons bug Date: Thu, 1 Jan 1998 02:06:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk A few weeks ago, I posted a request for help with a 2.2.5-STABLE (mid to late Nov) problem involving a bug in the syscons driver that caused a reboot when switching vtys. Someone (one of the developers?) from Japan, I belive, asked me to apply a couple patches to revert syscons.c and syscons.h back to 2.2.5-RELEASE to see where the bug appeared. It took a while, but I finally found the time to try those patches, and it took both of them before I got a stable syscons driver. Just wanted to let the person know (I lost your email, sorry). Thanks for the fix, I hope this info helps you out. --Troy