From owner-freebsd-mobile  Tue Oct 28 22:25:04 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA23756
          for mobile-outgoing; Tue, 28 Oct 1997 22:25:04 -0800 (PST)
          (envelope-from owner-freebsd-mobile)
Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA23744
          for <freebsd-mobile@FreeBSD.ORG>; Tue, 28 Oct 1997 22:25:00 -0800 (PST)
          (envelope-from handy@sag.space.lockheed.com)
Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM)
	id AA08991; Tue, 28 Oct 1997 22:24:59 -0800
Date: Tue, 28 Oct 1997 22:24:59 -0800 (PST)
From: "Brian N. Handy" <handy@sag.space.lockheed.com>
To: Satoshi Asami <asami@cs.berkeley.edu>
Cc: freebsd-mobile@FreeBSD.ORG, Nate Williams <nate@sri.mt.net>
Subject: Re: Real hackers run -current
In-Reply-To: <199710290408.UAA12369@silvia.HIP.Berkeley.EDU>
Message-Id: <Pine.OSF.3.96.971028222020.17778A-100000@sag.space.lockheed.com>
X-Files: The truth is out there
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-mobile@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 28 Oct 1997, Satoshi Asami wrote:

>I use 2.2-stable (of about a month ago) + PAO with a TP560E, and
>Alt-F12 (hybernation) works fine if I remove the 3c589D or Megahertz
>XJ1560.  It won't hybernate with either of them in there, so I just
>remove them temporarily, wait for a couple of heartbeats, type "sync",
>then Alt-F12.

Hmmm.  I was about to cheer you on to try Nate's diffs, but instead you've
got my interest up with the alt-F# stuff.  Are you running X when you do
this?  This is sort of a sideline, but I've always used 'zzz'.  I seem to
have the alt-f#'s wired down to do wierd things in X.

Anyway, I still maintain the latest changes seem to work pretty well.  I
have scored one hang -- I had my modem and enet card in, and popped them
out simultaneously.  This wedged the system pretty well!  (Not sure if it
was the combimation of the two, or if my ethernet card was in a wierd
state.)  The last thing I saw in the syslogs was something about slot 0
being unloaded.  Slot 1 never made it before things locked up tight.  (0
was the modem, 1 the ethernet card.)


Brian