Messages in this thread | | | Date | Wed, 10 Mar 1999 11:17:03 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | Re: Fujitsu MO 640 doesn't work with 2.2.2? |
| |
On Wed, 10 Mar 1999, Harvey Fishman wrote:
> On Wed, 10 Mar 1999, Serguei Koubouchine wrote: > > > The machine can be reliably crashed by writing to (or even reading lotta > > files from) the MO drive no matter whether it's plugged to the CDTxxxx or to > > a separate controller. No crashes when reading files from MO one-by-one with > > several seconds pause between reads. No crashes had been encountered on > > 2.2.0-pre6-ac2. Data corruption had been there since 2.1.129... > > I have seen that sort of behavior also with Adaptec chips (AIC-7870 and > AIC-7895). My solution has been to avoid wild-car writes. Happens with > my M2513a but I do ever remember seeing it happen with the M2512a. > > Harvey >
I suggest turning off disconnect as a start. Adaptec and BusLogic controllers have a BIOS menu. If this temporarily fixes the problem, you probably have a drive that negotiates for a sync speed that it can't possibly handle. Setting (forcing) the sync speed to be less than what it negotiated will usually fix this problem.
Target 0: Queue Depth 28, Wide Synchronous at 40.0 MB/sec, offset 15 Target 1: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset 15 Seagate ST34573W Disk, artifically reduced ^^^^^ Target 2: Queue Depth 28, Wide Synchronous at 40.0 MB/sec, offset 15 Target 3: Queue Depth 3, Synchronous at 5.00 MB/sec, offset 11 CDROM ^^^^^^ Target 4: Queue Depth 3, Synchronous at 4.00 MB/sec, offset 15 TAPE ^^^^^^
Cheers, Dick Johnson ***** FILE SYSTEM WAS MODIFIED ***** Penguin : Linux version 2.2.2 on an i686 machine (400.59 BogoMips). Warning : It's hard to remain at the trailing edge of technology.
- 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/
| |