From owner-freebsd-questions  Wed Jan  7 08:48:10 1998
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA13889
          for questions-outgoing; Wed, 7 Jan 1998 08:48:10 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA13448;
          Wed, 7 Jan 1998 08:42:03 -0800 (PST)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.5/8.8.5) id KAA06079;
	Wed, 7 Jan 1998 10:40:08 -0600 (CST)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199801071640.KAA06079@home.dragondata.com>
Subject: Re: Remote power cycle
In-Reply-To: <199801070955.BAA09833@implode.root.com> from David Greenman at "Jan 7, 98 01:55:53 am"
To: dg@root.com
Date: Wed, 7 Jan 1998 10:40:08 -0600 (CST)
Cc: bde@zeta.org.au, dpsmith@xoom.com, freebsd-questions@FreeBSD.ORG,
        freebsd-smp@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
>    The "BOOT_FORCE_COMCONSOLE" option was an option to building the
> bootblocks, not a kernel option, so I don't see how sio() flags has
> anything to do with it. That said, the option went away in 2.2, and
> now this is done with BOOT_COMCONSOLE_PORT, I guess. I haven't rebuilt
> the bootblocks since 2.1, so I didn't notice the change.
> 
> -DG
> 
> David Greenman
> Core-team/Principal Architect, The FreeBSD Project
> 

I'm also using the serial console to monitor machines, and remotely reboot
them when necessary. (I'm working on using X10 stuff to actually cycle power
for  me)

However, for now, even when the serial console is still running, but the
machine is  mostly dead, I can never get reboot to work... It tells me some
processess would not die, ps axl advised - then it locks up.

I've even tried reboot -q or reboot -n and got nowhere. Is there a better
way of recovering for this?

Kevin