Hello,
some while ago I asked about the sym53c8xx driver doing the following
error and then endlessly looping with linux-2.[2|3].x with an iP133 on
a MSI-5128 mainboard
>sym53c875-0: Downloading SCSI SCRIPTS.
>sym53c875-0:0: ERROR (c0:0) (8-0-0) (0/5) @ (script 38:f3100004).
>sym53c875-0: script cmd = f31c0004
>sym53c875-0: regdump: ca 00 00 05 47 00 00 0e 71 08 00 00 80 00 08 02.
Unfortunately I still cannot say, why this happens but I can at least
state, that it's solved for me: I just bought a P-II-400, ASUS P3C-F,
128M of mem and a Matrox G400 and took the SCSI-Controllers,
harddrives, CD-ROM and CD recorder over from the old system.
Since then sym53c8xx runs perfectly in any version without showing any
strangeness. So I think the above problem was just caused by a bug in
the MSI's PCI-implementation/BIOS or one of the other three changed
components although this doesn't seem very likely to me.
Thanks for your help and time anyway and keep up the great work!
--
bye, Michael
Original message:
>Hello,
>
>please feel free to kick me if this is an FAQ but I searched all the
>documentation, list archives and source code to find something about
>the following issue.
>
>I got a iP133 on a MSI-5128 mainboard with 64MB of EDO-RAM. The PCI
>slots are filled by a Mystique 170 4MB, 3Com 905B-TX and two Symbios
>Logic SCSI conrollers. The first is an 8751SP (UltraWide-SCSI) and the
>other an 8750SP (Ultra-SCSI) but both got a SYM53C875 chip on board.
>The first one holds two IBM harddisks while the second serves the
>CD-ROM and CDR. Everything is running just fine with the ncr53c8xx
>driver.
>
>The problem arose when I tried to use the sym53c8xx driver which did
>nothing more than saying
>
>>sym53c8xx: at PCI bus 0, device 15, function 0
>>sym53c8xx: IO region 0x6200[0..127] is in use
>>sym53c8xx: at PCI bus 0, device 16, function 0
>>sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
>>sym53c8xx: 53c875 detected with Symbios NVRAM
>>sym53c875-0: rev=0x04, base=0xe1007000, io_port=0x6300, irq=9
>>sym53c875-0: Symbios format NVRAM, ID 7, Fast-20, Parity Checking
>>sym53c875-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/4e/80/01/00/24
>>sym53c875-0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/46/80/00/08/24
>>sym53c875-0: on-chip RAM at 0xe1008000
>>sym53c875-0: resetting, command processing suspended for 2 seconds
>>sym53c875-0: restart (scsi reset).
>>sym53c875-0: enabling clock multiplier
>>sym53c875-0: Downloading SCSI SCRIPTS.
>>sym53c875-0:0: ERROR (c0:0) (8-0-0) (0/5) @ (script 38:f3100004).
>>sym53c875-0: script cmd = f31c0004
>>sym53c875-0: regdump: ca 00 00 05 47 00 00 0e 71 08 00 00 80 00 08 02.
>>scsi1 : sym53c8xx - version 1.3g
>>scsi : 2 hosts.
>>sym53c875-0: command processing resumed
>>scsi : aborting command due to timeout : pid 29687, scsi1, channel 0, id 3, lun 0
>0x00 00 00 00 00 00
>>sym53c8xx_abort: pid=29687 serial_number=29688 serial_number_at_timeout=29688
>>sym53c875-0: abort ccb=c0eeb000 (cancel)
>>SCSI host 1 abort (pid 29687) timed out - resetting
>>SCSI bus is being reset for host 1 channel 0.
>>sym53c8xx_reset: pid=29687 reset_flags=2 serial_number=29688
>serial_number_at_timeout=29688
>>sym53c875-0: resetting, command processing suspended for 2 seconds
>>sym53c875-0: restart (scsi reset).
>>sym53c875-0: enabling clock multiplier
>>sym53c875-0: Downloading SCSI SCRIPTS.
>>sym53c875-0:0: ERROR (c0:0) (8-0-0) (0/5) @ (script 38:f3100004).
>>sym53c875-0: script cmd = f31c0004
>>sym53c875-0: regdump: ca 00 00 05 47 00 00 0e 71 08 00 00 80 00 08 02.
>>sym53c875-0: command processing resumed
>>SCSI host 1 abort (pid 29687) timed out - resetting
>>SCSI bus is being reset for host 1 channel 0.
>>sym53c8xx_reset: pid=29687 reset_flags=2 serial_number=29735
>serial_number_at_timeout=29735
>>sym53c875-0: resetting, command processing suspended for 2 seconds
>>sym53c875-0: restart (scsi reset).
>>sym53c875-0: enabling clock multiplier
>>sym53c875-0: Downloading SCSI SCRIPTS.
>>sym53c875-0:0: ERROR (c0:0) (8-0-0) (0/5) @ (script 38:f3100004).
>>sym53c875-0: script cmd = f31c0004
>>sym53c875-0: regdump: ca 00 00 05 47 00 00 0e 71 08 00 00 80 00 08 02.
>>sym53c875-0: command processing resumed
>>SCSI host 1 abort (pid 29687) timed out - resetting
>
>and looping forever between resetting the scsi channel and getting
>that SCSI script download error. I reproduced it with 2.2.5 through
>2.2.12 (same sym53c8xx driver version anyway IIRC). Unfortunately I'm
>too scared by eaten ext2fs's to test it with 2.3.x.
>
>To debug the issue I compiled ncr53c8xx support into the kernel and
>used kernel options to assign it the first controller. I then used a
>sym53c8xx module loaded on the second controller to test it with
>various options.
>
>Using this method I discovered that everything works just fine if
>master parity is disabled using for example 'modprobe sym53c8xx
>sym53c8xx="mpar:n"'.
>
>Hunting information on that issue I found some messages in the
>archives of linux-kernel explaining exactly what I'm experiencing. But
>those entirely speak about Alpha systems and no solutions were
>mentioned.
>
>So my questions are:
>1. Is there anyone out there having the same problem?
>2. Is it dangerous to run a system with master parity disabled?
>3. Is my mainboard's PCI implementation somewhat broken or is it in
>the driver? (ncr53c8xx runs perfectly with mpar:y!)
>
>Thanks for your time and sorry again if this has already been
>discussed.
>
>FYI here's what /proc says about my system when the sym53c8xx driver
>is loaded and running with mpar:n :
>
>/proc/scsi/scsi:
>>Attached devices:
>>Host: scsi0 Channel: 00 Id: 00 Lun: 00
>> Vendor: IBM Model: DCAS-34330W Rev: S65A
>> Type: Direct-Access ANSI SCSI revision: 02
>>Host: scsi0 Channel: 00 Id: 01 Lun: 00
>> Vendor: IBM Model: DCAS-34330W Rev: S65A
>> Type: Direct-Access ANSI SCSI revision: 02
>>Host: scsi1 Channel: 00 Id: 03 Lun: 00
>> Vendor: PLEXTOR Model: CD-ROM PX-32TS Rev: 1.03
>> Type: CD-ROM ANSI SCSI revision: 02
>>Host: scsi1 Channel: 00 Id: 05 Lun: 00
>> Vendor: YAMAHA Model: CRW4416S Rev: 1.0e
>> Type: CD-ROM ANSI SCSI revision: 02
>
>/proc/scsi/sym53c8xx/0:
>>General information:
>> Chip sym53c875, device id 0xf, revision id 0x4
>> IO port address 0x6200, IRQ number 11
>> Using memory mapped IO at virtual address 0xc4a08000
>> Synchronous period factor 12, max commands per lun 32
>
>/proc/scsi/sym53c8xx/1:
>>General information:
>> Chip sym53c875, device id 0xf, revision id 0x4
>> IO port address 0x6300, IRQ number 9
>> Using memory mapped IO at virtual address 0xc4a0c000
>> Synchronous period factor 12, max commands per lun 32
>--
>bye, Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
