I'm unable to access my Seagate CTD-8000 DAT under 2.1.129/130/131.
Under 2.0.36 it works fine. The controller is an Adaptec AHA1542CF.
I set DEBUG=1 in st.c and recompiled. Here is the debugging info
Kai Makisara asks for in the README.st file:
On boot the driver writes:
st: Buffer size 32768 bytes, write threshold 30720 bytes.
st: Allocated tape buffer 0 (32768 bytes, 1 segments, dma: 1, a: c0ff8000).
st: segment sizes: first 32768, last 32768 bytes.
st: Allocated tape buffer 1 (32768 bytes, 1 segments, dma: 1, a: c0ff0000).
st: segment sizes: first 32768, last 32768 bytes.
When doing an 'mt setblk 0' I get:
st0: Block limits 1 - 16777215 bytes.
st0: Mode sense. Length 11, medium 31, WBS 90, BLL 8
st0: Density 13, tape length: 0, drv buffer: 1
st0: Block size: 512, buffer size: 32768 (64 blocks).
st0: Write protected
st0: Setting block size to 0 bytes.
In vt1, I started 'tar tvv', and in vt2 I type 'ps -l':
imladris:~# ps -l
FLAGS UID PID PPID PRI NI SIZE RSS WCHAN STA TTY TIME
COMMAND
100 0 66 1 1 0 1372 808 wait4 S 1 0:00 -bash
100 0 67 1 10 0 1372 808 R 2 0:00 -bash
100 0 68 1 0 0 1372 808 wait4 S 3 0:00 -bash
100 0 69 1 0 0 816 292 read_chan S 4 0:00
/sbin/age
100 0 70 1 0 0 816 292 read_chan S 5 0:00
/sbin/age
100 0 71 1 0 0 816 292 read_chan S 6 0:00
/sbin/age
0 0 90 66 1 0 936 332 stext_lock D 1 0:00 tar
tvv
100100 0 92 67 11 0 1064 352 R 2 0:00 ps -l
0 0 85 68 0 0 816 260 read_chan S 3 0:00 cat
imladris:~#
This is the kernel log:
st0: Block limits 1 - 16777215 bytes.
st0: Mode sense. Length 11, medium 31, WBS 90, BLL 8
st0: Density 13, tape length: 0, drv buffer: 1
st0: Block size: 0, buffer size: 32768 (1 blocks).
st0: Write protected
aha1542.c: Trying device reset for target 2
Sent BUS RESET to scsi host 0
st0: Error: 8000002, cmd: 8 0 0 28 0 0 Len: 10240
extra data not valid Current error st09:00: sense key Unit Attention
Additional sense indicates Power on, reset, or bus device reset occurred
st0: Sense: 70 0 6 0 0 0 0 a
st0: Tape error while reading.
At this point, the tape drive gets removed by the kernel, and I need
to reboot the box to get in contact with the DAT again.
I've spoken to Seagate Europe, and tried out their sgtape-s.exe test
program (under, shudder, Win95), and it reports the drive as working
correctly. Under Linux 2.0.36, the drive works like a charm.
Kai
--
Kai Harrekilde-Petersen <[EMAIL PROTECTED]> #include <std/disclaimer.h>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
