On Mon, Feb 14, 2000 at 08:31:46PM +0200, Gadi Oxman wrote:
> The trace below shows that the driver is waiting in an ioctl() for
> a completion of a mt command.
Ah, I did grovel through the source and come to that conclusion as well (I
wasn't thinking very clearly yesterday <g>)
> Which command were you running? After how much time from the
> mt command was the panic triggered?
>
> If this was a retension command, for example, it can take up to 10
> minutes in some tape drives. If the default timeout in ikd is lower
> than that, it explains the panic.
It was an MTEOM command, and without the deadlock detection it just blocks for
ages (tens of minutes), with no tape drive activity; the problem seems to
manifest itself when it's executed right after an MTWEOF (which is a bit of a
silly thing to do, I know...). It's an HP Colorado 8Gb drive (i.e. 4Gb <g>) --
is it possible that it's a bug / feature in the drive firmware?
Apart from that, the driver seems to work great though..
Cheers,
Steve
-- Steve Dodd, Network Adminstrator, WotNot Ltd.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:29 EST