From owner-freebsd-smp Fri Aug 8 10:20:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29844 for smp-outgoing; Fri, 8 Aug 1997 10:20:43 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA29839; Fri, 8 Aug 1997 10:20:39 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id LAA06615; Fri, 8 Aug 1997 11:20:20 -0600 (MDT) Message-Id: <199708081720.LAA06615@pluto.plutotech.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Steve Kargl cc: jwd@unx.sas.com (John W. DeBoskey), freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: scsi time-out & lockup under smp In-reply-to: Your message of "Fri, 08 Aug 1997 09:34:30 GMT." <199708080934.JAA03485@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Aug 1997 17:20:12 +0000 From: "Justin T. Gibbs" Sender: owner-freebsd-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >It occurs on uni-processor system, too. If I use dump(1) to backup >my system, I eventually get the following: > >st0(ahc0:2:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Do you know if this occurs during the rewind or during some other operation during the backup. These types of problems, at least when a tape drive is the culprit, are almost always caused by one of the timeouts in the driver being too short. For instance, you may have hit a bad tape block and the timeout for reading a tape block is simply too short to deal with the drives attempts to retry the read. >-- >Steve > >finger kargl@troutmask.apl.washington.edu >http://troutmask.apl.washington.edu/~kargl/sgk.html -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================