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/

On Tue, 12 Oct 2004 09:39:58 -0500 Danny Sauer wrote:

...

SCSI parity errors are often indicative of improper SCSI termination, cable too long, or problems with a particular device. It is almost always a hardware problem.

SCSI FAQ entry #1:

q: I'm having a problem - any problem - with my SCSI devices. Why? a: Check termination, and maybe check cables.

--Danny, noting that nearly every problem traces back to termination :)

Pay attention to the messages shown on the console when you first boot your system. Typically, SCSI BIOSes will list their devices. If one or more SCSI devices do not show up, that is often a sign of improper SCSI termination or incorrect SCSI adapter settings. mikus

Marc Collin a écrit :

Le 12 Octobre 2004 11:59, Mikus Grinbergs a écrit :

...

On Tue, 12 Oct 2004 09:39:58 -0500 Danny Sauer

wrote:

...

...

...

SCSI parity errors are often indicative of improper SCSI termination, cable too long, or problems with a particular device. It is almost always a hardware problem.

SCSI FAQ entry #1:

q: I'm having a problem - any problem - with my SCSI devices. Why? a: Check termination, and maybe check cables.

--Danny, noting that nearly every problem traces back to termination :)

Pay attention to the messages shown on the console when you first boot your system. Typically, SCSI BIOSes will list their devices. If one or more SCSI devices do not show up, that is often a sign of improper SCSI termination or incorrect SCSI adapter settings.

mikus

all my scsi devices show up in the scsi bioes

Hello, I come in this discussion, in order to tell you that I got a similar problem with module sym53c8xx.ko when they switch from version 'i" (kernel 2.4 and early 2.6) to version "j". The error messages were not parity errors, but domain validation errors and the boot sequence was aborting. I used 2 different solutions before finding the reason : - 1° - I inserted the "i" sources and headers for scsi in the 2.6 kernel and it worked. - 2° - I patched the "j" release in order to stop domain validation end it worked. But I happened to change one of my old drives : a maxtor 72Gb hdd and release "j" works. Making some googling, I found that some people had problems with old drives. I suggest you to disconnect ( one by one) your drives and to check if the boot process succeeds. To be complete, I installed this old drive in my summer house with release "j", but with an adaptec scsi 29160 adaptor, and it works ! Michel. -- Michel et Catherine Garnier 4 résidence les chênes Le parc de Rocquencourt 78150 Rocquencourt Tel/Fax : + 33 (0)1 39 43 80 13 Email : Michel.R.Garnier@wanadoo.fr Catherine.F.Garnier@wanadoo.fr ICQ : 155138655