[6231] in linux-scsi channel archive
Re: new ncr/sym53c8xx driver tree at tux
daemon@ATHENA.MIT.EDU (Gerard Roudier)
Wed Mar 31 14:35:23 1999
Date: Wed, 31 Mar 1999 20:11:52 +0200 (MET DST)
From: Gerard Roudier <groudier@club-internet.fr>
To: Matthew Jacob <mjacob@feral.com>
cc: linux-scsi@vger.rutgers.edu, ncr53c810@Colorado.EDU
In-Reply-To: <Pine.LNX.4.04.9903301122150.30672-100000@feral-gw>
> scsi : aborting command due to timeout :
> pid 54, scsi2, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00
The failure occurs on the first TEST_UNIT_READY sent to a device of this
SCSI BUS. That is simply strange, since the device should be quick at
responding, and this command does not need any DATA PHASE.
At this step, the driver does not try to negotiate anything and the SCSI
BUS has just been reset, so the failure seems double-strange to me.
And The fact that the first 875 just succeeds makes your problem appear
triple-strange to me. ;-)
> ncr53c876-1: rev=0x14, base=0x1ff80014000,
> io_port=0xfffff9fe02010c00, irq=6,7dc
> ncr53c876-2: rev=0x14, base=0x1ff80016000,
> io_port=0xfffff9fe02011000, irq=6,7dc
The both functions of the 876 report same IRQ thing that probably means
that they are sharing this thing.
In the Solaris boot-up messages, I donnot see what PCI ressources have
been assigned to the PCI devices. Were they the same ones ?
If I had to guess, I would think that some interrupt that should go
to the driver has just been lost prior to calling the driver interrupt
routine.
Could you for example, boot your system with an option that excludes one
of the 876 functions, a follow:
ncr53c8xx=excl:#io_address
Replace #io_address by the corresponding 0xffffff################ of
one function that seems as real an io address as Windows/NT is an O/S ;-)
You can exclude more than 1 controller, using
ncr53c8xx=excl:#io1,excl:#io2
You also could give a try with the other driver (sym53c8xx) that can be
configured independantly as either dynamically loadable module or
statically linked to the kernel, but only shares some CONFIG defines with
the other driver.
There is also some README.ncr53c8xx file that is not excellent english but
contains some informations, especially on boot options, as debug ones.
This file is also intended to help users refining diagnostics before
reporting problems.
With the informations you provide, I am not able to tell you more about
your problem.
Gérard.
On Tue, 30 Mar 1999, Matthew Jacob wrote:
> I went to the effort to snag this patch because I was having troubles with
> a card.... no change...
>
>
> Ultra30, 2.2.5-pre (sparc cvs repository)... your
> patch patch-53c8xx-s01-d00-2.2.3.gz applied...
>
> Card in question works absolutely fine in same configuration for Solaris 2.7.
>
> Boot device: /pci@1f,4000/scsi@3/disk@3,0 File and args: test
> SILO
> Uncompressing image...
> /
> Booting Linux...
> PROMLIB: Sun IEEE Boot Prom 3.9.5 1997/04/11 10:03
> Linux version 2.2.5 (mjacob@slinx.feral.com) (gcc version egcs-2.92.11 19980921 (gcc2 ss-980609 experimental)) #7 Tue Mar 30 10:54:11 PST 1999
> ARCH: SUN4U
> Ethernet address: 08:00:20:82:62:f3
> Calibrating delay loop... 591.46 BogoMIPS
> Memory: 191536k available (1240k kernel code, 2888k data, 112k init) [fffff80000000000,fffff80023f32000]
> POSIX conformance testing by UNIFIX
> PCI: Probing for controllers.
> PCI: Found PSYCHO version 0x3, main regs at fffff9fe00000000
> PSYCHO: PCI config space at fffff9fe01000000
> PCI: Probing PCI hardware
> ebus0: fffff9fff0000000[1000000] fffff9fff1000000[800000]
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> Starting kswapd v 1.5
> SAB82532 serial driver version 1.30
> ttyS00 at 0xfffff9fff1400000 (irq = 12,7eb) is a SAB82532 V3.2
> ttyS01 at 0xfffff9fff1400040 (irq = 12,7eb) is a SAB82532 V3.2
> Console: ttyS0 (SAB82532)
> pty: 256 Unix98 ptys configured
> md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
> ncr53c8xx: at PCI bus 0, device 3, function 0
> ncr53c8xx: 53c875 detected
> ncr53c8xx: at PCI bus 0, device 5, function 0
> ncr53c8xx: 53c876 detected
> ncr53c8xx: at PCI bus 0, device 5, function 1
> ncr53c8xx: 53c876 detected
> ncr53c875-0: rev=0x03, base=0x1ff80010000, io_port=0xfffff9fe02010400, irq=3,7e0
> ncr53c875-0: NCR clock is 40218KHz, 40037KHz
> ncr53c875-0: ID 7, Fast-20, Parity Checking
> ncr53c875-0: on-chip RAM at 0x1ff80011000
> ncr53c875-0: restart (scsi reset).
> ncr53c875-0: Downloading SCSI SCRIPTS.
> ncr53c876-1: rev=0x14, base=0x1ff80014000, io_port=0xfffff9fe02010c00, irq=6,7dc
> ncr53c876-1: NCR clock is 40218KHz, 40037KHz
> ncr53c876-1: ID 7, Fast-20, Parity Checking
> ncr53c876-1: on-chip RAM at 0x1ff80015000
> ncr53c876-1: restart (scsi reset).
> ncr53c876-1: Downloading SCSI SCRIPTS.
> ncr53c876-2: rev=0x14, base=0x1ff80016000, io_port=0xfffff9fe02011000, irq=6,7dc
> ncr53c876-2: NCR clock is 40218KHz, 40037KHz
> ncr53c876-2: ID 7, Fast-20, Parity Checking
> ncr53c876-2: on-chip RAM at 0x1ff80017000
> ncr53c876-2: restart (scsi reset).
> ncr53c876-2: Downloading SCSI SCRIPTS.
> scsi0 : ncr53c8xx - version 3.2
> scsi1 : ncr53c8xx - version 3.2
> scsi2 : ncr53c8xx - version 3.2
> scsi : 3 hosts.
> Vendor: IBM Model: DORS32160SUN2.1G Rev: WA7A
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> Vendor: IBM Model: DORS32160SUN2.1G Rev: WA4H
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
> Vendor: SEAGATE Model: ST32550N Rev: 0022
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdc at scsi0, channel 0, id 3, lun 0
> ncr53c875-0-<0,0>: tagged command queue depth set to 4
> ncr53c875-0-<1,0>: tagged command queue depth set to 4
> ncr53c875-0-<3,0>: tagged command queue depth set to 4
> scsi : aborting command due to timeout : pid 54, scsi2, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00
> ncr53c8xx_abort: pid=54 serial_number=82 serial_number_at_timeout=82
> (hangs here)
>
>
> Solaris boot messages (excerpt):
>
> mem = 195864K (0xbf46000)
> avail mem = 177209344
> Ethernet address = 8:0:20:82:62:f3
> root nexus = Sun Ultra 30 UPA/PCI (UltraSPARC-II 296MHz)
> pci108e,80000 at root: UPA 0x1f 0x4000
> pci108e,80001 at root: UPA 0x1f 0x2000
> glm0: Rev. 3 Symbios 53c875 found.
> PCI-device: scsi@3, glm #0
> glm0 is /pci@1f,4000/scsi@3
> glm3: Rev. 4 Symbios 53c875 found.
> PCI-device: scsi@5, glm #3
> glm3 is /pci@1f,4000/scsi@5
> glm4: Rev. 4 Symbios 53c875 found.
> PCI-device: scsi@5,1, glm #4
> glm4 is /pci@1f,4000/scsi@5,1
> sd0 at glm0: target 0 lun 0
> sd0 is /pci@1f,4000/scsi@3/sd@0,0
> <SUN2.1G cyl 2733 alt 2 hd 19 sec 80>
> sd1 at glm0: target 1 lun 0
> sd1 is /pci@1f,4000/scsi@3/sd@1,0
> <SUN2.1G cyl 2733 alt 2 hd 19 sec 80>
> sd3 at glm0: target 3 lun 0
> sd3 is /pci@1f,4000/scsi@3/sd@3,0
> <Linux custom cyl 1007 alt 2 hd 67 sec 62>
> sd779 at glm4: target 0 lun 0
> sd779 is /pci@1f,4000/scsi@5,1/sd@0,0
> WARNING: /pci@1f,4000/scsi@5,1/sd@0,0 (sd779):
> corrupt label - wrong magic number
>
> Vendor 'SEAGATE', product 'ST19171W', 17689267 512 byte blocks
> sd780 at glm4: target 1 lun 0
> sd780 is /pci@1f,4000/scsi@5,1/sd@1,0
> WARNING: /pci@1f,4000/scsi@5,1/sd@1,0 (sd780):
> corrupt label - wrong magic number
>
> Vendor 'SEAGATE', product 'ST19171W', 17689267 512 byte blocks
> sd781 at glm4: target 2 lun 0
> sd781 is /pci@1f,4000/scsi@5,1/sd@2,0
> <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
> sd782 at glm4: target 3 lun 0
> sd782 is /pci@1f,4000/scsi@5,1/sd@3,0
> <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
>
>
>
>
>
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
