From owner-freebsd-current@FreeBSD.ORG  Wed Jun 18 21:15:02 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AD07637B401
	for <freebsd-current@freebsd.org>;
	Wed, 18 Jun 2003 21:15:02 -0700 (PDT)
Received: from postal1.es.net (postal1.es.net [198.128.3.205])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C2C2B43F85
	for <freebsd-current@freebsd.org>;
	Wed, 18 Jun 2003 21:15:01 -0700 (PDT)	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal1.es.net (Postal Node 1) with ESMTP (SSL) id MUA74016;
        Wed, 18 Jun 2003 21:15:00 -0700
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP
	id 64DC75D08; Wed, 18 Jun 2003 21:14:56 -0700 (PDT)
To: Darryl Okahata <darrylo@soco.agilent.com>
In-Reply-To: Message from Darryl Okahata <darrylo@soco.agilent.com> 
	<200306190025.RAA17828@mina.soco.agilent.com> 
Date: Wed, 18 Jun 2003 21:14:56 -0700
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20030619041456.64DC75D08@ptavv.es.net>
cc: freebsd-current@freebsd.org
Subject: Re: APM problem in 5.1-RELEASE 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jun 2003 04:15:03 -0000

One thing that jumps out at me on my T30 is that when I issue the S3,
the disk spins down instantly. Under APM it takes several seconds and
under Windows XP it also pauses bor a few (maybe 4) seconds.

I suspect it is powering down the disk as soon as the S3 is issued and
the write cache is never given an opportunity to flush. This may well
lead to resume getting into some really bad state regarding the disk.

On my system, this has led to corruption, at least. (I, perhaps
foolishly, run softupdate with write cache enebled.on my laptop. After
all, it is not likely to lose power unexpectedly.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634