Date: Fri, 2 Jan 1998 23:10:02 +1030 (CST) From: Peter Childs <pjchilds@imforei.apana.org.au> To: grog@lemis.com (Greg Lehey), freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.5 problems Message-ID: <199801021240.XAA22902@al.imforei.apana.org.au> In-Reply-To: <199712020023.QAA21293@bubba.whistle.com> <19971202150522.15474@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <19971202150522.15474@lemis.com> you wrote: >> Erm, not really - better to leave it in -questions until you're sure >> it's a bug. :) FWIW there was something in the freebsd-stable list that sounded somewhat similar... I'll include it here for reference. However it refered to switching some of the syscons stuff back to 2.2.5-RELEASE, which I believe was one of the machines you were having problems with.. Path: al.imforei.apana.org.au!chuckie.apana.org.au!news.apana.org.au!gateway From: rewt@i-Plus.net (Troy Settle) Newsgroups: apana.lists.os.freebsd.stable Subject: syscons bug Date: 1 Jan 1998 18:33:12 +1100 Organization: APANA mail-news gateway Lines: 18 Approved: news@apana.org.au Message-ID: <00d601bd1683$d0f9ca80$3a4318d0@b.nu> NNTP-Posting-Host: core.apana.org.au Xref: al.imforei.apana.org.au apana.lists.os.freebsd.stable:1143 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801021240.XAA22902>