From owner-freebsd-hardware  Mon Apr  1 09:05:51 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA06914
          for hardware-outgoing; Mon, 1 Apr 1996 09:05:51 -0800 (PST)
Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA06906
          Mon, 1 Apr 1996 09:05:48 -0800 (PST)
Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp
	(Smail3.1.29.1 #12) id m0u3nOw-000wyEC; Mon, 1 Apr 96 09:28 PST
Received: from cc:Mail by ccgate.infoworld.com
	id AA828378283; Mon, 01 Apr 96 09:31:58 PST
Date: Mon, 01 Apr 96 09:31:58 PST
From: "Brett Glass" <Brett_Glass@ccgate.infoworld.com>
Message-Id: <9603018283.AA828378283@ccgate.infoworld.com>
To: sos@FreeBSD.org
Cc: jkh@time.cdrom.com, hardware@FreeBSD.org
Subject: Re: Some solutions to disk problems.... I think.
Sender: owner-hardware@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> Aha! Have found some instructions for writing code that can be
>> incorporated into the kernel to solve the timeout problem.

What timeout problem ??
 
On this machine, a Zeos Pantera 486 "Rattler," the disk was retracting its
heads (and, sometimes, even spinning down!) during periods of inactivity.
FreeBSD's kernel threw a fit when it next tried to access the drive; the
console was covered with ugly messages warning of timeouts in the disk
routine, and everything hung for nearly 30 seconds.

Not a good way to respond to a "green" computer system, which is common
nowadays.

> Could you be a little more specific ??

See my followup.

--Brett