From owner-freebsd-hackers Sun May 21 21:38:46 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA10858 for hackers-outgoing; Sun, 21 May 1995 21:38:46 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA10852 for ; Sun, 21 May 1995 21:38:45 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id AAA03138 for hackers@freebsd.org; Mon, 22 May 1995 00:41:17 -0400 From: Mark Hittinger Message-Id: <199505220441.AAA03138@ns1.win.net> Subject: Re: kern/430: bug in tape drivers (fwd) To: hackers@FreeBSD.org Date: Mon, 22 May 1995 00:41:17 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1155 Sender: hackers-owner@FreeBSD.org Precedence: bulk > >You get more than one "bt0: Try to abort" messages? That Yes, and they are repeated attempts to abort the rewind command I believe. > > More than one "bt0 Try to abort" means try to abort a previous abort > command. So I guess SCSI bus itself stuck up entirely. Check keep light > on borad LED or not. All disk i/o waits until the rewind finishes. Disk activity light is lit during entire rewind. Once rewind finishes then everything continues with no trouble. > > >I'm not sure what your work around does: you end up stretching out > >the "Try to abort" time until the drive finishes and "unlocks" > >the host adapter. So you've tried to abort a few transfers. Did they > >abort? I don't know. Do you wind up getting a disk retry per > >abort message after this? The workaround (a gross and sleazy kludge I admit :-) ) lets me do backups without bitspraying my disks! When I have time I want to open the hood on the timeout period calculations, it seems like timeouts happen faster than they ought to given the comments in the source. Maybe there are some pentium-90 incompatible assumptions. Regards, Mark Hittinger bugs@win.net