From owner-freebsd-mobile  Wed Oct 29 18:10:30 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA04808
          for mobile-outgoing; Wed, 29 Oct 1997 18:10:30 -0800 (PST)
          (envelope-from owner-freebsd-mobile)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA04803
          for <mobile@freebsd.org>; Wed, 29 Oct 1997 18:10:21 -0800 (PST)
          (envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
	by austin.polstra.com (8.8.7/8.8.7) with ESMTP id SAA04141;
	Wed, 29 Oct 1997 18:10:10 -0800 (PST)
	(envelope-from jdp)
Message-Id: <199710300210.SAA04141@austin.polstra.com>
To: Nate Williams <nate@mt.sri.com>
cc: mobile@freebsd.org
Subject: Re: Suspend/resume in -current: still no joy 
In-reply-to: Your message of "Wed, 29 Oct 1997 19:02:02 MST."
    <199710300202.TAA15796@rocky.mt.sri.com> 
Date: Wed, 29 Oct 1997 18:10:10 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Ahh, this is a 'known' bug.  Basically, the APM bios won't allow
> itself to powered down with the power on (for whatever reason), and
> because we don't handle the error condition (NO, I say I'm *NOT*
> going to supsend dammit!), we 'break'.  So, the moral of the story
> is, don't suspend unless the APM allows you to. :)

Ohhhhh.  I get it now.  Thanks, now I know how to avoid the problem.

John