From owner-freebsd-hardware Tue Aug 25 18:36:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17436 for freebsd-hardware-outgoing; Tue, 25 Aug 1998 18:36:00 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17431 for ; Tue, 25 Aug 1998 18:35:59 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id TAA18461; Tue, 25 Aug 1998 19:29:27 -0600 (MDT) Date: Tue, 25 Aug 1998 19:29:27 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808260129.TAA18461@narnia.plutotech.com> To: David Wolfskill cc: hardware@FreeBSD.ORG Subject: Re: SCSI bus timeouts Newsgroups: pluto.freebsd.hardware In-Reply-To: <199808251804.LAA23506@pau-amma.whistle.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199808251804.LAA23506@pau-amma.whistle.com> you wrote: > Any hints or tips welcomed. 1. Check your cables and termination on ahc0. You're getting parity errors and cables, or termination are the likely cause of these errors. 2. Switch to using CAM. sd1 is returning busy status maybe because it is doing a thermal recal (who knows). The old SCSI layer doesn't have the facilities to deal with a busy device gracefully, we end up beating on the drive hoping it will accept the command and we probably confuse it to the point of not working. The CAM patches are available at ftp://ftp.FreeBSD.org/pub/FreeBSD/cam. See the README file at that location for more details. > Thanks, > david > -- > David Wolfskill UNIX System Administrator > dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message