lkml.org 
[lkml]   [1999]   [Feb]   [23]   [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


On Mon, 22 Feb 1999, Bradley M. Kuhn wrote:

> [1.] One line summary of the problem:
>
> ncr53c8xx SCSI driver locks up computer after timeout message
>
> [2.] Full description of the problem/report:
>
> I have a TekRam DC390/UW2 80MB/Sec SCSI card which uses the ncr53c8xx driver
> and a Seagate ST39173LW drive.
>
> As the README for the ncr53c8xx suggests, I have configured the drive with:
> - only asynchronous data transfers
> - tagged commands disabled
> - disconnections not allowed

The README also suggests to first check that your SCSI bus is compliant to
specs. Let me assume you did it. :)

> Thus, I am not using any advanced features that might be buggy.

General remark:
---------------
IMO, mixing a JAZ device with a fine Fast-40 Hard disk on the same SCSI
BUS is kind of suicide, since the JAZ devices are known to be crappily
firmwared.

> Every once and a while, I get something like the following in my log files:

You got 2 SCSI interrupts in the same second (UDC+PAR) that seem to have
occurred for a single cause. This is not impossible if the device
disconnected the BUS and the chip was reading the SCSI BUS, or if the
disconnect had been too hard. Btw, we get such kinds of error conditions
with not correctly set SCSI BUS.

I suggest you the following:

1 - Make sure that your SCSI BUS is, at least theorically, correctly
configured (cables characteristics and quality, terminator positions,
etc...). If you aren't sure enough, send me (us) the description of
your SCSI BUS (cables length, position of each terminator and
devices).

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.

3 - Send me the messages printed by the driver at bootup using driver
verbose level 2. Boot command line : ncr53c8xx=verb:2

4 - Never use lspci command or cat /proc/pci/your_895_device under root
account with linux-2.1/2.2 since the reading of config space bytes 128
to 256 will just read the whole IO register space of the chip and
trigger bunches of side effects that have every chance to kill your
system.

Let me know.

Gérard.

> Feb 22 19:43:24 atheist kernel: ncr53c895-0:0: ERROR (0:4) (8-0-0) (f/9f) @(script 6c:1e000000).
> Feb 22 19:43:24 atheist kernel: ncr53c895-0: script cmd = 860b0000
> Feb 22 19:43:24 atheist kernel: ncr53c895-0: regdump: da 00 80 9f 47 0f 00 03 75 08 80 00 80 20 0e 0a.
> Feb 22 19:43:24 atheist kernel: ncr53c895-0: have to clear fifos.
> Feb 22 19:43:24 atheist kernel: ncr53c895-0: unexpected disconnect
> Feb 22 19:43:24 atheist kernel: ncr53c895-0-<0,0>: COMMAND FAILED (8a 8)@c0086020.
> Feb 22 19:43:24 atheist kernel: ncr53c895-0: SCSI parity error detected: SCR1=64 DBC=1e000000 SSTAT1=a
> Feb 22 19:43:24 atheist kernel: ncr53c895-0: restart (scsi reset).
> Feb 22 19:43:24 atheist kernel: ncr53c895-0: Downloading SCSI SCRIPTS.
> Feb 22 19:43:27 atheist kernel: ncr53c895-0-<0,*>: FAST-40 WIDE SCSI 80.0 MB/s (25 ns, offset 15)
>
>
> And, immediately folowing that, the machine locks up completely, and I need
> to reset it.
>
> I don't understand why it is receiving an unexpected disconnect. I have
> disconnections not allowed.
>
> [3.] Keywords (i.e., modules, networking, kernel):
>
> ncr53c8xx, SCSI, LVD, Ultra2, Tekram, Seagate
>
> [4.] Kernel version (from /proc/version):
> Linux version 2.2.1 (root@localhost.localdomain) (gcc version 2.7.2.3) #2
> Wed Feb 17 01:23:54 EST 1999
>
> [7.] Environment
>
> [7.1.] Software (add the output of the ver_linux script here)
>
> Linux atheist 2.2.1 #2 Wed Feb 17 01:23:54 EST 1999 i586 unknown
> Kernel modules 2.1.85
> Gnu C 2.7.2.3
> Binutils 2.9.1.0..4
> Linux C Library 2.0.7
> Dynamic linker ldd (GNU libc) 2.0.7
> Linux C++ Library 2.8.0
> Procps 1.2.7
> Mount 2.7l
> Net-tools 1.33
> Kbd 0.94
> Sh-utils 1.16
>
>
> [7.2.] Processor information (from /proc/cpuinfo):
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 5
> model : 8
> model name : AMD-K6(tm) 3D processor
> stepping : 12
> cpu MHz : 350.802387
> fdiv_bug : no
> hlt_bug : no
> sep_bug : no
> f00f_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu vme de pse tsc msr mce cx8 sep pge mmx 3dnow
> bogomips : 699.60
>
> [7.3.] Module information (from /proc/modules):
>
> (No modules)
>
> [7.4.] SCSI information (from /proc/scsi/scsi)
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: SEAGATE Model: ST39173LW Rev: 6246
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: MICROP Model: 3243-19 1128RV Rev: 28RV
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 04 Lun: 00
> Vendor: iomega Model: jaz 1GB Rev: H.72
> Type: Direct-Access ANSI SCSI revision: 02
>
> (The problem is with ID0. The other devices seem to function well, even
> under heavy load)
>
> [7.5.] Other information that might be relevant to the problem
> (please look in /proc and include all information that you
> think to be relevant):
>
> > cat /proc/scsi/ncr53c8xx/0
> General information:
> Chip NCR53C895, device id 0xc, revision id 0x1
> IO port address 0xec00, IRQ number 11
> Using memory mapped IO at virtual address 0xc8004000
> Synchronous period factor 10, max commands per lun 32
>
>
> --
> 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.059 / U:0.860 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site