From owner-freebsd-current  Thu Sep 12 19:02:28 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA20224
          for current-outgoing; Thu, 12 Sep 1996 19:02:28 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA20217
          for <freebsd-current@freebsd.org>; Thu, 12 Sep 1996 19:02:21 -0700 (PDT)
Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.6/8.7.3) id MAB03971; Fri, 13 Sep 1996 12:02:09 +1000
Received: by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a)
	id MAA14019; Fri, 13 Sep 1996 12:04:59 +1000 (EST)
Date: Fri, 13 Sep 1996 12:04:59 +1000 (EST)
From: Stephen McKay <syssgm@devetir.qld.gov.au>
Message-Id: <199609130204.MAA14019@ogre.devetir.qld.gov.au>
To: Peter Childs <pjchilds@imforei.apana.org.au>
cc: freebsd-current@freebsd.org
Subject: Re: VM problems (still)
X-Newsreader: NN version 6.5.0 #1 (NOV)
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Peter Childs <pjchilds@imforei.apana.org.au> wrote:

> Also, i'm not sure if this would be an easy one to fix, but with 
> the panic calls they don't reset the video mode, so in X
> you just get _hung_ ...

I've been using a serial console for a little while now for just this reason.
Plug a 9600bps terminal (or another PC) into COM1 using a crossover cable,
type -h to your FreeBSD boot prompt, and it all just happens.  You might
have to move your mouse, but I'm sure you can work that out.

Stephen.