Subject: Re: SCSI timeouts too small for tapes
To: Michael VanLoon <mvanloon@MindBender.serv.net>
From: Matthew Jacob <firstname.lastname@example.org>
Date: 01/02/1999 09:15:15
The timeouts are in the tape driver. They have been regularized and
cleaned up in -current. I think (2 weeks ago is forever) that the original
problem was with 1.3.X.
On Sat, 2 Jan 1999, Michael VanLoon wrote:
> I know I regularly have problems like this with both Seagate/Archive
> DDS-2 and DDS-3 drives. I have similar but different problems when
> trying to use these drives with NetBSD on an ahc controller.
> -----Original Message-----
> From: Matthew Jacob <email@example.com>
> Date: Tuesday, December 15, 1998 8:16 PM
> >What tape drive?
> >On Tue, 15 Dec 1998, VaX#n8 wrote:
> >> When performing erase commands, I have noticed that the command exits
> >> two minutes into the erasing, no console logging is done, and then
> >when the
> >> drive actually completes, the NCR controller gives a SCSI phase error
> >> (CCB 0xdeadbeef already dequeued). Then the bus locks up.
> >> I assume that this is because of a hard-coded timeout.
> >> Is this a correct analysis?
> >> If so, where is the code located or how do I adjust it?
> >> At first I thought this was an electrical problem.
> >> It has caused me headaches for weeks.
> >> Similarly, if an offline command causes a rewind and then an eject
> >> if activity occurs on the bus between the rewind and eject, it
> >> locks up.