lkml.org 
[lkml]   [1999]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ncr53c8xx SCSI driver locks up computer after timeout message
Thus spoke Gerard Roudier:

> IIRC, the board uses a LVD to SE converter that allows to use SE device
> and LVD device driven by a single SCSI initiator.

> I never tried such a controller, but on controller that does not use LVD
> to SE converter you must use *at most* 2 cables and terminate the BUS at
> each end and only at each end. "End" mean the *extreme* end of the cable.

I am doing that. However, I am currently relying on the external JAZ
drive's terminator for one end of the chain...

Based on your experience, do you think this terminator is not reliable?

> If you dismount the Jaz and the Jaz was not at one end of the BUS, you
> have been fine, otherwise you just broke your BUS compliance.

So you are saying that the external JAZ drive's own terminator switch is
faulty?

I am going to buy an actual terminator tommorrow, and turn the Jaz drive's
own terminator off. Do you really think this is my problem, though?

> > > 2 - If you donnot have either old 810 rev. < 16 or 815 or 825 rev < 16 on
> > > your system, give a try with the latest sym53c8xx-1.2a driver that has
> > > been recently enhanced for SCSI error recovery. Changes haven't yet been
> > > backported to stock ncr53c8xx driver.

I have a newer 895. I will try your new driver tommorrow evening.

> > > 3 - Send me the messages printed by the driver at bootup using driver
> > > verbose level 2. Boot command line : ncr53c8xx=verb:2
> >
> > I will do this the next time I reboot the machine.

Here is the data:

Feb 24 05:30:45 kernel: ncr53c8xx: setup=disc:n,specf:0,ultra:0,tags:0,sync:255,burst:255,wide:n,diff:1,revprob:n,buschk:0x1
Feb 24 05:30:45 kernel: ncr53c8xx: setup=mpar:n,spar:y,fsn=n,verb:2,debug:0x0,led:n,settle:10,irqm:1,nvram:0x1,pcifix:0x0
Feb 24 05:30:45 kernel: ncr53c8xx: at PCI bus 0, device 10, function 0
Feb 24 05:30:45 kernel: ncr53c8xx: 53c895 detected
Feb 24 05:30:45 kernel: ncr53c895-0: rev=0x01, base=0xeb000000, io_port=0xec00, irq=11
Feb 24 05:30:45 kernel: ncr53c895-0: using memory mapped IO at virtual address 0xc8004000
Feb 24 05:30:45 kernel: ncr53c895-0: clock multiplier found
Feb 24 05:30:45 kernel: ncr53c895-0: ID 7, Fast-10, Parity Checking
Feb 24 05:30:45 kernel: ncr53c895-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/8e/a0/01/00/24
Feb 24 05:30:45 kernel: ncr53c895-0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/80/00/00/00/00
Feb 24 05:30:45 kernel: ncr53c895-0: requesting shared irq 11 (dev_id=0xc0008080)
Feb 24 05:30:45 kernel: ncr53c895-0: resetting, command processing suspended for 10 seconds
Feb 24 05:30:45 kernel: ncr53c895-0: restart (scsi reset).
Feb 24 05:30:45 kernel: ncr53c895-0: enabling clock multiplier
Feb 24 05:30:45 kernel: ncr53c895-0: waiting 10 seconds for scsi devices to settle...
Feb 24 05:30:45 kernel: scsi0 : ncr53c8xx - revision 3.1f
Feb 24 05:30:45 kernel: scsi : 1 host.
Feb 24 05:30:45 kernel: ncr53c895-0: command processing resumed
Feb 24 05:30:45 kernel: Vendor: SEAGATE Model: ST39173LW Rev: 6246
Feb 24 05:30:45 kernel: Type: Direct-Access ANSI SCSI revision: 02
Feb 24 05:30:45 kernel: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Feb 24 05:30:45 kernel: Vendor: MICROP Model: 3243-19 1128RV Rev: 28RV
Feb 24 05:30:45 kernel: Type: Direct-Access ANSI SCSI revision: 02
Feb 24 05:30:45 kernel: Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0
Feb 24 05:30:45 kernel: Vendor: iomega Model: jaz 1GB Rev: H.72
Feb 24 05:30:45 kernel: Type: Direct-Access ANSI SCSI revision: 02
Feb 24 05:30:45 kernel: Detected scsi removable disk sdc at scsi0, channel 0, id 4, lun 0
Feb 24 05:30:45 kernel: scsi : detected 3 SCSI disks total.
Feb 24 05:30:45 kernel: ncr53c895-0-<0,*>: asynchronous.
Feb 24 05:30:45 kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
Feb 24 05:30:45 kernel: ncr53c895-0-<2,*>: asynchronous.
Feb 24 05:30:45 kernel: SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8388315 [4095 MB] [4.1 GB]
Feb 24 05:30:45 kernel: ncr53c895-0-<4,*>: asynchronous.
Feb 24 05:30:45 kernel: SCSI device sdc: hdwr sector= 512 bytes. Sectors= 2091050 [1021 MB] [1.0 GB]



Then a failure follows:

Feb 24 05:40:15 kernel: ncr53c8xx_abort: pid=29172 serial_number=29181 serial_number_at_timeout=29181
Feb 24 05:40:15 kernel: ncr53c895-0: abort ccb=c009a820 (cancel)
Feb 24 05:40:17 kernel: SCSI host 0 abort (pid 29172) timed out - resetting
Feb 24 05:40:17 kernel: SCSI bus is being reset for host 0 channel 0.
Feb 24 05:40:17 kernel: ncr53c8xx_reset: pid=29172 reset_flags=2 serial_number=29181 serial_number_at_timeout=29181
Feb 24 05:40:17 kernel: ncr53c895-0: resetting, command processing suspended for 10 seconds
Feb 24 05:40:17 kernel: ncr53c895-0: restart (scsi reset).
Feb 24 05:40:17 kernel: ncr53c895-0: enabling clock multiplier
Feb 24 05:40:26 kernel: ncr53c895-0: command processing resumed
Feb 24 05:40:26 kernel: ncr53c895-0-<0,*>: asynchronous.
Feb 24 05:40:26 kernel: ncr53c895-0-<4,*>: asynchronous.


After this, I got a kernel panic. I am running 2.2.2 now, BTW.


Thanks again for your help, Gérard. I will download the new driver from
tux.org tommorrow and see if changes anything, and I will put a new
terminator on the end of with the JAZ drive.

If you have any information that may be of help in the meantime, I would
appreciate it if you would pass it along.

Thanks.
--
Bradley M. Kuhn | bkuhn@ebb.org | http://www.ebb.org/bkuhn

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.109 / U:0.120 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site