From owner-freebsd-current Sat May 17 05:46:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA22785 for current-outgoing; Sat, 17 May 1997 05:46:56 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA22780 for ; Sat, 17 May 1997 05:46:54 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id GAA26748; Sat, 17 May 1997 06:46:52 -0600 (MDT) Message-Id: <199705171246.GAA26748@pluto.plutotech.com> To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: current@FreeBSD.ORG Subject: Re: ahc error In-reply-to: Your message of "Sat, 17 May 1997 03:09:47 PDT." <199705171009.DAA03196@blimp.mimi.com> Date: Sat, 17 May 1997 07:45:28 -0600 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I was trying to build packages (on a 2.2.2 machine), and just got this >from one of the ccd'd disks: > >=== >sd13(ahc2:12:0): NOT READY asc:4,2 >sd13(ahc2:12:0): Logical unit not ready, initializing command required >, retries:3 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. >Satoshi -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================