[3416] in linux-scsi channel archive
The Fujitsu M2513a driver is driving me crazy.
daemon@ATHENA.MIT.EDU (Harvey Fishman)
Fri Feb 27 22:38:09 1998
Date: Fri, 27 Feb 1998 22:35:25 -0500 (EST)
From: Harvey Fishman <fishman@panix.com>
To: linux-scsi@vger.rutgers.edu
I am not REALLY sure whether this is the appropriate list or linux-kernel
might be, but I'll try here first.
I recently upgraded from a Fujitsu M2512a MO drive (230 MB) to an M2513a
(640 MB), and I have been having a LOT of problems with the Linux driver.
I have an OLD (1994-95 era) Adaptec AHA-2940 host adapter with its
original 1.11 firmware. I am still using only 230 MB media.
The old drive worked flawlessly for over two years with all sorts of
kernel versions, but with the new drive I find that if I try to do a heavy
series of writes to the drive, I will invariably hang the SCSI bus and
require a BRS type of reboot. The box runs 95% of the time under NT and
there the drive runs flawlessly with similar exercise, so the problem does
not seem to be hardware. In addition to the MO, there are three fixed
disks and three CD-ROM readers on the SCSI bus. One end is terminated by
the host adapter and the other end is terminated by one of the CD-ROM
readers. The entire bus is 6 feet long, with the MO almost exactly in the
center. When I switched drives, it was just a case of taking the old one
out, untwisting the loop in the cable that the old drive required with its
backwards connector and dropping the new one into the same mount. NT was
happy and Linux seemed to be also. But then in the course of doing things
the trouble arose...
Another way to seem to bollix things up is to switch the logical console
in the midst of a long read access to the drive. This seems to just hang
the drive leaving the bus in working order, but the logical console that
was controlling the drive interaction is now hung. This also requires a
reboot to recover, but that can be done from the command line rather than
the switch. kill -9 of the process doing the read does nothing. kill -9
of the CLI of the hung process sometimes recovers, but this is spotty.
Anybody got any ideas for things that I could try to get more information
to either peg the problem on ME or to help others to find what might be in
the software to cause it? Thanks for all suggestions.
Harvey
--
----------------------------------------------------------------------------
Harvey Fishman |
fishman@panix.com | A little heresy is good for the soul.
718-258-7276 |
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
