> I have been watching the reported problems with prepatch 9 and the bulk of
> them are related to this SCSI adapter. We use the Buslogic 958 controllers
> here and have been having great success with it. It seems from a cursory
> examination that the Adaptec 2940 driver problem is the only real show
> stopping bug reported thus far.
...
My system is unusable for backups with 2.0.31pre9. I haven't yet done
enough testing to narrow it down much.
The problem I get is (I can't quote, as the messages aren't logged, and
has scrolled off - I'll try to catch this someow) is scsi timeout while
accessing the SCSI tape drive. I think an access to the SCSI hard drive
triggers it. The "mt" process is stuck in the st driver, but I can still
access the SCSI tape drive.
I have tried both low level 53C810 drivers, and have increased by 10 the
timeouts in st.c, both with no evident affect.
Here is the tail end of the kernel messages:
+ 48 : dsa_next = 0x0
scsi0 target 2 : sxfer_sanity = 0x0, scntl3_sanity = 0x3
script : 0x78030300 0x0 0x78050000 0x0 0x90080000 0x0
0x0 0x0
scsi0 : saved data pointer at offset 0
scsi0 : active data pointer at offset 0
scsi0 : issue queue
scsi0 : schedule dsa array :
scsi0 : dsa at phys 0x119a080 (virt 0x0119a080)
+ 64 : dsa_msgout length = 31524324, data = 0x1e12218 (virt
0x01e12218)
+ 60 : select_indirect = 0xc0000004
+ 56 : dsa_cmnd = 0x0
+ 48 : dsa_next = 0x0
scsi0 : end schedule dsa array
scsi0 : reconnect_dsa_head :
scsi0 : end reconnect_dsa_head
The sti() implicit in a printk() prevents hangs
scsi0 : target 5 accepting asynchronous SCSI
scsi0 : setting target 5 to asynchronous SCSI
email charlieb@nlc.net.au
WWW http://www.nlc.net.au/~charlieb/