From: John E. Stump (jstump@auntbea.austin.ibm.com)
Date: 01/19/93


From: jstump@auntbea.austin.ibm.com (John E. Stump)
Subject: new seagate patches
Date: Tue, 19 Jan 1993 15:52:56 GMT

I had a quick moment last night to test out the patches to the seagate
driver from Eric Y. to hopefully fix the ST-01 + Syquest rebooting
problem.

Halleluah! NO more reboots!! I was able to write and read from my
Syquest cartridge.

There were a few problems, though. I did the following:

$ mount /dev/sda1 /user
$ mount -t msdos /dev/fd0 /mnt
$ cp /mnt/* /user

This "seemed" to work, but I got a rash of messages like:

         "scsi0: unexpected interrupt."

This only happened when the cp was reading from the floppy. Strange.

Then I did the following disk intensive command:

$ cp --verbose --recursive /usr/* /user

This also seemed to work, but I saw a message like this pop up once:

"dumping sense buffer: 0 0 0 0 0 0 0 0 0 0 SCSI disk error: host 0 id 0 ..."

The rest of the message I didn't see because it scrolled off the screen
(I shouldn't have used --verbose).

Anyway, that was all the time I had to work with these new patches. I
didn't even have time to verify that all the files copied over were
correct, just a few I tested.

One other note: when the buffer cache is being flushed to the Syquest
(which takes awhile), the system is completely locked up; not even
keystrokes are echoed. I guess this means the seagate driver is not
interrupt driven?

Oh well, progress is being made and I can now use my Syquest. Thanks
Eric for your hunting down of this problem!!

my particulars:
        generic Intel 486SX-25
        8 MB RAM
        120 MB IDE
        40MB ST-01/Syquest drive
        stock .99pl3 w/ seagate.diff applied, on top of SLS .98 system

thanks y'all

john
(use my sig address for email, not the address in header)

-- 
John Stump (jstump@netftp.austin.ibm.com)