[5215] in linux-scsi channel archive
Re: Diamond Fireport 40 (Sym875)
daemon@ATHENA.MIT.EDU (Geert Uytterhoeven)
Thu Nov 26 04:13:57 1998
Date: Wed, 25 Nov 1998 23:34:49 +0100 (CET)
From: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
To: linux-scsi@vger.rutgers.edu
cc: linuxppc-dev@lists.linuxppc.org
In-Reply-To: <Pine.LNX.4.03.9811231138040.26529-100000@mercator.cs.kuleuven.ac.be>
On Mon, 23 Nov 1998, I wrote:
> I'm considering to buy a Diamond Fireport 40 (SYM53C875 based) UW-SCSI host
> adapter for my CHRP box (Linux/PPC). Are there known problems with this board
> on non-Intel architectures?
>
> Should I go for a SYM U2W-SCSI board instead? I have a Quantum Viking II U2W,
> which is currently connected to the (slow) onboard MESH Fast SCSI.
I borrowed a FirePort 40 from a friend for testing.
I have the following SCSI devices:
- QUANTUM VIKING II 4.5WLS Rev 3506 (U2W, with UW68-to-U50 convertor)
- HP HP35480A Rev T503
- QUANTUM FIREBALL_TM3200S Rev 300X (the one with tagged queueing bug ;-(
- PLEXTOR CD-ROM PX-12TS Rev 1.02
Originally these were all connected to the on-board MESH Fast-SCSI controller,
using a narrow cable, termination on the CD-ROM.
Since I had no wide cable for testing, I always used the Viking with the
UW68-to-U50 convertor, even on the '875.
The FirePort 40 is detected fine (kernel vger 2.1.129):
| ncr53c8xx: at PCI bus 0, device 5, function 0
| ncr53c8xx: attempting to force PCI_COMMAND_MASTER...succeeded.
| ncr53c8xx: attempting to force PCI_COMMAND_IO...succeeded.
| ncr53c8xx: attempting to force PCI_COMMAND_MEMORY...succeeded.
| ncr53c8xx: PCI_LATENCY_TIMER=0, bursting should'nt be allowed.
| ncr53c8xx: PCI_CACHE_LINE_SIZE not set, features based on CACHE LINE SIZE not used.
| ncr53c8xx: 53c875J detected
| ncr53c875J-0: rev=0x04, base=0xc1081000, io_port=0x1400, irq=30
| ncr53c875J-0: NCR clock is 40218KHz, 40218KHz
| ncr53c875J-0: ID 7, Fast-20, Parity Checking
| ncr53c875J-0: on-chip RAM at 0xc1082000
| ncr53c875J-0: restart (scsi reset).
| ncr53c875J-0: Downloading SCSI SCRIPTS.
| scsi0 : ncr53c8xx - revision 3.1b
Since I have to boot from the MESH (Open Firmware doesn't know about the '875),
I connected only the Viking to the FirePort. The Viking was identified
correctly, but then I got a lot of SCSI errors (sorry, I could capture the last
messages only):
| 6>ncr53c875J-0-<0,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=9
| ncr53c875J-0:0: ERROR (81:0) (6-a3-2) (10/9d) @ (scripth b90:48000000).
| ncr53c875J-0: script cmd = 785d8700
| ncr53c875J-0: regdump: da 10 00 9d 47 10 00 0f 06 06 80 a3 80 00 0b 00.
| ncr53c875J-0: have to clear fifos.
| ncr53c875J-0: restart (scsi reset).
| ncr53c875J-0: Downloading SCSI SCRIPTS.
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=1
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=9
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=1
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=1
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=9
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=9
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=1
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=1
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=9
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000000 SSTAT1=1
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| sda : READ CAPACITY failed.
| sda : status = 1, message = 00, host = 0, driver = 18
| sda : extended sense code = b
| sda : block size assumed to be 512 bytes, disk size 1GB.
| SCSI device sdb: hdwr sector= 512 bytes. Sectors= 6281856 [3067 MB] [3.1 GB]
| Partition check:
| sda:ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000200 SSTAT1=e
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000200 SSTAT1=e
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000200 SSTAT1=6
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000200 SSTAT1=e
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| ncr53c875J-0: SCSI parity error detected: SCR1=3 DBC=19000200 SSTAT1=6
| ncr53c875J-0: SCSI parity error detected: SCR1=1 DBC=19000000 SSTAT1=9
| ncr53c875J-0-<0,0>: 2 parity error(s).
| SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 18000002
| extra data not valid Current error sd08:00: sense key Aborted Command
| scsidisk I/O error: dev 08:00, sector 0
| unable to read partition table
| sdb: sdb1 sdb2 sdb3 sdb4
| VFS: Mounted root (ext2 filesystem) readonly.
| Freeing unused kernel memory: 92k init 32k prep 4k pmac
The Viking was the last drive on the chain. I tried playing with the
termination jumper (read: what I thought was the termination jumper, left my
specs somewhere else :-(, but to no avail. I connected a borrowed CD-Writer
(PLEXTOR CD-R PX-R412C Rev 1.04) with correct termination to the end of the
chain to make sure it was no termination problem, but that didn't help.
Then I removed the Viking from the chain, and everything worked fine. Could it
be that the cable was too long to use FAST-20 transfers with the Viking? It was
about 75 cm long.
/proc/scsi/ncr53c8xx/0 says:
| General information:
| Chip NCR53C875J, device id 0x8f, revision id 0x4
| IO port address 0x1400, IRQ number 30
| Synchronous period factor 12, max commands per lun 32
My config options:
| CONFIG_SCSI_NCR53C8XX=y
| CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
| CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
| CONFIG_SCSI_NCR53C8XX_SYNC=20
| # CONFIG_SCSI_NCR53C8XX_PROFILE is not set
| # CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
| # CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
Oops, now I see in README.ncr53c8xx that you can disable parity checking for
flawed devices. Is the Viking II known to be such a flawed device?
Well, I think this is sufficient success to justify buying a FirePort 40 :-)
Of course I do intend to connect the Viking II with a wide cable.
Thanks for reading this, and for your comments!
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP} http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
