Date: Wed, 04 Feb 1998 07:56:32 +0100 From: Lars Koeller <Lars.Koeller@post.uni-bielefeld.de> To: Doug White <dwhite@resnet.uoregon.edu> Cc: scsi@FreeBSD.ORG Subject: Re: SCB and 2940 Problems! Message-ID: <199802040656.AA187635393@pollux.hrz.uni-bielefeld.de> In-Reply-To: dwhite's message of Tue, 03 Feb 1998 12:06:14 -0800. <Pine.BSF.3.96.980203120312.13454A-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multipart MIME message.
--==_Exmh_5296095340
Content-Type: text/plain; charset=us-ascii
----------
Hello Doug, SCSI gurus!
In reply to Doug White who wrote:
> On Mon, 2 Feb 1998, Lars Koeller wrote:
>
> > Before I make an PR, I want to query you as an SCSI expert!
>
> I'm not much of a SCSI wizzard, I only know some patterns.
>
> > adapters. The solution named are ofter termination check/problems.
> > After changing from NCR815 cotroller to 2940U, I run into such
> > trouble, too.
>
> Perhaps your DAT isn't happy with the organization of the bus, or one of
> your devces is unhappy. After **double**checking the termination (should
> be on on only the END devices -- use bus power if available) try
> rearranging the order of devices, or take devices off and try to isolate
> the troublesome device.
I do all this, before I'm going to contact you! I use the Seagate DAT at
both busses (see appended E-Mail below a AH2940 and a AH2940UW). The last
test was the ST15150N disk and the Seagate DAT at the 2940 with a very short
internal 50 pol ribbon cable. The disk terminates the bus as usual,
termpower from bus is o.k. No external devices.
No of the disks or the HP DAT at the same bus direct before the
Seagate DAT ever have such a problem, even under heavy load.
The SCB timeout only occures when disk and DAT are under 'heavy'
load, i.e. backup onto the DAT with dump or some other backup
software. Using the same configuration and the HP DAT as the
destination runs without any problems!!!
Again. I've checked all terminators, etc. several times, it's all o.k!
Here are the configurations I've tested:
ADIC : ADIC 1200 autochanger with build in HP 1533A DDS2 DAT
StDAT : Seagate DDS2 DAT, Phyton 28388 (8000 Series)
WangQIC: Wangtec ES5525 525MB QIC Tape drive
The total cable lengthe never exceeds 2.5 meters!
External cable is a hight quality 50 pol high desity Sub-D
to 50 pol centronics cable!
Intern drives | Extern drives
------------------------------------------------------------------
|
1) ST15150N--------AH2940-------ADIC----WangQIC----StDAT--(aktive Term)
(Term on)
(Term Power from Bus)
2) ST15150N--------AH2940-------WangQIC----StDAT--(aktive Term)
(Term on)
(Term Power from Bus)
3) ST15150N----StDAT----AH2940
(Term on)
(Term Power from Bus)
4) ST32171UW----ST32171UW----AH2940UW
(Term) |
|
Pioneer CDROM----StDAT-------+ (50 pol internal connetor)
DRU-466
(Term)
There are always both (AH2940 and 2940UW) adapters installed!
In all cases, only the StDAT have hanging SCB's!
Any ideas???
Thanks a lot
Lars
--
E-Mail: | Lars Koeller
Lars.Koeller@Uni-Bielefeld.DE | UNIX Sysadmin
lkoeller@cc.FH-Lippe.DE | Computing Center
PGP-key: | University of Bielefeld
http://www.nic.surfnet.nl/pgp/pks-toplev.html | Germany
----------- FreeBSD, what else? ---- http://www.freebsd.org -------------
--------------------- 1st Mail ------------------------------------------
Hello Doug!
Before I make an PR, I want to query you as an SCSI expert! I read
some mails in the list, concerning SCB problems on Adaptec host
adapters. The solution named are ofter termination check/problems.
After changing from NCR815 cotroller to 2940U, I run into such
trouble, too.
I do some debuging and testing on my SCSI buses (2940UW with 2
ST32171UW+Pioneer DR466 CDROM and 2940U ST15150N+Seagate Python 28388
DAT+Wangtec ES5525+Adic Changer with HP1533). It's definitely NOT a termination
problem, and only the Seagate DAT has these problems on both busses!
If I use dump or some other tool with constant high data flow, I get
the messages like this (both are from the Seagate DAT, st0 on the
2940U, st3 same on 2940UW):
Jan 31 18:29:03 odie /kernel: st3(ahc1:4:0): SCB 0x7 - timed out in command phase, SCSISIGI == 0x84
Jan 31 18:29:06 odie /kernel: SEQADDR = 0x41 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2
Jan 31 18:29:06 odie /kernel: st3(ahc1:4:0): abort message in message buffer
Jan 31 18:29:06 odie /kernel: st3(ahc1:4:0): SCB 0x7 - timed out in command phase, SCSISIGI == 0x94
Jan 31 18:29:06 odie /kernel: SEQADDR = 0x41 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2
Jan 31 18:29:06 odie /kernel: st3(ahc1:4:0): no longer in timeout
And sometimes
Jan 25 15:26:36 odie /kernel: SEQADDR = 0x41 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2
Jan 25 15:26:36 odie /kernel: st0(ahc0:1:0): abort message in message buffer
Jan 25 15:26:36 odie /kernel: st0(ahc0:1:0): SCB 0x1 - timed out in command phase, SCSISIGI == 0x94
Jan 25 15:26:36 odie /kernel: SEQADDR = 0x41 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2
Jan 25 15:26:36 odie /kernel: st0(ahc0:1:0): no longer in timeout
Jan 25 15:26:36 odie /kernel: ahc0: Issued Channel A Bus Reset. 4 SCBs aborted
Jan 25 15:26:36 odie /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0
Jan 25 15:26:36 odie /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 1
Jan 25 15:26:36 odie /kernel: , retries:3
Jan 25 15:26:36 odie /kernel: st0(ahc0:1:0): Target Busy
I append my kernel config file.
--==_Exmh_5296095340
Content-Type: text/plain ; name="ODIE"; charset=us-ascii
Content-Description: ODIE
Content-Disposition: attachment; filename="ODIE"
#
# ODIE kernel config file
#
machine "i386"
cpu "I686_CPU" # aka Pentium Pro(tm)
ident ODIE
maxusers 16
config kernel root on sd1
# This allows you to actually store this configuration file into
# the kernel binary itself, where it may be later read by saying:
# strings /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL
#
options INCLUDE_CONFIG_FILE # Include this file in kernel
#
# Under some circumstances it is convenient to increase the defaults
# for the maximum number of processes per user and the maximum number
# of open files files per user. E.g., (1) in a large news server, user
# `news' may need more than 100 concurrent processes. (2) a user may
# need lots of windows under X. In both cases, it may be inconvenient
# to start all the processes from a parent whose soft rlimit on the
# number of processes is large enough. The following options work by
# changing the soft rlimits for init.
#
options CHILD_MAX=128
options OPEN_MAX=128
#
# Certain applications can grow to be larger than the 128M limit
# that FreeBSD initially imposes. Below are some options to
# allow that limit to grow to 256MB, and can be increased further
# with changing the parameters. MAXDSIZ is the maximum that the
# limit can be set to, and the DFLDSIZ is the default value for
# the limit. You might want to set the default lower than the
# max, and explicitly set the maximum with a shell command for processes
# that regularly exceed the limit like INND.
#
options "MAXDSIZ=(256*1024*1024)"
options "DFLDSIZ=(256*1024*1024)"
options INET #InterNETworking
options HDLC #X.25 link layer for serial lines
options FFS #Berkeley Fast Filesystem
options NFS #Network Filesystem
#options MFS #Memory Filesystem
#options MSDOSFS #MSDOS Filesystem
#options "CD9660" #ISO 9660 Filesystem
options PROCFS #Process filesystem
options "COMPAT_43" #Compatible with BSD 4.3
options "SCSI_DELAY=4" #Be pessimistic about Joe SCSI device
options MROUTING #Multicast routing
options "MAXCONS=8" #Number of max. allowed virt. consoles
options QUOTA #enable disk quotas
#options COMPAT_LINUX #Linux Emulator
#options "COMPAT_IBCS2" #SCO & SYSV Emulator
options PERFMON #Pentium (Pro) performance counters
options SYSVSHM #System V shared memory support
options SYSVSEM #System V Semophore support
options SYSVMSG #System V Message support
options UCONSOLE #Allow ordinary users to take the
#console - this is useful for X.
options XSERVER #include code for XFree86
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
#
# KTRACE enables the system-call tracing facility ktrace(2).
#
options KTRACE #kernel tracing
#
# Enable the kernel debugger.
#
options DDB
#
# ISA devices
#
controller isa0
options "AUTO_EOI_1"
controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fdc0 drive 0
disk fd1 at fdc0 drive 1
device apm0 at isa?
#
# PCI devices
#
controller pci0
options SCSI_REPORT_GEOMETRY
# AHC Adaptec 2940UW SCSI controller
controller ahc0
controller ahc1
options AHC_TAGENABLE
options AHC_ALLOW_MEMIO
# Devices connected
device ch0
device sd0
device st0
device cd0
# The syntax for wiring down devices is:
controller scbus0 at ahc0
disk sd0 at scbus0 target 0
tape st0 at scbus0 target 1
tape st1 at scbus0 target 2
device ch0 at scbus0 target 3
tape st2 at scbus0 target 4
controller scbus1 at ahc1
disk sd1 at scbus1 target 0
disk sd2 at scbus1 target 1
device cd0 at scbus?
# ps2 mouse
device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr
options "PSM_ACCEL=3"
# syscons is the default console driver, resembling an SCO console
device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr
# sio1 (dcf-77)
device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr
device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr
device lpt0 at isa? port? tty irq 7 vector lptintr
#
# BISDN section
#
#options IPI_VJ # Van Jacobsen header compres. support
#options "IPI_DIPA=3" # send ip accounting packets every 3s
# This is the Teles S0/16.3 card at 0x180 !!!
#controller tel0 at isa? port 0xd80 net irq 9 vector telintr
#pseudo-device disdn
#pseudo-device isdn
#pseudo-device ipi 4
#pseudo-device itel 2
#pseudo-device ispy 1
#pseudo-device ipp 2
#pseudo-device ppp 2
# Order is important here due to intrusive probes, do *not* alphabetize
# this list of network interfaces until the probes have been fixed.
# Right now it appears that the ie0 must be probed before ep0. See
# revision 1.20 of this file.
#device ed0 at isa? port 0x280 net irq ? iomem 0xe8000 vector edintr
#
# Audio drivers: `snd', `sb', `pas', `gus', `pca'
#
# snd: Voxware sound support code
# sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum
# sbxvi: SoundBlaster 16
# sbmidi: SoundBlaster 16 MIDI interface
# pas: ProAudioSpectrum PCM and MIDI
# gus: Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX
# gusxvi: Gravis Ultrasound 16-bit PCM
# gusmax: Gravis Ultrasound MAX (currently broken)
# mss: Microsoft Sound System
# opl: Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum
# uart: stand-alone 6850 UART for MIDI
# mpu: Roland MPU-401 stand-alone card
#
# Beware! The addresses specified below are also hard-coded in
# i386/isa/sound/sound_config.h. If you change the values here, you
# must also change the values in the include file.
#
# pca: PCM audio through your PC speaker
#
# If you don't have a lpt0 device at IRQ 7, you can remove the
# ``conflicts'' specification in the appropriate device entries below.
#
# Controls all sound devices
#controller snd0
#device sb0 at isa? port 0x220 irq 10 drq 3 vector sbintr
#device opl0 at isa? port 0x388
#
# Miscellaneous hardware: `mcd', `wt', `ctx', `apm'
#
# gp: National Instruments AT-GPIB and AT-GPIB/TNT board
# joy: joystick
# labpc: National Instrument's Lab-PC and Lab-PC+
#device joy0 at isa? port "IO_GAME"
pseudo-device loop
pseudo-device ether
pseudo-device log
pseudo-device ccd 2
pseudo-device bpfilter 4
pseudo-device sl 2
# ijppp uses tun instead of ppp device
pseudo-device tun 1
pseudo-device pty 32
pseudo-device gzip #Exec gzipped a.out's
pseudo-device vn #Vnode driver (turns a file into a device)
--==_Exmh_5296095340--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802040656.AA187635393>