(1) I had a system hang while reading a QIC-120 tape (co-inciding with the timeout shown below). Nov 12 20:02:54 linus /kernel: st0(aha0:4:0): MEDIUM ERROR info:11 field replaceable unit: 1 Nov 12 20:18:21 linus /kernel: st0(aha0:4:0): timed out The first error seems to be unrelated, since it didn't show up on subsequent attempts, but the problem occurs repeatably at the same place on the tape (about two thirds through). The tape error isn't a simple retry - the head shuffles about on the tape considerably. The tape wasn't written on this drive. (Could this be a tape drive problem?) On my third attempt I came out of X, and this time the system timed out and trapped into DDB ("adapter not taking commands.. frozen?!"). (2) The system doesn't like to be rebooted while the tape is rewinding; SCSI_DELAY=15 is nowhere near enough here! The system panics in the usual way after a SCSI timeout. Is this just because the probe isn't clever enough to delay talking to the SCSI device, or should it be able to find out what it needs from the device even while rewinding? How-To-Repeat: Happens at the same position on my tape each time.
As Mark Valentine wrote: > Nov 12 20:02:54 linus /kernel: st0(aha0:4:0): MEDIUM ERROR info:11 field replaceable unit: 1 This is clearly a problem with your tape (and/or drive). > Nov 12 20:18:21 linus /kernel: st0(aha0:4:0): timed out This looks like a subsequent problem in the driver (since your tape drive did lengthy attempts to recover from the above error). I've once been discussing the problems of adapter timeouts with Peter Dufault. I think we came to the conclusion to make something else than now, but i forgot what it was. :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Responsible Changed From-To: freebsd-bugs->gibbs Collect SCSI PRs in preparation for this summer's SCSI clean up. We still need a better method for dealing with timeouts for operations that can take a long time.
Is it safe to close this one? Responsible-Changed-From-To: freebsd-bugs->gibbs Responsible-Changed-By: gibbs Responsible-Changed-When: Sun Jun 23 22:02:14 PDT 1996 Responsible-Changed-Why: Collect SCSI PRs in preparation for this summer's SCSI clean up. We still need a better method for dealing with timeouts for operations that can take a long time.
As Studded wrote: > Is it safe to close this one? After CAM is in the tree, probably. ;-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
State Changed From-To: open->closed timed out, check again when CAM is here