From owner-freebsd-mobile@FreeBSD.ORG  Fri Jun 13 12:39:14 2003
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 42CDC37B401
	for <freebsd-mobile@FreeBSD.org>;
	Fri, 13 Jun 2003 12:39:14 -0700 (PDT)
Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net
	[207.115.63.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9637943F75
	for <freebsd-mobile@FreeBSD.org>;
	Fri, 13 Jun 2003 12:39:13 -0700 (PDT)
	(envelope-from metrol@metrol.net)
Received: from metbsd.priv.metrol.net
	(adsl-67-121-60-13.dsl.anhm01.pacbell.net [67.121.60.13])
	h5DJdB3T016764;	Fri, 13 Jun 2003 15:39:12 -0400
From: Michael Collette <metrol@metrol.net>
To: Lukas Ertl <l.ertl@univie.ac.at>
Date: Fri, 13 Jun 2003 11:45:02 -0700
User-Agent: KMail/1.5.2
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306131145.02702.metrol@metrol.net>
cc: FreeBSD Mailing Lists <freebsd-mobile@FreeBSD.org>
Subject: Re: Thinkpad R40 apm fun on STABLE
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2003 19:39:14 -0000

Lukas Ertl wrote:

> On Fri, 13 Jun 2003, Michael Collette wrote:
> 
>> It's been putting up a bit of a fight with FreeBSD.  The biggest of my
>> glitches seems to be apm.  Oh sure, it'll go to sleep.  What it won't do
>> =
> is
>> wake up properly.  Upon waking you can see the LCD backlight kick on, a
>> little blinking on the HD light, then the HD light goes solid on.  At
>> thi=
> s
>> point the only recovery is a forced power down.
> 
> Are you sure the machine is locked up? Eventually, the laptop has hit a
> panic and the HD light just indicates that a core dump is written :-)
> 
> regards,
> le

I'm not entirely sure.  The light is lit, but I can't hear the drive spinning.  
Attempting to toggle caps lock has no effect, usually a pretty good lockup 
indicator.  No keystrokes impact anything.  Also, I've left it alone for 
upwards of 20 minutes without it recovering.

Initially I was thinking along the same lines as you're suggesting here.

Later on,
-- 
"Always listen to experts.  They'll tell you what can't be done, and why.  
Then do it."
- Robert A. Heinlein