Actually I tried all the drivers for the ASUS SC200, a 53c810 based
card that used to work well. I have only a DDS-1 tape connected to
it but the drivers just do not cut it. Some refuse to load and others
get kernel panics. This gets even stranger. I proceeded to connect
the unit to a Compaq Proliant 6000 (four PIII Xeons). It has a 53c875
controller (three channels) and the sym53c8xx is crashing the system
if I try to access the tape (it does recognise it just fine when
loaded).
The newer driver (in sym53c8xx_2) does not get that far, the driver
locks up when I modprobe this driver.
Here are the boot messages, where the driver seems to OK (this is
the original sym53c8xx driver):
[BTW, why the final "scsi : 0 hosts left" message?]
[I will test again tomorrow, it is a new moon then...]
Oct 4 12:56:16 ssa28 kernel: SCSI subsystem driver Revision: 1.00
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 0, device 13,
function 0
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 4, device 9,
function 0
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 4, device 9,
function 1
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
Oct 4 12:56:16 ssa28 kernel: sym53c875-0: rev 0x4 on pci bus 0 device
13 function 0 irq 5
Oct 4 12:56:16 ssa28 kernel: sym53c875-0: ID 7, Fast-20, Parity
Checking
Oct 4 12:56:16 ssa28 kernel: sym53c875-1: rev 0x14 on pci bus 4 device
9 function 0 irq 5
Oct 4 12:56:16 ssa28 kernel: sym53c875-1: ID 7, Fast-20, Parity
Checking
Oct 4 12:56:16 ssa28 kernel: sym53c875-2: rev 0x14 on pci bus 4 device
9 function 1 irq 5
Oct 4 12:56:16 ssa28 kernel: sym53c875-2: ID 7, Fast-20, Parity
Checking
Oct 4 12:56:16 ssa28 kernel: scsi0 : sym53c8xx-1.7.3c-20010512
Oct 4 12:56:16 ssa28 kernel: scsi1 : sym53c8xx-1.7.3c-20010512
Oct 4 12:56:16 ssa28 kernel: scsi2 : sym53c8xx-1.7.3c-20010512
Oct 4 12:56:16 ssa28 kernel: Vendor: ARCHIVE Model: Python
28388-XXX Rev: 4.28
Oct 4 12:56:16 ssa28 kernel: Type:
Sequential-Access ANSI SCSI revision: 02
Oct 4 12:56:16 ssa28 kernel: sym53c875-0: detaching ...
Oct 4 12:56:16 ssa28 kernel: sym53c875-0: resetting chip
Oct 4 12:56:16 ssa28 kernel: sym53c875-1: detaching ...
Oct 4 12:56:16 ssa28 kernel: sym53c875-1: resetting chip
Oct 4 12:56:16 ssa28 kernel: sym53c875-2: detaching ...
Oct 4 12:56:16 ssa28 kernel: sym53c875-2: resetting chip
Oct 4 12:56:16 ssa28 kernel:
Oct 4 12:56:16 ssa28 kernel: inserting floppy driver for 2.4.18-ac3ser
Oct 4 12:56:16 ssa28 kernel: Floppy drive(s): fd0 is 1.44M
Oct 4 12:56:16 ssa28 kernel: FDC 0 is a National Semiconductor PC87306
Oct 4 12:56:16 ssa28 kernel: parport0: PC-style at 0x3bc [PCSPP]
Oct 4 12:56:16 ssa28 kernel: SCSI subsystem driver Revision: 1.00
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 0, device 13,
function 0
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 4, device 9,
function 0
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 4, device 9,
function 1
Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
Oct 4 12:56:16 ssa28 kernel: sym53c875-0: rev 0x4 on pci bus 0 device
13 function 0 irq 5
Oct 4 12:56:16 ssa28 kernel: sym53c875-0: ID 7, Fast-20, Parity
Checking
Oct 4 12:56:16 ssa28 kernel: sym53c875-1: rev 0x14 on pci bus 4 device
9 function 0 irq 5
Oct 4 12:56:16 ssa28 kernel: sym53c875-1: ID 7, Fast-20, Parity
Checking
Oct 4 12:56:16 ssa28 kernel: sym53c875-2: rev 0x14 on pci bus 4 device
9 function 1 irq 5
Oct 4 12:56:16 ssa28 kernel: sym53c875-2: ID 7, Fast-20, Parity
Checking
Oct 4 12:56:16 ssa28 kernel: scsi0 : sym53c8xx-1.7.3c-20010512
Oct 4 12:56:16 ssa28 kernel: scsi1 : sym53c8xx-1.7.3c-20010512
Oct 4 12:56:16 ssa28 kernel: scsi2 : sym53c8xx-1.7.3c-20010512
Oct 4 12:56:16 ssa28 kernel: Vendor: ARCHIVE Model: Python
28388-XXX Rev: 4.28
Oct 4 12:56:16 ssa28 kernel: Type:
Sequential-Access ANSI SCSI revision: 02
Oct 4 12:56:16 ssa28 kernel: sym53c875-0: detaching ...
Oct 4 12:56:16 ssa28 kernel: sym53c875-0: resetting chip
Oct 4 12:56:16 ssa28 kernel: sym53c875-1: detaching ...
Oct 4 12:56:16 ssa28 kernel: sym53c875-1: resetting chip
Oct 4 12:56:16 ssa28 kernel: sym53c875-2: detaching ...
Oct 4 12:56:16 ssa28 kernel: sym53c875-2: resetting chip
Oct 4 12:56:16 ssa28 kernel: scsi : 0 hosts left.
--
Eyal Lebedinsky ([email protected]) <http://samba.org/eyal/>
Hello Eyal , I have a CP6000 unit (PPRO's tho) & am having no
such difficulties . Now that said I rebuilt the WHOLE scsi
layout in the system in order to get rid of those older hotswap
cages (imo, they stink electrically) . Btw , Stable as heck .
Wheres that forest I need to knock on ;-)
Is your scsi setup easy enough to make an ascii art description
of ? If so would you post it please ? From the messages below
it appears (to me) that their is some difficulty in the chain that
attaches to the python . I have never seen those messages when I
have attached (albeit differant) tape drives , ie: DLT,dat2,dat3 .
Twys , JimL
On Sat, 5 Oct 2002, Eyal Lebedinsky wrote:
> Actually I tried all the drivers for the ASUS SC200, a 53c810 based
> card that used to work well. I have only a DDS-1 tape connected to
> it but the drivers just do not cut it. Some refuse to load and others
> get kernel panics. This gets even stranger. I proceeded to connect
> the unit to a Compaq Proliant 6000 (four PIII Xeons). It has a 53c875
> controller (three channels) and the sym53c8xx is crashing the system
> if I try to access the tape (it does recognise it just fine when
> loaded).
>
> The newer driver (in sym53c8xx_2) does not get that far, the driver
> locks up when I modprobe this driver.
>
> Here are the boot messages, where the driver seems to OK (this is
> the original sym53c8xx driver):
> [BTW, why the final "scsi : 0 hosts left" message?]
> [I will test again tomorrow, it is a new moon then...]
>
> Oct 4 12:56:16 ssa28 kernel: SCSI subsystem driver Revision: 1.00
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 0, device 13,
> function 0
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 4, device 9,
> function 0
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 4, device 9,
> function 1
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
> Oct 4 12:56:16 ssa28 kernel: sym53c875-0: rev 0x4 on pci bus 0 device
> 13 function 0 irq 5
> Oct 4 12:56:16 ssa28 kernel: sym53c875-0: ID 7, Fast-20, Parity
> Checking
> Oct 4 12:56:16 ssa28 kernel: sym53c875-1: rev 0x14 on pci bus 4 device
> 9 function 0 irq 5
> Oct 4 12:56:16 ssa28 kernel: sym53c875-1: ID 7, Fast-20, Parity
> Checking
> Oct 4 12:56:16 ssa28 kernel: sym53c875-2: rev 0x14 on pci bus 4 device
> 9 function 1 irq 5
> Oct 4 12:56:16 ssa28 kernel: sym53c875-2: ID 7, Fast-20, Parity
> Checking
> Oct 4 12:56:16 ssa28 kernel: scsi0 : sym53c8xx-1.7.3c-20010512
> Oct 4 12:56:16 ssa28 kernel: scsi1 : sym53c8xx-1.7.3c-20010512
> Oct 4 12:56:16 ssa28 kernel: scsi2 : sym53c8xx-1.7.3c-20010512
> Oct 4 12:56:16 ssa28 kernel: Vendor: ARCHIVE Model: Python
> 28388-XXX Rev: 4.28
> Oct 4 12:56:16 ssa28 kernel: Type:
> Sequential-Access ANSI SCSI revision: 02
> Oct 4 12:56:16 ssa28 kernel: sym53c875-0: detaching ...
> Oct 4 12:56:16 ssa28 kernel: sym53c875-0: resetting chip
> Oct 4 12:56:16 ssa28 kernel: sym53c875-1: detaching ...
> Oct 4 12:56:16 ssa28 kernel: sym53c875-1: resetting chip
> Oct 4 12:56:16 ssa28 kernel: sym53c875-2: detaching ...
> Oct 4 12:56:16 ssa28 kernel: sym53c875-2: resetting chip
> Oct 4 12:56:16 ssa28 kernel:
> Oct 4 12:56:16 ssa28 kernel: inserting floppy driver for 2.4.18-ac3ser
> Oct 4 12:56:16 ssa28 kernel: Floppy drive(s): fd0 is 1.44M
> Oct 4 12:56:16 ssa28 kernel: FDC 0 is a National Semiconductor PC87306
> Oct 4 12:56:16 ssa28 kernel: parport0: PC-style at 0x3bc [PCSPP]
> Oct 4 12:56:16 ssa28 kernel: SCSI subsystem driver Revision: 1.00
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 0, device 13,
> function 0
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 4, device 9,
> function 0
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: at PCI bus 4, device 9,
> function 1
> Oct 4 12:56:16 ssa28 kernel: sym53c8xx: 53c875 detected
> Oct 4 12:56:16 ssa28 kernel: sym53c875-0: rev 0x4 on pci bus 0 device
> 13 function 0 irq 5
> Oct 4 12:56:16 ssa28 kernel: sym53c875-0: ID 7, Fast-20, Parity
> Checking
> Oct 4 12:56:16 ssa28 kernel: sym53c875-1: rev 0x14 on pci bus 4 device
> 9 function 0 irq 5
> Oct 4 12:56:16 ssa28 kernel: sym53c875-1: ID 7, Fast-20, Parity
> Checking
> Oct 4 12:56:16 ssa28 kernel: sym53c875-2: rev 0x14 on pci bus 4 device
> 9 function 1 irq 5
> Oct 4 12:56:16 ssa28 kernel: sym53c875-2: ID 7, Fast-20, Parity
> Checking
> Oct 4 12:56:16 ssa28 kernel: scsi0 : sym53c8xx-1.7.3c-20010512
> Oct 4 12:56:16 ssa28 kernel: scsi1 : sym53c8xx-1.7.3c-20010512
> Oct 4 12:56:16 ssa28 kernel: scsi2 : sym53c8xx-1.7.3c-20010512
> Oct 4 12:56:16 ssa28 kernel: Vendor: ARCHIVE Model: Python
> 28388-XXX Rev: 4.28
> Oct 4 12:56:16 ssa28 kernel: Type:
> Sequential-Access ANSI SCSI revision: 02
> Oct 4 12:56:16 ssa28 kernel: sym53c875-0: detaching ...
> Oct 4 12:56:16 ssa28 kernel: sym53c875-0: resetting chip
> Oct 4 12:56:16 ssa28 kernel: sym53c875-1: detaching ...
> Oct 4 12:56:16 ssa28 kernel: sym53c875-1: resetting chip
> Oct 4 12:56:16 ssa28 kernel: sym53c875-2: detaching ...
> Oct 4 12:56:16 ssa28 kernel: sym53c875-2: resetting chip
> Oct 4 12:56:16 ssa28 kernel: scsi : 0 hosts left.
>
> --
> Eyal Lebedinsky ([email protected]) <http://samba.org/eyal/>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| [email protected] | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+
"Mr. James W. Laferriere" wrote:
>
> Hello Eyal , I have a CP6000 unit (PPRO's tho) & am having no
> such difficulties . Now that said I rebuilt the WHOLE scsi
> layout in the system in order to get rid of those older hotswap
> cages (imo, they stink electrically) . Btw , Stable as heck .
> Wheres that forest I need to knock on ;-)
Sounds good
> Is your scsi setup easy enough to make an ascii art description
> of ? If so would you post it please ? From the messages below
> it appears (to me) that their is some difficulty in the chain that
> attaches to the python . I have never seen those messages when I
> have attached (albeit differant) tape drives , ie: DLT,dat2,dat3 .
As I mentioned the ONLY scsi device is the externally connected DDS-1
tape drive. It is a SCSI-2 narrow (50-pin) device. It uses a
HD-centronics->50pin-centronics cable.
I believe the BIOS on this machine really does not like and IDE disks
connected. It does have an IDE controller but will only allow the CD
drive on it, so we have a PCI/IDE controller installed to handle the
single IDE disk. The machine refuses to boot off the IDE but LILO is
happy to do so off a floppy.
BTW, I only have this machine in order to test out software on a 4-way
SMP machine, which is why we passed on installing more expensive scsi
disks.
Now, when I connect the cable to my tape, lilo fails to boot off the
floppy. It seems that the first BIOS disk (80h) which is detected
properly by the IDE controller is trashed by the scsi controller
(which initialises later than the IDE). So we now boot off the floppy
directly (i.e. the kernel boots off the floppy, not just lilo).
Finally, now that we are booting just fine, and the scsi tape drive
is clearly detected at bootup by the kernel, I see that the scsi
driver does not stay loaded (maybe the boot process loads it, and
if there are no disks it unloads it?). So I try to load it myself
modprobe sym53c8xx
and this kills the machine.
By "kills" I mean the machine stutters for a few seconds, and then
locks up, not even vt switching. No message is ever displayed.
--
Eyal Lebedinsky ([email protected]) <http://samba.org/eyal/>
Hello Eyal ,
On Sun, 6 Oct 2002, Eyal Lebedinsky wrote:
> "Mr. James W. Laferriere" wrote:
> > Is your scsi setup easy enough to make an ascii art description
> > of ? If so would you post it please ? From the messages below
> > it appears (to me) that their is some difficulty in the chain that
> > attaches to the python . I have never seen those messages when I
> > have attached (albeit differant) tape drives , ie: DLT,dat2,dat3 .
> As I mentioned the ONLY scsi device is the externally connected DDS-1
> tape drive. It is a SCSI-2 narrow (50-pin) device. It uses a
> HD-centronics->50pin-centronics cable.
I have been reviewing your previous message to the list . In it
you mentioned putting a Asus sc200(53c810) card into this system .
Was that card in the system when the dmesg output was taken ?
IF it was then that dmesg output shows a bug in the controller
card recognition routines . A 53c810 isn't a 53c875 .
Also iirc the 6000 has either a 53c876 or two 53c875's on board
not three . At least mine only reports 2 53c875's .
Another source of information for the sym driver is
/usr/src/linux/drivers/scsi/sym53c8xx_2/Documentation.txt
> I believe the BIOS on this machine really does not like and IDE disks
> connected. It does have an IDE controller but will only allow the CD
> drive on it, so we have a PCI/IDE controller installed to handle the
> single IDE disk. The machine refuses to boot off the IDE but LILO is
> happy to do so off a floppy.
Iirc the bios is stunted to only allow boot to cdrom on the ide
port . So the limitation probably continues onto other ide
controllers as well .
> BTW, I only have this machine in order to test out software on a 4-way
> SMP machine, which is why we passed on installing more expensive scsi
> disks.
>
> Now, when I connect the cable to my tape, lilo fails to boot off the
> floppy. It seems that the first BIOS disk (80h) which is detected
> properly by the IDE controller is trashed by the scsi controller
> (which initialises later than the IDE). So we now boot off the floppy
> directly (i.e. the kernel boots off the floppy, not just lilo).
>
> Finally, now that we are booting just fine, and the scsi tape drive
> is clearly detected at bootup by the kernel, I see that the scsi
> driver does not stay loaded (maybe the boot process loads it, and
> if there are no disks it unloads it?). So I try to load it myself
> modprobe sym53c8xx
> and this kills the machine.
>
> By "kills" I mean the machine stutters for a few seconds, and then
> locks up, not even vt switching. No message is ever displayed.
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| [email protected] | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+