From owner-freebsd-scsi Tue Dec 15 18:20:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06221 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 18:20:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06216 for ; Tue, 15 Dec 1998 18:20:52 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA64842; Tue, 15 Dec 1998 19:20:32 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812160220.TAA64842@panzer.plutotech.com> Subject: Re: scsi error message In-Reply-To: <199812152353.IAA05913@net.kitel.co.kr> from swjeong at "Dec 16, 98 08:53:50 am" To: swjeong@net.kitel.co.kr (swjeong) Date: Tue, 15 Dec 1998 19:20:32 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org swjeong wrote... > > I am using 3.0-RELEASE. > I saw the following SCSI error message. > What is the reason? > I have properley terminated SCSI bus. > > # dmesg > > ... > > da5 at ahc0 bus 0 target 7 lun 0 > da5: Fixed Direct Access SCSI2 device > da5: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled > da5: 8347MB (17096357 512 byte sectors: 255H 63S/T 1064C) > > ... > > (da5:ahc0:0:7:0): tagged openings now 62 > (da5:ahc0:0:7:0): SCB 0x10 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR == 0x8 > SSTAT1 == 0xa > (da5:ahc0:0:7:0): Queuing a BDR SCB > (da5:ahc0:0:7:0): Bus Device Reset Message Sent > (da5:ahc0:0:7:0): no longer in timeout, status = 34b > ahc0: Bus Device Reset Sent. 62 SCBs aborted The "timed out while idle" message is caused by a device going "out to lunch" and not coming back on the bus. In this case, it probably means that we sent a transaction to the disk and it didn't return the transaction within 60 seconds. That drive, with the 71xx firmware revisions, is known to be more or less broken for tagged queueing. Since I see the tagged openings message, either one of two things has happened: - You have disabled the quirk entry in cam_xpt.c. - There's something wrong with the quirk entry or quirk entry mechanism, since it is reporting the number of outstanding tags. So, have you changed the quirk entry? There's one other odd, and possibly bad thing there. The above disk is on SCSI ID 7. That's generally the SCSI ID that the SCSI controller is on. What SCSI ID is your controller on? Can you send the full dmesg output from that machine? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message