[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

SCSI problems with Symbios Logic on a Sun Fire 280R



Hi all,

I've installed Debian Sarge on a Fire 280R and it seems to be working flawlessly except for a nasty problem with one of the SCSI controllers on it.

The machine has two SCSI controllers on it, as reported by lspci:

0000:00:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 37) 0000:00:06.1 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 37)
---
0000:02:04.0 SCSI storage controller: QLogic Corp. QLA2200 64-bit Fibre Channel Adapter (rev 05)


The qla2200 fb controller is working without any problems, as it's the one who has the hard disk drives attached to it:

SCSI subsystem driver Revision: 1.00
qlogicfc0 : Could not read from NVRAM
qlogicfc0 : Loop Reinitialized
qlogicfc0 : Link is Up
scsi0 : QLogic ISP2200 SCSI on PCI bus 02 device 20 irq 7263616 base 0x7ffed000300
qlogicfc0 : Port Database
wwn: 200000e08b000000  scsi_id: 0  loop_id: 2
wwn: 500000e0106617c1  scsi_id: 1  loop_id: 0
wwn: 500000e010662b71  scsi_id: 2  loop_id: 1
  Vendor: FUJITSU   Model: MAP3735F SUN72G   Rev: 1201
  Type:   Direct-Access                      ANSI SCSI revision: 04
  Vendor: FUJITSU   Model: MAP3735F SUN72G   Rev: 1201
  Type:   Direct-Access                      ANSI SCSI revision: 04
Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 2, lun 0
SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
Partition check:
 sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7
SCSI device sdb: 143374738 512-byte hdwr sectors (73408 MB)
 sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7
---

The problems however comes whenever I try to use any of the devices attached to the sym53c875 controller. I've tried with three different driver modules: ncr53c8xx, sym53c8xx and sym53c8xx_2. sym53c8xx by itself won't even load. With both ncr53c8xx and sym53c8xx_2 the devices attached to this controller (an internal DVD-ROM drive which comes with the machine and an external StorEdge DDS-4 tape drive, which is now offline) gets correctly identified. With both the ncr53c8xx and sym53c8xx_2 drivers it starts writing abort and bus reset SCSI messages as soon as I try to access any of the devices on the controller (ie. mount the DVD drive or try to read the status of the tape):

chronos:~# modprobe sym53c8xx
sym53c8xx: at PCI bus 0, device 6, function 0
sym53c8xx: 53c875 detected
sym53c8xx: at PCI bus 0, device 6, function 1
sym53c8xx: 53c875 detected
sym53c875-0: rev 0x37 on pci bus 0 device 6 function 0 irq 4,218
sym53c875-0: ID 7, Fast-20, Parity Checking
sym53c875-0: PCI clock (66829 KHz) is out of range [22688 KHz - 45375 KHz].
sym53c875-0: giving up ...
sym53c875-0: rev 0x37 on pci bus 0 device 6 function 1 irq 4,219
sym53c875-0: ID 7, Fast-20, Parity Checking
sym53c875-0: PCI clock (66829 KHz) is out of range [22688 KHz - 45375 KHz].
sym53c875-0: giving up ...
/lib/modules/2.4.26/kernel/drivers/scsi/sym53c8xx.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.26/kernel/drivers/scsi/sym53c8xx.o: insmod /lib/modules/2.4.26/kernel/drivers/scsi/sym53c8xx.o failed /lib/modules/2.4.26/kernel/drivers/scsi/sym53c8xx.o: insmod sym53c8xx failed

------
chronos:~# modprobe ncr53c8xx
ncr53c8xx: at PCI bus 0, device 6, function 0
ncr53c8xx: 53c875 detected
ncr53c8xx: at PCI bus 0, device 6, function 1
ncr53c8xx: 53c875 detected
ncr53c875-0: rev 0x37 on pci bus 0 device 6 function 0 irq 4,218
ncr53c875-0: ID 7, Fast-20, Parity Checking
ncr53c875-1: rev 0x37 on pci bus 0 device 6 function 1 irq 4,219
ncr53c875-1: ID 7, Fast-20, Parity Checking
scsi2 : ncr53c8xx-3.4.3b-20010512
scsi3 : ncr53c8xx-3.4.3b-20010512
  Vendor: TOSHIBA   Model: DVD-ROM SD-M1711  Rev: 1005
  Type:   CD-ROM                             ANSI SCSI revision: 02

chronos:~# mount /dev/scd0 /cdrom -t iso9660
Attached scsi CD-ROM sr0 at scsi2, channel 0, id 6, lun 0
ncr53c875-0-<6,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 16)
scsi : aborting command due to timeout : pid 5731, scsi2, channel 0, id 6, lun 0 Mode Sense 00 2a 00 80 00 ncr53c8xx_abort: pid=5731 serial_number=5732 serial_number_at_timeout=5732
ncr53c875-0: abort ccb=fffff800772a6000 (cancel)
SCSI host 2 abort (pid 5731) timed out - resetting
SCSI bus is being reset for host 2 channel 0.
ncr53c8xx_reset: pid=5731 reset_flags=2 serial_number=5732 serial_number_at_timeout=5732
ncr53c875-0-<6,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 16)

(... and so it starts all over again, in this case it won't give control back to the console so I have to reboot)


------
chronos:~# modprobe sym53c8xx_2
sym.0.6.0: setting PCI_COMMAND_INVALIDATE.
sym.0.6.1: setting PCI_COMMAND_INVALIDATE.
sym0: <875> rev 0x37 on pci bus 0 device 6 function 0 irq 4,218
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym0: SCSI BUS has been reset.
sym1: <875> rev 0x37 on pci bus 0 device 6 function 1 irq 4,219
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.1.17a
scsi2 : sym-2.1.17a
  Vendor: TOSHIBA   Model: DVD-ROM SD-M1711  Rev: 1005
  Type:   CD-ROM                             ANSI SCSI revision: 02

chronos:~# mount /dev/scd0 /cdrom -t iso9660
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 6, lun 0
sym0:6: FAST-20 SCSI 20.0 MB/s ST (50.0 ns, offset 16)
sym0:6:0: ABORT operation started.
sym0:6:0: ABORT operation timed-out.
sym0:6:0: DEVICE RESET operation started.
sym0:6:0: DEVICE RESET operation timed-out.
sym0:6:0: BUS RESET operation started.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
sym0:6:0: BUS RESET operation complete.
sym0:6:0: ABORT operation started.
sym0:6:0: ABORT operation timed-out.
scsi: device set offline - not ready or command retry failed after bus reset: host 1 channel 0 id 6 lun 0
sr0: scsi3-mmc drive: 23x/2x xa/form2 cdda
Uniform CD-ROM driver Revision: 3.12
cdrom: open failed.
mount: block device /dev/scd0 is write-protected, mounting read-only
mount: No medium found


This time I get similar messages but at least I get back to the console again, and the mount operation fails down with a 'no medium found' error. A obvious as it may seem, the DVD drive does indeed has a disc inside of it. The same thing happens when I try to access the tape drive (when connected), using either stinit or mt-st status.


I ran 'probe-scsi-all' from the OpenBoot prompt and got no problems at all. It might not be all that relevant but perhaps it's worth noting that I have access to this machine only via serial console, no video card, monitor and keyboard are attached to it. Also I installed this machine via network boot, so I have not used the DVD drive before.

Sorry for the lenghty message but I wanted to give as much detail as possible.

Regards and thanks for your help.

--
Carlos Oliva G.
Igloo Sistemas Ltda.
carlos.oliva@igloo.cl - http://www.igloo.cl
Tel/Fax: +56 32 684798



Reply to: