Marc Collin wrote:
i have a tekram dc390f i use suse 9.1 (kernel 2.6)
with suse 8.0, 8.1, 8.2 and 9 i don't have this problem...
the problem happen with kernel 2.6...
i have a scsi hd on the 68-Pin Wide SCSI Internal port and a cdrom and burner scsi on my 50-Pin SCSI-2 Internal port
i get often sym0: SCSI parity error detected: SCR1=132 DBC=2440a04 SBCL=0 linux kernel: eth0: no IPv6 routers present linux kernel: sym0: SCSI parity error detected: SCR1=132 DBC=2440a04 SBCL=0 linux kernel: sym0:0: ERROR (81:0) (a-0-0) (f/9d/0) @ (memd136a328:ffffffff). linux kernel: sym0: regdump: da 00 40 9d 47 0f 00 0e 00 0a 80 00 80 00 0f 0a 30 30 71 1f 02 ff ff ff. linux kernel: sym0: SCSI BUS reset detected. linux kernel: sym0: SCSI BUS has been reset.
linux kernel: sym0: SCSI parity error detected: SCR1=132 DBC=50000000 SBCL=0 linux kernel: sym0:4:0: ABORT operation started. linux kernel: sym0:4:0: ABORT operation timed-out. linux kernel: sym0:6:0: ABORT operation started. linux kernel: sym0:6:0: ABORT operation timed-out. linux kernel: sym0:4:0: DEVICE RESET operation started. linux kernel: sym0:4:0: DEVICE RESET operation timed-out. linux kernel: sym0:6:0: DEVICE RESET operation started. linux kernel: sym0:6:0: DEVICE RESET operation timed-out. linux kernel: sym0:4:0: BUS RESET operation started. linux kernel: sym0: SCSI BUS reset detected. linux kernel: sym0: SCSI BUS has been reset. linux kernel: sym0:4:0: BUS RESET operation complete.
the bus reset often
Symbios/LSI Logic SCSI support seems to be flaky in all distros using 2.6 kernels, regardless which distro I've tried, SuSE, Fedora or Mandrake. I've seen stuff like the above with all 53c8xx chipped HBAs, but worse with faster ones than with 53c875 like I think you have. Maxtor drives are more trouble for me than IBM/Hitachi. Make sure your cabling and termination strictly meets spec. -- "[W]hoever finds me finds life....[A]ll who hate me love death." Proverbs 8:35-6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/