From owner-freebsd-current  Sat May 17 11:38:12 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA05823
          for current-outgoing; Sat, 17 May 1997 11:38:12 -0700 (PDT)
Received: from dfw-ix9.ix.netcom.com (dfw-ix9.ix.netcom.com [206.214.98.9])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05818
          for <current@FreeBSD.ORG>; Sat, 17 May 1997 11:38:08 -0700 (PDT)
Received: (from smap@localhost)
          by dfw-ix9.ix.netcom.com (8.8.4/8.8.4)
	  id NAA00777; Sat, 17 May 1997 13:37:36 -0500 (CDT)
Received: from sjx-ca85-08.ix.netcom.com(207.94.112.168) by dfw-ix9.ix.netcom.com via smap (V1.3)
	id sma000766; Sat May 17 13:37:27 1997
Received: (from asami@localhost) by blimp.mimi.com (8.8.5/8.6.9) id LAA10939; Sat, 17 May 1997 11:37:23 -0700 (PDT)
Date: Sat, 17 May 1997 11:37:23 -0700 (PDT)
Message-Id: <199705171837.LAA10939@blimp.mimi.com>
To: gibbs@plutotech.com
CC: current@FreeBSD.ORG
In-reply-to: <199705171246.GAA26748@pluto.plutotech.com> (gibbs@plutotech.com)
Subject: Re: ahc error
From: asami@vader.cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * Looks to me like your drive decided to spin down for some strange
 * reason.  It shouldn't do so simply because the aic7xxx driver decided
 * to send it an abort tag request when a pending transaction didn't return.
 * My guess is that the spin down caused the initial timeout.  Smells like a
 * hardware, not software problem.

I see.  I guess it's just the murphy's law at work (I've been pounding
this drive the past few weeks but not for package building)....

Satoshi